Orkestia
Proud to collaborate with Microsoft for Startups
Sign in

AppData: records that belong to the app

AppData is the platform data plane. Apps persist records as workflows, with the same identity as every other catalog call.

Orkestia2 min readUpdated

Orkestia is the backbone that connects software, AI, and the real world. AppData is where an Orkestia app keeps its records. Not a database you SSH into. A data plane on the same engine as Deploy and Staff: typed, permissioned, audited.

When the database is yours, connect Neon or the cloud you already run. Neon Postgres, connected once. When the record belongs to the app on Orkestia, AppData is the store. Agents query it through the catalog, not through an ad-hoc URL.

What lives here

App-owned tables, records, and the workflows that create and read them. Access follows the principal that started the run: a member, a Staff actor you granted, or an end-user who signed in with Orkestia. End-users do not see the operator console. Sign in with Orkestia.

The live types are in the catalog, AppData and data. domains. reference.orkestia.dev is the same list with schemas. Do not assume a SQL client is the way in unless the catalog says so. The workflows are the way in.

How you use it

  1. Create an account and subscribe.
  2. Provision the app that will own the records.
  3. Declare the tables the app needs, through the types the catalog lists.
  4. Read and write as workflows, from the console or from MCP.
whoami()
list_workflow_types(prefix="appdata.")
list_workflow_types(prefix="data.")
get_workflow_schema("<type>")
start_workflow(workflow_type="<type>", initial_data={...})

If has_prerequisites is true, finish them before you write. A failed write retries on the same run id.

What it is not

It is not a replacement for Magalu, AWS, or Neon when you already have a database in that account. It is not a second ledger for Omie or Bling. Those stay the system of record for the books. Omie on Orkestia, Bling on Orkestia.

A first afternoon on AppData

  1. Subscribe. Provision the app that will own the tables.
  2. list_workflow_types(prefix="appdata.") and prefix="data.". Open the schema for a declare-or-create type. Start it. Read the payload.
  3. Write one record as a workflow. Read it back as a workflow. Open the history for both ids.
  4. Sign in as a fake end-user if the table is for them, and confirm they cannot see operator types.

If you catch yourself pasting a Postgres URL into chat, you are in the wrong product. Neon and Magalu connections are for databases you already run. AppData is the app's records on Orkestia.

Lifecycle for pieces of AppData still moves. The catalog is the source of truth, not this paragraph. Beta and GA labels live on the type and on the docs page for that type.

hello@orkestia.dev

  • appdata
  • platform