Financial Mac
Designed to graduate to its own Mac so money workflows can keep tighter audit, caps, and approval controls.
AT0 · pronounced Auto
Your whole life,
on Auto.
AT0 is private AI with big-AI capability: owner-controlled memory, specialized agents, human approval, and a system you can make your own.
Private infrastructure
Designed around owner-controlled systems, not an ad-funded cloud assistant.
Human approval
High-stakes actions wait for review before AT0 acts on your behalf.
Domain isolation
Family, financial, medical, and code contexts stay bounded by role.
No data resale
Early-access data is used to contact you about AT0, not sold or shared.
Why now
Cloud AI got powerful. The private layer is missing.
The market already understands chat, memory, and agents. What is still missing is an owner-controlled system that can work across a private life without turning that life into cloud product data.
01
Memory is expected
Useful AI has to remember. AT0 makes memory visible, scoped, editable, deletable, and exportable.
02
Agents are starting to act
Autonomy needs approvals, logs, and limits, especially when money, health, family, or code are involved.
03
Privacy needs a place to run
AT0 is aimed at owner-controlled hardware: Mac mini, home server, NAS, Unraid node, or a dedicated AT0 Node.
Proof, not promise
AT0 is already being built across real systems.
These are the concrete pieces in the local AT0/JARVIS stack. Status labels are intentionally conservative.
Live foundation
Alpha control plane
Identity, scoped routes, route-risk classification, approval queue, RLS, rate limits, TaskGraph, kill switch, and Buddy events.
Evidence: jarvis-alpha phase status and approval gateway docs.
Working surface
Helm workspace
Unified operator workspace with Alpha authority, connector contracts, action inbox shape, and read-only domain summaries.
Evidence: jarvis-helm product and architecture docs.
Live domain
Family Vault
PIN auth, member roles, chores, calendar, emergency sheet export, RLS, append-only custody audit, and LaunchAgents.
Evidence: jarvis-family product, security, and CLAUDE docs.
In development
Financial command center
Net worth, spend, trading safety, approvals, agents, workers, caps, provenance, and isolated Postgres architecture.
Evidence: jarvis-financial product and README.
Working pipeline
Forge and Smithy
Spec-to-code development pipeline with guardrails, architecture tests, operator playbooks, and reviewed run artifacts.
Evidence: jarvis-forge docs and runs.
Prototype path
Print Copilot
AI settings driver, SCAD generation and repair prompts, visual print safety, and autonomous printing path docs.
Evidence: jarvis-print-copilot docs and prompts.
Architecture proof
One private core. Domain machines when risk demands separation.
AT0 is designed as owner-controlled infrastructure: a core control plane, bounded domain workers, and approval rails before actions touch money, health, family, or code.
Owner-controlled
AT0 Core
Identity, memory, approvals, routing, policy, logs, and the operator surface stay coordinated here.
MemoryScoped, editable, deletable, exportable.
ApprovalHuman review before high-risk action.
PolicyRole, route, budget, and risk limits.
LogsObservable runs with source context.
Family and Home
Can stay in the core or move to local hardware when schedules, devices, and household automations need isolation.
Forge and Create
Build, design, and fabrication agents can move to a dedicated machine when compute or device access needs separation.
Medical and Privacy
Sensitive context stays scoped away from lower-risk work, with review before anything becomes an action.
Approvals / observability / cost controls
Each domain reports back to the core. High-stakes workflows stop at review, and every machine can keep its own blast radius.
Founding access
Opening in deliberate waves.
Founder Circle requests get a private AI readiness checklist, onboarding priority, and first access to the AT0 Node path.
500
Founder Circle
Hands-on onboarding, readiness checklist, direct feedback loops, and early influence over the product spine.
Priority access
1,000
Private Beta
More households, more workflows, and enough usage to prove the install and domain model hold up.
Expanded pilots
5,000
Public Waitlist
A larger launch pool for referrals, community proof, and the first public rollout story.
Launch signal
One presence · every domain
Not an app. An operating layer for your life.
AT0 runs as one intelligence across the systems that actually matter. Each domain stays isolated and accountable.
Family
Your people, schedules, and home base.
Financial
Wealth, markets, and taxes.
Medical
Health, tracked and understood.
Home
Automation and the connected house.
Create
Design, build, and 3D print in one place.
Privacy
Your data and footprint, under your control.
Legal
Contracts, approvals, and evidence.
Next domain
Documents
Records, files, receipts, and manuals.
Next domain
Calendar
Custody, deadlines, travel, and reminders.
Next domainOne brain · many hands
The agents that do the work.
Specialized modules plug into the same beacon. Each has one job, done well.
Forge
Builds code from a spec.
Warden
Keeps your system secure.
Smithy
Turns ideas into specs.
Crucible
3D printing and fabrication.
Spark
The persona and voice.
Herald
Answers inbound interest and grows public signal.
More agents on the way
Continuity core
Memory that never resets.
Most AI forgets you the second you close the tab. AT0 doesn't. It remembers what matters across your people, projects, preferences, and domains. Memory stays visible: source, scope, edit, delete, and export controls are part of the model.
Built on three guarantees
Powerful because it's disciplined.
01
Remembers with controls
Memory that survives conversations, with source, scope, edit, delete, and export controls.
02
Acts within guardrails
Every action is authorized, constrained, and observable. Medical, financial, and legal moves require human review.
03
Runs where you control it
Designed for owner-controlled hardware: Mac mini, home server, NAS, Unraid node, or AT0 Node.
at0 › private runtime model
✓ core .................. memory, policy, approvals
✓ domains ............... scoped by risk and role
● financial ............ dedicated Mac boundary planned
✓ observability ......... logs, caps, kill switches
at0 › owner remains in control
Privacy is the architecture
Your data never leaves the building.
100%
self-hosted on your hardware
Per-domain
isolation with bounded blast radius
Zero
data sold, shared, or sent to ads
AT0 is not medical, financial, or legal advice. It organizes context and drafts action, then keeps high-stakes decisions behind owner or professional review.
Trust FAQ
Big-AI capability, operator-owned.
AT0 is positioned for people who want the power of modern AI without turning their private life into someone else's product.
What is AT0?
AT0, pronounced Auto, is a private AI operating layer that puts memory, agents, approvals, and domains to work around one owner.
How is it different from cloud AI?
Cloud AI is powerful but generic. AT0 is shaped around your infrastructure, your memory, your rules, and the parts of your life you choose to connect.
Does AT0 sell my data?
No. The public site uses early-access contact data to respond about AT0. The product direction is private infrastructure and no data resale.
Can it act on its own?
Yes, inside guardrails. High-stakes actions stay behind human approval so autonomy remains accountable instead of invisible.
Where does it run?
AT0 is aimed at owner-controlled hardware: Mac mini, home server, NAS, Unraid node, or a dedicated AT0 Node. The public website is separate from the private runtime.
What happens after I join?
Founder Circle requests receive onboarding priority, a private AI readiness checklist, and first access to the AT0 Node path as waves open.
Meet AT0.
Join the Founder Circle for onboarding priority, a private AI readiness checklist, and first access to the AT0 Node path.