Subbasis Docs
Build governed agentic execution with Subbasis.
Subbasis is a governed agentic execution platform. It is built for teams that want to use AI systems in real operations without losing control over permissions, approvals, context, and reviewability.
Simple automation often assumes linear triggers and short-lived tasks. Real operations are different: they pause, fail, resume, escalate, require human decisions, and depend on external systems. This is why agentic execution needs a runtime and not only prompt templates.
Why agentic execution needs a runtime
LLMs can reason probabilistically. They are strong at drafting, classifying, and proposing next actions. But business operations need deterministic boundaries around execution. A runtime enforces those boundaries:
- what an agent can do
- when an approval is required
- which connector is allowed
- how evidence is recorded
- how retries and recovery happen
Without runtime control, workflows drift into fragile ad-hoc automation. With runtime control, AI reasoning becomes part of a governed execution system.
How Subbasis differs from simple automation
Subbasis is designed around durable execution, not only event triggers:
- Workflows can wait and resume over long periods.
- Agent tasks run with permissions and policies.
- Connector usage is governed through explicit execution contracts.
- Context Intelligence keeps operational state attached to the execution path.
- Evidence captures decisions and outcomes in reviewable history.
Subbasis constrains execution through deterministic contracts, policies, and evidence boundaries. It does not assume perfect determinism of every external system.
Who these docs are for
- New adopters who need a practical first workflow.
- Developers and technical founders designing runtime-aware operations.
- Operators and SME teams running governed execution day-to-day.
- Architects and advanced readers evaluating local execution and distributed models.
Choose your path
New to Subbasis
Developer / technical founder
Operator / SME
Architect / advanced reader
Where to start now
If you are implementing your first use case, begin with Getting started overview, then complete First governed workflow, and keep Key concepts open as a reference.