Architecture overview
- Console — Session cookies scoped to
.agentruntime.io; HTTPS only in production - REST / Platform MCP — Personal access tokens with scoped permissions
- Inbound webhooks — HMAC-signed body + automation PAT; no session cookie on public ingress
- Workflow runs — Execute in tenant-scoped projects with role checks on every API call
https://api.agentruntime.io. Do not call internal service URLs directly.
Tenant isolation
| Layer | Isolation |
|---|---|
| Workspace (tenant) | Billing, members, vault paths, and default project scope |
| Project | Workflows, runs, MCP instances, connections, inbound subscriptions |
| Roles | tenant_admin, project_admin, project_contributor, project_viewer — see Roles and permissions |
X-Tenant-Id and X-Project-Id for scoped operations. PATs are validated against user identity and project role.
Secrets and credentials
| Secret type | Storage | Console path |
|---|---|---|
| Connector API keys | Vault-backed Connections | Connections |
| LLM vendor keys | Vault-backed Providers | Providers |
| Automation PATs | Vault-backed API keys | Settings → API keys |
| Webhook signing secrets | Shown once at subscription create | Workflow → Inbound |
| Workspace vault paths | Tenant vault | Settings (admins) |
Authentication
- Email + password with verification for new accounts
- Google OAuth (Sign in with Google / One Tap)
- PATs for CI, scripts, inbound webhook automation, and Platform MCP
- Domain verification — Tenant admins can restrict workspace access to verified email domains
Inbound webhook security
External senders must provide:Authorization: Bearer pat_…(automation PAT bound to the subscription)X-Agentruntime-Signature: sha256=<hmac-sha256 of raw body>using the signing secret
Data handling
| Data | Notes |
|---|---|
| Workflow graphs | Stored per project; published versions are immutable snapshots |
| Run events | Step inputs/outputs logged for observability and Command Center |
| LLM prompts | Sent to the model provider you configure (tenant or platform key) |
| MCP tool calls | Executed against your bound connections; third-party adapters follow their vendor policies |
| Billing ledger | Usage events and credit debits in Wheelhouse |
Compliance posture
AgentRuntime is not certified for regulated workloads out of the box. Evaluate against your requirements:| Topic | Current guidance |
|---|---|
| HIPAA / PHI | Do not use the healthcare connector in production — mock APIs only. Do not store PHI in workflows without a BAA and architecture review. |
| PCI | Do not pass cardholder data through workflow input or MCP tools. Use Stripe Checkout for payments. |
| SOC 2 / ISO | Contact sales for current attestation status and security packet. |
| Data residency | Discuss deployment region and subprocessors with sales for enterprise contracts. |
| AI subprocessors | LLM calls route to vendors you configure (OpenAI, Anthropic, Google, etc.). Review their DPAs. |
Shared responsibility
| You are responsible for | AgentRuntime is responsible for |
|---|---|
| PAT and webhook secret hygiene | Platform patching and edge TLS |
| Connector credential scope (least privilege) | Tenant-scoped API authorization |
| Workflow logic and data minimization | Vault storage for configured secrets |
| External webhook sender integrity | Signature verification on ingress |
| LLM prompt content and PII policies | Metering and audit of billable actions |
Legal policies
Review the current policies on the marketing site:| Policy | URL |
|---|---|
| Privacy | agentruntime.io/legal/privacy-policy |
| Terms of service | agentruntime.io/legal/terms-of-service |
| Billing and credits | agentruntime.io/legal/billing |