Osy#betaRun it on Osyrin: osyrin.com

Reference / Zones

An organization's apps

osyrin org apps [--org <slug>] [--server <url>] [--json]

`osyrin org apps` lists the apps of one organization — slug, name, status and how many versions each has — and says which organization they belong to. Name it with `--org` when you belong to more than one; with one, it is used.

stablezonescliapplicationsorganizations

Summary#

osyrin org apps --org acme lists every app of the organization acme, under a title that names it: Applications of Acme Ltd (acme on https://osyrin.app). It is the same --org every other osyrin org command takes (An organization's environments).

Signature#

osyrin org apps [--org <slug>] [--server <url>] [--json]

Description#

Which organization?#

  • --org <slug> names it. Its id works too. An organization you are not a member of is refused, and the refusal lists yours: No organization 'acne'. Yours: acme, globex.
  • Left out, your only organization is used. When you belong to more than one, the command refuses rather than guess — You belong to more than one organization — name it with --org: acme, globex. — and lists nothing.

Only that organization's apps are listed; an app of another organization you belong to never appears in the table. A deleted app is not listed.

What each row says#

columnmeans
Slugthe app's slug on Osyrin Cloud: the name your project gave it, then the organization's slug (ledger-acme)
Namethe app's name
StatusDraft, Published, Archived or Dormant — below
Versionshow many versions of the app have been built

Status:

  • Draft — the app exists and has never been served.
  • Published — it is served in at least one environment.
  • Dormant — nothing has served, deployed or opened it for 90 days, on a plan that removes what goes quiet. It is still served, and the first visit makes it Published again.
  • Archived — an app its organization has set aside.

An organization with no apps yet says so: Acme Ltd has no applications yet. Create one with osy deploy (Deploying your app to an environment).

For a script: --json#

{
  "organization": "acme",
  "applications": [
    {
      "id": "6f1c…",
      "slug": "ledger-acme",
      "canonicalSlug": "ledger",
      "name": "Ledger",
      "status": "Published",
      "latestVersionLabel": "1.4.0",
      "latestPublishDate": "2026-10-24T09:12:00Z",
      "versionCount": 3
    }
  ]
}
  • organization — the slug of the organization listed.
  • slug — as in the table. canonicalSlug is the name your project gave it, without the organization's part.
  • status — by name, as in the table.
  • latestVersionLabel and latestPublishDate — the newest version built, and when; null for an app with none.
  • versionCount — how many versions have been built.

Options:

  • --org — the organization; needed when you belong to more than one.
  • --server — the Osyrin to ask (default: the one you signed in to).
  • --json — the shape above, in place of the table.

A refusal exits with 1; an Osyrin that cannot be reached exits with 2.

Examples#

osyrin org apps --org acme
osyrin org apps --org acme --json
osyrin org apps --org acme --server https://osyrin.app

See also#

An organization's environments — the organization's environments, which its apps are deployed to.

Deploying your app to an environment — creating and deploying an app from your project.

Deploying an application to a cloud platform — the zone builds it — what a deploy does in the zone.

What your plan allows, and how much of it is used — how many apps a plan includes.

Related

An organization's environments

An organization's environments — prod, staging, sandbox — are where its apps are deployed, each with its own database…

Deploying an application to a cloud platform — the zone builds it

A cloud deploy hands over the application's bundle — its app blob and the package archives it pins — to the zone the…

Deploying your app to an environment

Builds your app on this machine and hands it to the zone one of its organization's environments runs on — `osy deploy…

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

`osyrin org plan` and `osyrin app plan` say which plan applies and, for every meter — requests, CPU, egress, storage…