Priced like a backend.
Not like a leap of faith.
Beta pricing, stated plainly. History lives on object storage, so keeping everything forever is the default — not a premium tier.
Developer
For building and verifying locally.
- —Local engine, CLI, and Studio
- —Unlimited Scenarios and invariants
- —Full provenance, locally
- —Agent skills for Claude Code, Codex, Devin
Team
For shipping contained systems to production.
- —Managed cloud runtime and deploys
- —Observation log kept forever, object-storage rates
- —Receipts and audit views for operators
- —Verification gates in CI
Enterprise
For regulated and high-stakes domains.
- —Dedicated runtime cells, SSO, private networking
- —Retention, redaction, and legal hold, declared against the ontology
- —Audit exports with provenance intact
- —Support with named engineers
beta pricing — locked for design partners through general availability.
Asked precisely, answered plainly
Why is storage effectively unmetered?
The observation log lives in sealed, content-addressed segments on object storage; the ontology decides layout, and semantic indexes let queries skip segments entirely. Cold history costs S3 prices while remaining query-serving, so "keep everything" is the default posture, and it is passed through at cost.
Does Tarski replace my coding agent?
No. Tarski is the ground your agent builds on. Claude Code, Codex, Devin, and others author dh against your contract; Tarski verifies the result and contains what runs.
Can I migrate an existing Postgres or Firestore app?
Not wholesale. Tarski is observation-first and does not emulate mutable-state databases. Teams typically start with a new agent-facing surface — a containment boundary around an LLM feature — and grow from there.
What does "verified" actually claim?
That every Scenario in your corpus reproduces its expected world exactly, and every named invariant holds at every fixpoint, under a deterministic evaluator. It is a precise statement about declared behavior — not a theorem about all possible inputs, and we don't pretend otherwise.
What happens when an invariant refuses a transition in production?
The intent is refused with a receipt naming the invariant and the observations involved. Nothing touches the world. Operators see it in Studio, and the pinned timeline can be promoted to a fixture in one step.