An agent runtime, not just a chat
A chat that drafts a reply is a demo. An agent runtime is the place those agents live and run in production — persistent, stateful, scheduled, and overseen. OrgSDK is built to be that runtime for your whole agent team.
- Hosted & always-on
- Persistent, stateful agents
- Bounded code workflows
- Schedules, not babysitting
- Approvals out of the box
- Full audit trail
What an agent runtime does
The operational jobs, built in
Running agents in production is a list of jobs: give them tools, fire them on a schedule, let them remember, gate the risky steps, and record everything. OrgSDK ships each one — no glue to write.
Persistent agent teams
Agents have roles, tools, and memory. They survive restarts, keep their identity, and run around the clock — not as single calls, but as a team.
Workflows in TypeScript
The operating model is real, versioned TypeScript with typed inputs and scoped tool access. Inspectable, repeatable, and precise.
Schedules that fire
Drive work with schedules. The work stays on even when no one is watching.
Memory & durable state
Memory, tables, and artifacts persist across sessions and service restarts. Agents keep what they learn between runs — no lost context.
Human approvals
Pause any workflow for a decision before a risky action. Approve, reject, or reply from the dashboard — every gate is logged.
Audit & run traces
Each run records its steps, tool calls, and results. The activity feed is the source of truth for what your agents did, and when.
Tenant separation
Safe enough to actually let agents act
Each team has its own security boundary in the managed cloud. Workflows use typed, versioned TypeScript and can call only the tools enabled for their agent. Work stays bounded, inspectable, and repeatable. One org's agents, memory, and credentials never bleed into another's.
Scoped plugins
Every tool is an explicitly attached plugin — scope is per agent.
Approval gates
Pause any irreversible step for a human decision, fully logged.
Per-tenant isolation
Agent state, credentials, and work stay within the organisation's boundary.
Durable state
Memory, tables, and artifacts survive sessions and service restarts.