7:04 am.
Before your
laptop opens.
Every order stuck, every payment failed, every refund overdue — and what it already did about it. Then it gets on with the rest: builds your pages, fixes your SEO, runs your Meta ads. A full technical team, in the chat app already on your phone.
A full technical team in your WhatsApp
A developer, an SEO lead, a marketer and an ops lead that answer in seconds and keep working after you log off. Tell it what you want in a text or a voice note. Underneath, it is Claude Code with a shell, files and a real browser, running on our servers.
Builds and
edits your site
“Build a landing page for the fall collection.” New pages, theme edits, sections and fixes, done on your Shopify store, and it tells you what it changed.
Fixes your
search
“Why aren’t our bestsellers ranking?” Titles, meta descriptions, alt text, broken links and thin collection copy — found, fixed and reported back.
Runs your
Meta ads
“How did yesterday’s ads do?” Reads Ads Manager, flags what is losing money and drafts new creatives. Any change to a budget waits for your tap.
Clears the
morning queue
The 7:04 brief: stuck orders, failed payments, overdue refunds, and what it already did about each. Carrier traces opened, replies drafted.
Knows your
numbers
“What sold last week, and what’s about to run out?” Sales charts, stock warnings and a weekly report, from your own store data.
Answers to
your voice
Voice notes, photos and PDFs. Talk to it from the warehouse floor like you would to Jarvis; it remembers your store across every conversation.
It runs without you
Schedules written in a sentence, not in cron. The brief arrives because the night ended, not because you opened an app — and anything that touches money waits for your yes.
Trust is earned, so it starts read-only
For the first 14 days it changes nothing. It tells you, every morning, what it would have done. Then you turn it on — and money still waits for your tap.
Every action is logged with a timestamp. File changes are snapshotted before they happen and can be rolled back. If the agent issues a refund you did not approve, we reimburse it, up to three months of your subscription. The source is public under the Elastic License 2.0, so you can read exactly what it will and will not do before you give it anything.
Your own instance
One Linux account, one daemon, one database, its own scoped credentials. We provision it, keep it patched and keep it running, and we pay for the model. You talk to it.
$ daemon health • Telegram: connected • WhatsApp: up + linked • Model: claude-opus-5 (effort=max) • Schedules: 40 · Workflows: 3 • Backups: nightly, 14 kept # real output from the instance # this page was built from
Your instance is yours: its own account, its own database, its own credentials, and no other customer can read it. Cancel and we hand you the data and delete ours.
Everyone else sells you a builder
This one shows up already knowing your store, and it messages you first. One bill: model usage is included, usage is counted in jobs rather than tokens, and there is no overage line — a heavy month is a conversation, never a surprise.
Operator
Start hereOne store. The 7am brief, every morning, before you open the laptop.
- Up to 50 jobs a day, unlimited chat
- Model usage included — one bill
- Slack, WhatsApp or Telegram, 3 seats
- Site edits, SEO and Meta ads, not just orders
- Read-only for 14 days, then approve-first on money
Ops Team
One store, more of it delegated, and someone building skills for you.
- Up to 150 jobs a day, unlimited chat
- The strongest model at high effort
- 8 seats, shell jobs, HTTP triggers
- Custom skills built for your store
- Priority response, same day, named contact
Multi-Store
A portfolio, or an operator running several brands from one phone.
- Dedicated server, 4 vCPU / 8 GB
- Up to 500 jobs a day, 20 seats
- Any model, maximum effort
- One instance per store, one chat to you
| Name | Price | What it does |
|---|---|---|
| Extra seat | $25/mo | One more person on the allowlist. |
| Second store | $400/mo | Another store on Operator or Ops Team. |
| Dedicated server | $150/mo | Your own box instead of a shared host. |
| GPU voice | $200/mo | Cloned voice replies and large-model transcription. |
The questions with awkward answers
What does it actually cost to run?
The price on the page. Model usage is included and we provision the key; you never open an account anywhere else and never see a token. Each plan is described in jobs a day, and the daemon enforces a daily spend ceiling underneath that. If a runaway job burns through it, that is our cost, not yours.
How do you compare to hiring, an agency, or Zapier?
A VA costs about $2,200 a month loaded, sleeps, and leaves. A developer, an SEO freelancer and an ads agency bill separately, by the hour, and answer tomorrow. Zapier and n8n fire a rule or they do not, and the day something unexpected happens is the day they do the wrong thing quietly. This is one agent that does all of it, already running on your store, and it opens the conversation.
If you would run Claude Code yourself: this is the same agent, given somewhere to live. It does not stop when you close the laptop.
Is it really a whole technical team?
For the work a store actually hands out, yes: new pages and theme edits, SEO fixes, reading and adjusting Meta campaigns, order operations, the weekly numbers. It does the work itself, in your store and your ad account, and tells you what it changed. Anything that spends money or talks to a customer waits for your tap.
It is not a brand designer or a strategist, and it will tell you when a job is beyond it rather than bluff.
Is it sandboxed?
No, and we would rather say so than sell you the word. Three things stand in for it. A permission gate blocks destructive commands, credential writes and private-key reads. Anything that touches money or one of your customers — a refund, a price, a payout, an ad budget, a message — waits for your tap and is denied if you do not answer. And for the first 14 days it is read-only: it tells you what it would have done and changes nothing.
An agent that acts on your behalf can still make mistakes on your behalf. Give it a scoped staff account, never your password.
Which chat apps?
Slack, WhatsApp or Telegram. In Slack it answers DMs and @-mentions in the thread, and an approval is two buttons in your DM. WhatsApp runs on a number we help you set up — never your main business line.
Where does my data live, and who can see it?
In its own Linux account on our server, with its own database and its own credentials. Other customers cannot read it. Anthropic sees the content of each turn, under a key dedicated to your instance. Backups run nightly and fourteen are kept. Cancel and we export it to you and delete ours.
Who is behind this, and who answers at 2am?
One person: Sahil. He builds it, provisions it, and is the one you message when something breaks — and it has been running his own store in production for a year. That is a strength at this size and a limit past it, which is why there are three prices and not a self-serve funnel. Timezones are real: response is same business day on Operator, same day on Ops Team.
The source is public. Why pay?
So you can read every line before you hand it a key — that is the point of publishing it. The licence lets you run it yourself, unsupported, and we will not stop you. What you pay for is the machine that stays up, the model bill, the WhatsApp bridge that gets re-linked when it drops, the nightly backups, and a person who answers.
Can I cancel?
Any time, effective at the end of the period you paid for, with a 7-day money-back window on a first subscription. A failed payment drops you to smaller limits after a grace period rather than stopping the agent. Nothing is deleted.
What is not built yet?
No web dashboard, no single sign-on, no roles, no shared team memory, no SMS or email channel yet. No models other than Claude, because the agent is Claude Code. We list these because a feature grid that quietly implied them would be a lie, and you would find out in week two.