What is AT0?
AT0, pronounced "Auto", is private AI for putting your whole life on auto: a private operating layer that coordinates memory, agents, approvals, and life domains around one owner.
AT0 is for people who want the capabilities of big AI with private infrastructure, persistent memory, and controls they can see.
AT0, pronounced "Auto", is private AI for putting your whole life on auto: a private operating layer that coordinates memory, agents, approvals, and life domains around one owner.
Those tools are powerful general AI services. AT0 is a private operating layer around the person: owner-controlled memory, domain boundaries, custom agents, human approval, and workflows that become your own system over time.
It means AT0 is shaped by the operator's domains, permissions, habits, tone, priorities, and review rules. The goal is not a generic assistant. The goal is private AI that learns how your life and work actually operate.
The owner does. AT0 memory is designed to stay visible and scoped by domain, with source, edit, delete, and export controls instead of a hidden profile you cannot inspect.
No. The public site uses early-access form data to respond about AT0 and measure aggregate interest. AT0's product direction is private infrastructure and no data resale.
AT0 is designed around owner-controlled infrastructure: Mac mini, home server, NAS, Unraid node, or a dedicated AT0 Node. The public website is hosted separately on Cloudflare and only handles marketing pages, analytics, and access requests.
Yes, inside guardrails. High-stakes actions stay behind human approval so the system can help without hiding important decisions from the owner.
The public roadmap covers memory, family, financial, medical, home, creation, privacy, legal, documents, and calendar domains, with agents such as Forge, Warden, Smithy, Crucible, Spark, and Herald.
No. AT0 organizes context, drafts action, and tracks decisions. Medical, financial, and legal decisions require owner or professional review before action.
AT0 is opening in deliberate waves of 500, 1,000, and 5,000 so onboarding can stay safe and feedback can shape the product before broader release.
Your request goes into the Founder Circle queue. Early requests receive onboarding priority, a private AI readiness checklist, and first access to the AT0 Node path as waves open.
Start with the story, then request access when the use case is clear.
Read why AT0 exists