Pre-GABuilding with design partners

AI for production that runs air-gapped.

No internet required. TZero runs on open-source models you host, and your data stays inside your network.

  • Air-gapped
  • Runs on open-source models
  • Changes wait for a person
Works withDocker VMsCloud RunGKEAzurePostgresRedisGitHub

01 · Product

Know it. Ask it. Remember it.

Know

A map that matches production

Every service, at the commit it's running.

checkoutabc123 · 2h
ownerpayments
usesorders-db, redis
errorsnormal

Ask

Ask the agent

Support and on-call ask in plain language. The agent runs approved steps.

YouWhy was #4412 charged twice?
read · billing180 ms
read · logs240 ms
TZeroThe first charge timed out and the retry charged again.

Remember

Every fix makes the next one faster

The next alert starts with what worked.

Queue fullsame as Aug 12
Worker restartedapproved by Lena
Release abc123rolled back
Root cause draftedreviewed, then saved

Change safely

Changes wait for a person

Dry run, approval, then it runs from your cloud.

fix orders.status312 rows
before → afterpending → paid
ApproveDismisssecond engineer required

Prove it

The record is the audit

Who asked, what ran, who approved. Export in a click.

Q3 changes1,284
approved by a second person100%
SSH keys replaced14
Example figures.

02 · Platform

Autonomous agents. Planned work.

A planner turns intent into steps. Routing picks the right agent. Agents talk to each other. The work runs; changes still wait for a person.

Planner

A plan before anything runs

From a release diff or a plain-language question, TZero builds a watch plan or work plan: what to check, what to read, what would change.

goalwatch release abc123
steps5 checks · 15m / 1h / 1d
readslogs, metrics, rows
changeshold for a person

Routing

Work goes to the right agent

Questions and checks are routed to the service, owner, and agent that already know that part of production, not a generic chat.

askWhy was #4412 charged twice?
routecheckout → billing
agentrefunds-v2
ownerpayments

Agent ↔ agent

Agents hand work to each other

A release agent can ask the map, call an ask agent for context, or pass a remembered fix forward, without starting from zero.

release→ map · live commit
ask→ billing · 180 ms
remember→ Aug 12 restart
Hand-off recorded. Same thread.

Autonomous work

Agents drive the work

Once the plan is set, agents run the reads and watches on their own. Anything that changes production still waits for a person.

statusrunning
reads12 · no engineer
proposedrollback 9f81c2e
gateapprove @Lena

planrouteagents talkrunhold for a person

03 · Release agents

Every deploy gets its own agents.

Agents are created from each diff, follow the code when it moves and retire when it's deleted. Each one checks its change at 15 minutes, an hour and a day, then stops.

Releases this week

+ new · retired · watching
7e21a0fMon · billingbillinginvoice-legacy
abc123Tue · refunds v2+ refunds-v2billing · reboundinvoice-legacy
c90d4e2Thu · nightly sync+ nightly-syncrefunds-v2billing
f3b8a61Fri · cleanuprefunds-v2billingnightly-sync · watching

04 · Use cases

Most production work isn't an incident.

One week

5 jobs · 0 engineers paged
MON 14:02Release checkDeveloperBad line found in 18 min
TUE 10:31Support questionSupport leadAnswered with no engineer
WED 02:14Night pageJunior on-callFixed with last time's fix
THU 16:40Data fixEngineer312 rows, reviewed first
FRI 09:00New hireFirst weekOn-call with no credentials

05 · Safety

Reads run at speed. Changes wait for a person.

Guarantees

6 of 6 on
Runs air-gapped
Nothing dials in
Approved actions only
No standing credentials
Every action recorded
Open-source models you host

GitHub and Datadog are optional connectors and the only parts that reach the internet. Leave them off and TZero runs fully air-gapped.

lookproposehold for a personapproverecord

Design partners

Pre-GA

Worth one release.

01Connect one service
02Ship a release
03Ask a real question
04Judge the answer

No fake metrics · no fake logos · the product video uses sample data