Back to corpus
architecturetechnical paper candidatescore 50

AgentOS — System Architecture

``` ┌─────────────────────────────────────────────────────────────────────────────┐ │ AgentOS Platform │ │ │ │ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │ │ │ Dashboard │ │ CLI │ │ SDK │ │ Webhooks │ │ │ │ (Next.js) │ │ (agentos) │ │ (npm pkg) │ │ (inbound) │ │ │ └──────┬───────┘ └──────┬──────┘ └──────┬──────┘ └──────┬──────┘ │ │ │ │ │ │ │ │ ═══════╪═════════════════╪═════════════════╪═════════════════╪══════════ │ │ │ API Gateway (Hono) │ │ │ │ │ ┌──────────────────────────────────┐ │ │ │ └─

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

| Layer | Isolation Method | |-------|-----------------| | **Database** | Row-Level Security (RLS) — every table has `tenant_id`; policies enforce `auth.uid()` → `tenant_id` mapping | | **Compute** | Session-level isolation — each session runs in sandboxed context with tenant-scoped filesystem | | **Secrets** | Vault per tenant — encrypted at rest; decrypted only in session runtime | | **Events** | Channel-per-tenant — Redis channels namespaced by `tenant:{id}:*` | | **Storage** | Prefix-per-tenant — `{tenant_id}/` prefix in object storage | | **API** | Middleware injection — `req.tenantId` set by auth; all queries scoped automatically | | Feature | Free | Pro ($49/mo) | Enterprise (Custom) | |---------|------|-------------|---------------------| | Concurrent sessions | 2 | 20 | Unlimited | | Session duration | 5 min | 30 min | Unlimited | | Heartbeat checks | 5 | 50 | Unlimited | | Dream garden | 10 dreams | 100 dreams | Unlimited | | Skills | Public only | Public + private | Custom + self-hosted | | Model providers | 1 | Unlimited | Unlimited | | Team members | 1 | 10 | Unlimited | | Support | Community | Email | Dedicated | | SLA | None | 99.9% | 99.99% | | Token budget/mo | 1M | 50M | Custom | | Metric | Rate | |--------|------| | Tokens (pass-through + 15% markup) | Provider cost × 1.15 | | Session compute (per min) | $0.005/min | | Storage (per GB/mo) | $0.10/GB | | API calls (over tier limit) | $0.001/call |

Promotion decision

What has to happen next

Promote into a technical note or architecture paper with implementation anchors.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.