What your plan allows, and how much of it is used

Summary#

osyrin org plan --org acme prints the organization's plan and a line per meter: used, included, and what the limit does. osyrin app plan --app billing-acme does the same for one app — its own plan, or its organization's.

Signature#

osyrin org plan [--org <slug>] [--server <url>] [--json]
osyrin app plan --app <slug> [--server <url>] [--json]

Description#

One line per meter. Each meter says how much was used in the current month — the organization's own month, the same for its apps — how much the plan includes (or that it is unlimited), and in words what happens at the limit: a warning, a charge for the overage, or a refusal. Some meters are levels rather than sums: storage is the latest measured reading, and apps, environments and custom domains are counted as they are now.

Two meters are about backups. Backup retention is not a limit you reach: it says how many days a backup is kept — 7 on the Beta plan, 30 on a paid plan — and it has no percentage. Backups on demand counts the backups a person asked for this month (Request backup, osyrin app backup). The Beta plan includes none, so that request is refused there; the nightly backup is not a request and is always taken. See Downloading your daily backups.

The plan line says where it comes from: the plan the subject subscribes to and since when, or the plan every organization or app gets by default, with any add-ons.

Token usage is separate. The LLM and embedding tokens an app spends are read with osyrin app usage and osyrin org usage, day by day.

Who may read it: the organization's members for the organization, and the app's team for an app. A subject you cannot see is answered as not found.

• --json — Admin's own record: {subjectName, planName, planLine, addOns, meters: [{meter, name, unit, used, included, unlimited, percent, resetsAt, atLimit, summary}], overall}.

Examples#

osyrin org plan --org acme --server https://osyrin.app
osyrin app plan --app billing-acme --server https://osyrin.app --json

See also#

An organization's environments — environments count against a plan.

Serving an app at your own domain — so do custom domains.

Downloading your daily backups — how long backups are kept, and downloading them.

Reading what your application actually used — what an app used on your own computer.