Architecture

Built to run agents around the clock, safely

OrgSDK is cloud-only and designed to keep each organisation separate. Agents, memory, and credentials stay within tenant boundaries. Here are the guarantees your team can rely on.

What you can rely on

Four guarantees for production agent work

Managed operations, tenant separation, bounded execution, and durable continuity are built into every plan.

Managed cloud

OrgSDK runs as a managed cloud service, including hosting, upgrades, and day-to-day operations. There is no self-hosted deployment to maintain.

Tenant separation

Each organisation's agents, state, and credentials are kept within its own security boundary and separated from every other tenant.

Bounded execution

Workflows can use only the tools explicitly enabled for their agent. Typed inputs and versioned code make recurring work inspectable and repeatable.

Durable state

Agents, memory, tables, artifacts, schedules, runs, approvals, and audit history persist across sessions and service restarts.

Per-tenant isolation

Your org is its own world

Tenant separation is a product guarantee, not an optional setting. The data and work of one organisation remain separated from another. Agents, memory, and credentials for one org never cross into another.

  • Tenant separation by default
  • Durable state within your boundary
  • Bounded execution with scoped tools

Tool access

Tools are scoped, not global

Every tool an agent can call is explicitly enabled for that agent. 100+ built-in tools reach your stack — email, code, data, search, and the web — but nothing is reachable unless you wire it up. Scope is set per agent, not org-wide.

  • Tools enabled per agent, explicitly
  • Credentials encrypted at rest
  • Credentials available only within their approved scope

What happens when work runs

From instruction to accountable result

  1. 01

    You create an agent or start a workflow from the dashboard or an MCP client.

  2. 02

    OrgSDK verifies access and applies the permissions configured for that agent.

  3. 03

    The workflow runs with only its approved tools and pauses at any human approval gates.

  4. 04

    Results, memory, and audit history are saved so your team can inspect what happened and continue later.

Cloud-only, by design.

There is no self-hosted deployment and no bring-your-own infrastructure offering. Hosting, isolation, upgrades, and the operational surface are ours to run — so you can focus on what your agents do, not on keeping them alive.

Run agents with guarantees you can verify

Choose a plan for managed cloud operations, durable state, scoped tools, approvals, and auditability.