The chat is solo. Real life isn’t.

A single person talking to an assistant is a tool. A group of people and an AI working in one shared Space — where the thinking becomes structured, durable artifacts everyone can see — is something else. It's the difference between an answer and a plan.

Most software makes one person the operator and everyone else a spectator. We think the opposite is the point: the value shows up the moment the second person is in.

One engine, two products. For life: trips, reunions, moves — whoever you're planning with, your own calendar and files. For work: a launch, an incident, a migration, an offsite — the cross-functional work no doc keeps up with, your org's tools connected once. Same engine: a shared Space the AI turns into a living set of structured artifacts.

The AI in stateful has a name and a character: Pango, a robot pangolin. You summon it with @pango (or @ai) in any Space, and you'll see “Pango is thinking…” while it works. Picking a character — not just a name — was the unlock. Pango is persistent without being needy, comfortable being part of a group it didn't choose, and not afraid to organize a mess. Three months of trying other names told us this matters more than it sounds. The full story is on the blog.

Small, opinionated, and honest about where we are. We're early — so you won't find inflated logos or invented numbers on this site. We'd rather earn the proof than fake it.

The product is new. The thinking isn't. The same team spent years on tools for developer workflows — Runme, Foyle, a long string of notebook + AI experiments — chasing the same question from a different angle: how groups of people keep state across the messy middle. stateful is the answer we eventually arrived at: built for everyone, not just engineers.

The current writing lives on the blog.

Press, partnerships, or just curious: hello@stateful.com.