01
Observe
Telemetry, audit history, and GKE events through typed read-only tools — every evidence record carries source, time range, and hash.
Solvan detects production degradation from real alert events, investigates with read-only evidence tools, acts within bounded authority, and verifies recovery — then stays on the case until the defect is permanently repaired.
scripts/bootstrap && scripts/startOpen source under Apache 2.0 — built for production systems on Google Cloud: Cloud Run, GKE, and Cloud SQL. Every action authorized, bounded, and receipted.
p95 latency 2.7 s sustained 6m · 3 alerts deduplicated into 1 incident
Evidence + infrastructure agents · 14 typed read-only calls
Connection-pool recycle · pre-authorized by policy · reconciled
Rollback exceeds autonomous authority · awaiting commander
payments-api v2.8.1 → v2.8.0
digest a1b2c3…e4f5d6 · target v2.8.0 · risk high
Bound to action digest, target version, and expiry. Any change invalidates it.
Observes and actuates across your GCP production environment
Your production environment
Your incident and tooling layer
Platform
Solvan deploys into your GCP project and region. Production credentials never reach a model.
01
Telemetry, audit history, and GKE events through typed read-only tools — every evidence record carries source, time range, and hash.
02
A private actuator in your region holds the only production permissions. Bounded mitigations run under policy; high-risk actions need digest-bound approval.
03
Every agent runs under its own least-privilege identity. Policy screens every call, and all state stays in Cloud SQL in your project.
GCP is the first supported environment. AWS and Azure are on the roadmap.
How it works
One continuous loop — no hand-offs between tools, no lost context.
Events, not prompts.
The evaluator runs every 25 seconds against real alert events. Duplicates are deduplicated; each incident opens with durable typed state.
Read-only by construction.
Agents gather evidence in parallel with typed read-only tools. Every record carries provenance — a hypothesis never silently becomes root cause.
Bounded authority, exact approvals.
Pre-authorized mitigations execute immediately. High-risk actions need approval bound to the exact action digest, target, and expiry.
Mitigation is not repair.
Recovery is judged independently from fresh telemetry and probes. A Reliability Case stays open until permanent repair is verified.
Why Solvan is different
Permissions live in identity, IAM, and gateway policy — not prompt promises. A policy-denied action stays denied, even if a human approves it.
An incident can read “Service restored · repair open” for days while the Reliability Case drives the permanent fix.
Confidence never converts a hypothesis into root cause. Every committed fact carries its source and freshness.
Incidents, approvals, and receipts live in Cloud SQL — not a chat window. Agents can crash mid-incident and resume without duplicating side effects.
Capabilities
Multi-day ownership with durable checkpoints. A case closes only when permanent repair is independently verified.
Every high-risk approval binds to the action digest, target version, and expiry. Change any of them and it's void.
Recovery is judged by service-owned profiles and synthetic probes — the planner can't weaken its own success criteria.
Only verified learnings with full provenance reach the Memory Bank. Never a guess, a fluke, or an unverified fix.
Identity, gateway enforcement, and Model Armor apply uniformly to every agent — observable activity, auditable authority.
Decisions and evidence without private chain-of-thought. Every claim links to its source, every action to its receipt.
Security
An agent that touches production has to earn authority structurally.
Each agent runs under its own scoped identity — no shared credentials, no ambient authority.
Credentials never enter model context, traces, or the DOM. Evidence is redacted at the tool boundary.
The gateway can deny a critical action even when a human approves it.
State, telemetry, and memory stay in your GCP region, in your project.
Every detection, approval, and execution produces a durable, queryable receipt in Cloud SQL.
Incidents, cases, and memory are partitioned per tenant at the data layer.
Apache 2.0. Solvan deploys into your own GCP project — every line is yours to audit.
Solvan is an early-stage project. These are architectural commitments enforced in code — not certifications.
Detect the next degradation before your users report it — and get to a verified recovery, with receipts.