Built for absence

Software that runs
when you don't.

Inai builds autonomous systems that run the work you'd rather not babysit — recovering from failures, escalating with context, and paging a human only when the playbook runs out.

$ inai daemon --detachuptime 41d 06h · 0 weekend pages
What we build

The runtime, the agents that live on it, and the way you watch them.

three primitives
INAI.RUNTIME

A process that survives you.

The workflow keeps state through every crash, restart, and network blip. Nothing falls on the floor. Nothing runs twice.

sla99.97%
restartsauto-resume
weekend pages0 expected
INAI.AGENTS

Operators that don't sleep.

Long-running agents with a memory, a budget, and a playbook. Escalate with full context when stuck.

modelsany
budgetsper task & customer
escalationslack · pagerduty
INAI.TELEMETRY

Proof the silence is healthy.

A live status board, full decision history, and a weekly digest. You can show anyone what the system did while you were away.

status boardlive
history90 days default
audit logcsv · pdf
Manifesto · three rules

What an absent system promises.

Read the full manifesto
01

Absence is the spec.

What happens when nobody is watching is the design question.

02

The runtime is the product.

Features come and go. The process that survives restarts is the asset.

03

Page humans last.

Agents escalate with context — what they tried, where they're stuck.

Private design partnership

We'll page you when there's a runway.

Inai takes a small number of design partners per quarter. Tell us what you'd want to hand off.

Request access