Product pages
Build apps
The path for building an app on Orkestia — sign-in, backend, data, hosting, chat, domain, modules and flags, environments, pricing — in the order you meet them.
An Orkestia app is an Identity app plus whatever you attach to it. Your frontend can live anywhere. Orkestia supplies login, a backend made of compositions, a data plane, and optionally the hosting.
This section is the map. Each step links to the section that holds the detail.
The lifecycle
1. Create the Identity app sign-in + end-users → App Enablement
2. Write the backend compositions, schedules → Backend
3. Store data App Data, ownership → App Data
4. Go live site, processes, Files → App Host
5. Add realtime chat space, Buzz → Chat
6. Use your domain CNAME + TXT → App Host
7. Gate what each user may use expose, capability, flag → Modules and feature flags
8. Run it Lumen, backups, limits → Operate
Where each part lives
| You want to | Start here |
|---|---|
| Add "Sign in with Orkestia" | App Enablement and the Auth SDK |
| Write business logic without a server | Backend |
| Store rows that belong to a user, an app or a workspace | App Data |
| Publish a site or run a container | App Host |
| Give users a chat | Chat |
| Track the people who reach your app as contacts and leads | CRM |
| Let a group of users share data | Workspaces |
| Let your users build their own automations | End-user authoring |
| Switch a feature off for your users | Modules and feature flags |
| Stage a release before production | Environments |
| Know what it costs and what the limits are | Pricing and limits |
| Watch an app in production | Operate, Lumen and Operations |