Every business gets its own private copy at its own web address, with its own core engine, its own data and its own AI key. We set it up, keep it updated and look after the server.
Your address, your password, your data.
Each client runs in their own pair of containers on our server: the dashboard and the core engine. You sign in at your own address, such as jarvis.yourbusiness.com, behind your own password. Your data lives in your own volumes and survives every update.

Memory, skills, scheduled jobs and agents.
Each client has a private core engine that runs the long jobs: Tasks, Research, scheduled routines and missions. Anything it asks permission for waits in "Needs your OK". It cannot update itself and cannot be reached from outside your copy.

Your data keeps building either way.
With a working AI key J.A.R.V.I.S is fully online. Without one it drops to "Offline · slow mode": mail sync and sorting, ranking, calendar, a daily brief built by code, figures, and short chat on a local model still work. Mail, calendar and notes keep building, so adding a key lights everything up with the full history.

You pay the AI provider directly, with a monthly cap.
Each business uses its own OpenRouter key, so AI usage is billed to you at cost. You set a monthly spend limit in Settings; the arc reactor and orbs fill against it, with reminders at 80% and 100%. At the limit chat keeps working and background work pauses, with a "Raise my limit" button.

Two presses for anything that goes to a customer.
Emails, posts, quotes and payments all wait for your approval in the app. Inboxes are listed without changing anything. There is no AI customer support yet: messaging apps are you talking to J.A.R.V.I.S only. And there is no bank access, ever.

Every client runs the same core; modules are switched on per client.
New versions are released with plain-words notes and tried on our own demo first. Fixes go out straight away; new features wait for approval. Your settings, mail, notes and history are untouched by every update.

We walk through your address, the sign-in, the core engine and the approvals on a live copy.