Put Orkestia in your app

You finish this when a person can sign in to an app you own with Orkestia. Data, hosting, and chat are the next jobs, and each one can wait.

1. Sign-in

App Enablement is the path: provision the identity app, install @orkestia/auth, wire the PKCE flow, then call Orkestia as that end user. The endpoint contract is Sign in with Orkestia.

Do this before App Data or chat. Both assume an identity app.

2. Store rows

When the app needs tables, declare them in App Data. End users reach rows through the Data API or a workflow you expose. They do not get a database URL.

3. Host the site

When you want Orkestia to serve the frontend, follow the first week on App Host: claim the site, publish the website, and attach App Data only if the site needs Postgres. Buzz is a separate hostname. Skip it until a client needs it.

4. Let people talk to an actor

When end users should talk to a Staff actor on a page you publish, follow Option A: hosted chat from enable through the first message.

The other doors, if the chat lives in your UI instead, are the embedded component, your own client, and the chat API.