v1
Platos v1 launch
The first public release. Apache 2.0, self-hostable in five minutes, production-tested. Everything below ships in the v1 baseline. Subsequent releases stack on top with deltas.
- ·Agent runtime: durable, versioned agent configs with system prompt, tools, memory, model, and budget caps composed into one record. Versioning, canary rollouts, and rollback first-class on the agent detail page.
- ·Conversations and threads: chat surface with streaming token output, tool-call traces, attachments (images, PDFs), structured output, citations, and reasoning-token display per provider.
- ·Postman mode: side-by-side conversation pipeline view for debugging tool calls, prompt assembly, and provider routing.
- ·Sub-agents and clusters: agents can spawn agents, share memory and context across a cluster topology.
- ·Skills: reusable agent behaviors with manifest-declared `required_env`. Claude-skills-format compatible. Import from URL.
- ·Connected entities: external systems wired in via the platools SDK (TypeScript and Python). 200+ MCP tools across the federated surface.
- ·Tool gateway: scope-aware routing, schema injection, per-tool ACL, audit log, retry waterfall.
- ·Approvals: human-in-the-loop with edit-first flow (approved, approved-with-edits, denied), durable approvals via wait.forToken for hours-to-days SLA, JSON arg editor on the detail page, structured rate-limit response.
- ·Background ops (BGOs): durable long-running operations spawned via `spawn_bgo`, schedulable via `schedule_bgo`. Built on trigger.dev.
- ·Memory: three-tier system (short-term thread context, long-term per-user, knowledge graph). Async extraction. Per-user drill-down with breach detection. Memory ratings loop.
- ·Observability: full trace per turn with cache, reasoning, and cost columns. ClickHouse spans store with first-class token columns. Prometheus metrics with kind labels.
- ·Cost correctness: provider-aware cache discount factors (Anthropic 90 percent, OpenAI 50 percent, Google 75 percent). Reasoning-token billing. Idempotent retries.
- ·Budget caps: per-agent, per-user, scope-wide, skill-tier. TOCTOU-safe via reservation pattern. Threshold alerts at 50, 80, and 100 percent.
- ·Governance: rate limits, safety events, breach detection. Per-user consumption summary on the Users monitoring tab. Currently-breached users panel on Governance.
- ·Encryption: AES-256-GCM at-rest for conversations behind `PLATOS_MESSAGE_ENCRYPTION_KEY`. Encrypted secret store for provider keys.
- ·MCP gateway: federates four tool families (entity tools mirrored, trigger meta-tools, Platos skills, control plane). OAuth 2.1 with Dynamic Client Registration for scoped tools. PAT bearer tokens for service accounts.
- ·Public docs MCP: unauthenticated read-only catalog at `mcp.platos.dev/mcp`, install in Claude Code, Cursor, or any MCP client with one command.
- ·Multi-key provider support: N keys per provider via numbered env-var variants. Anthropic, OpenAI, Google, Vertex, plus OpenAI-compatible providers (Groq, DeepSeek, Together, Fireworks, others).
- ·BYOK across providers: provider keys live in env vars; the Providers page shows linked status and runs health checks.
- ·Webhooks: subscribe to conversation events from any external system.
- ·OpenAPI: public REST surface documented and machine-readable.
- ·Engine layer: durable run engine V2, schedules, queues, deployments, batches, waitpoints. Surfaced in the dashboard for visibility; full reference at trigger.dev/docs.
- ·Self-host: one docker compose file. Postgres, ClickHouse, Redis, MinIO, agent, webapp. Five-minute install on a 4 GB VPS.
- ·Reference entity backend at `references/entity-hello-world` for the OSS onboarding sample.
- ·Docs and guides: 47 docs across platform, engine, governance, observability, and DX tiers. 28 guides across getting-started, integrations, recipes, and troubleshooting.
- ·Public REST API at `/api/v1/public` for docs, guides, and search. ISR-cached for 10-minute propagation.
- ·Talk to Platos: in-product chat agent backed by the docs MCP, indexes 75 markdown surfaces with question-first search.
