Guides
Start with a job. Each one ends with something you have done. The cards under it are the longer walkthroughs, for when that job needs the detail.
Start here
The concepts section explains what Orkestia is. The rest of this page is how to go further — design workflows with AI, expose them to end-users, provision runners, and run a governed delivery lifecycle — while execution stays inside your cloud accounts.
Core guides
The end-to-end workflows that define day-to-day use of the platform — from AI-driven design to governance and observability.
Building with DGI
Describe an outcome in natural language and let the Dialog Generative Interface reason it into a runnable workflow design.
Staff & Agents
Hire actors, attach agent configs, launch sessions, and oversee the fleet from staff.orkestia.dev.
Creating & Exposing Virtual Workflows
Compile DGI-designed or hand-authored compositions into deterministic virtual workflows and publish them for agents and end-users.
Keep scheduled compositions cheap
Start runs from data changes or cron times instead of minute polls, skip empty runs, and read the cost estimate before you activate.
Typed decisions with TypeSafe
Closed-set choice, score, and noul answers in front of compositions, Staff, DGI, and cluster actions. Not a chat model.
Runner Management & Provisioning
Connect, provision, and self-heal the Kubernetes and multi-cloud runners that execute work inside your accounts.
Runner group kinds
Every backend_type (Fargate, EC2, Kubernetes, Azure, GCE, Cloud Run, Droplet, Magalu, DevKit) plus purposes and integrations.
Lumen
Enable observability, mint a key, send data or install the collector, and triage in the Lumen app.
Security & Compliance
Apply the Zero Trust / Zero Code Custody model: keep code and data in your cloud while Orkestia holds only state.
Platform setup guides
Connect your cloud, deploy the runtime, and wire DNS so the core guides have somewhere to run.
AWS Connections
Establish the cross-account IAM trust that lets Orkestia orchestrate workloads in your AWS accounts without holding credentials.
Cloud Connections
Connect GCP, Azure, Magalu Cloud, and Kubernetes clusters with provider-native grants — same delegation model, no credentials in workflow inputs.
Where to start
| If you want to… | Start with | Then read |
|---|---|---|
| Design a workflow from a prompt | Building with DGI | Virtual Workflows |
| Gate a composition on a typed decision | Typed decisions with TypeSafe | TypeSafe connection |
| Govern AI agents | Staff & Agents | Staff Governance |
| Expose workflows to your users | Virtual Workflows | Auth SDK · App Data |
| Call workflows from code | SDKs | API & tooling |
| Store app rows without a DSN | App Data | App Enablement |
| Inspect agent memory | Engram | Write & recall · Field |
| Local hooks / coding runner | DevKit | Tickets & software delivery |
| Run work in your own cloud | AWS Connections → Cloud Deploy | Runner Management |
| Keep tabs on everything | Lumen | Enable · Send data · Query API |
| Turn production errors into merged fixes | Tickets & Software Delivery | Governance & Approvals |
Agent Exchange
A labor market for Staff actors — listings, deals, leases, a shared ledger, and settlement on the seller's own payment account
Receive webhooks with a re-query
Point a provider's webhook at a Hook URL, run a composition on each delivery, and act only on what the provider's API confirms. Worked example — Banco Inter Pix and boletos
