Small pieces around each OS. Not one giant SaaS.
Instead of one giant fixed backend and interface, Agentik provisions smaller contextual pieces around each OS and each team. This page explains the shape.
01 Shape
One block is the wrong shape for AI work.
Classic SaaS builds one backend, one database and one interface. Every customer gets the same shape, and every workflow bends to it.
An AI organization is not one shape. A content team of nine agents is not a growth department of forty-eight, and a client project must never see the next client's memory.
So the platform is many small pieces, placed around the work.
02 Control plane
Agentik holds the organization. The host runs the model.
The control plane keeps which OS, which project, who may do what, which step is next, which gate is open and what evidence came back. The execution layer is where the work happens: the AI host you connect over MCP, the HTTPS API or the CLI.
03 Building blocks
The building blocks.
- Edge deployment
- Edge/native deployment: the site, the API and the MCP endpoint run as one Cloudflare Worker, answered near the caller.
- Storage and databases
- D1 holds accounts, projects, runs and records. R2 holds the private files each run produces, with a checksum for every one.
- Durable coordination
- A Durable Object per account carries live updates. Coordination belongs next to the team it serves.
- Workflows
- Our own runtime on D1 and a queue: durable runs, pinned methods, dependency graphs, leases and a human gate at every step.
- Queues and schedules
- A job queue with bounded retries and a five-minute lease recovery. Automations run only with your consent.
- Model routing / AI gateway
- Agents store a need, not a model name. Nine needs map to the model your host provides, and an AI gateway will route the jobs Agentik runs itself.
- Isolated execution
- Host jobs will run in their own sandbox or container, apart from every other client and every other team.
- Dynamic interfaces
- Dynamic interfaces and app hosting: each OS declares its views, and its interface will be generated and hosted next to the team that uses it.
04 Why this shape
Why this shape fits an AI organization.
Isolation
Each client project keeps its own memory, objects, connections, overlay and audit. Small pieces per project make that boundary physical, not just a filter in a shared table.
Package
An OS declares what it needs: its stores, its runs, its schedules, its views. The platform will provision exactly that, and nothing else.
Coordination
A team that waits on a human, a lease or a timer needs one place that remembers, and that place lives with the team.
Surface
When the interface forms around the OS, it needs somewhere to live that is as small as the OS.
05 Stability
Stability is measured. Not inherited.
No platform makes a product stable by itself. Tests, evaluations and production data do.
An automated test suite and HTTP checks cover each origin. Every package declares evaluations for structure, quality and safety. Recovery is designed in: expired leases are recovered, replays are idempotent, and an uncertain effect is checked, not run again.