An assistant can build one business, once you allow it.
If you build or change your sites with an assistant like Claude, Fleet lets it in to one business, for up to eight hours, once you approve its four-digit code.
You give the order. The code is the gate. You decide how far it goes.
It asks first. You say yes in Fleet.
01
You ask for something
In plain words, in the chat you already use. "Add a Christmas pre-order page to the bakery site."
02
It asks Fleet, and shows a code
The assistant asks for one business and shows you a four-digit code. The request expires in 10 minutes if nobody allows it.
03
You allow it in Fleet
Check the code matches, choose how far it can go, and press Allow. Nothing starts before that.
04
It works, then it stops
On that business only. Its access ends within eight hours, or the moment you revoke it.
You, to your assistant
Add a Christmas pre-order page to the bakery site.
Your assistant
I have asked Fleet to let me build Riverside Bakery. Approve it with this code:
4 8 1 7
A chat wants to build Riverside BakeryOnly this business. Ends within eight hours. Code 4817.
AllowLook, build, or everything. You choose.
When you allow it, you pick one of three. Start with look if you only want it to answer questions about a business.
Look
It can see how the business is set up. It changes nothing.
Build
It can build and deploy the business’s websites and apps.
Everything
The rest of what an assistant can do on that business as well. Still only that business.
It touches one business, and you can see everything it did.
One business only
It cannot see your other businesses, let alone change them.
Nothing saved on your computer
It pushes code through Fleet, so no password or key is saved on the computer it runs on.
An app gets its own key
An app can be given a sealed key to exactly one repository, so nobody has to copy a code-host token around.
Everything is in your log
What it asked for, what it did, and what was refused, in the same activity log as everything else.
It ends by itself
Within eight hours. Tomorrow it has to ask again, and you have to allow it again.
One button revokes all
Change your mind and every assistant’s access ends at once.
Ask Fleet itself. Every change waits for you.
Orion is an assistant built into the Fleet dashboard. Ask it about your fleet in plain words: which server is busy, when a business was last backed up, what an alert means.
Looking needs no approval
Asking, looking things up and explaining them happen straight away.
Every change is a card
When Orion wants to change something, it shows you a card saying what and where. Nothing happens until you approve it.
Your own key, your own budget
Orion uses your own AI key, and you set a monthly budget for it.
On your phone too
Orion is on Telegram as well, so you can ask from your phone. Changes still wait for you to approve them.
If you already build with Claude.
Fleet connects to Claude Code and the Claude desktop app, and gives the assistant 28 tools for working on a business.
Create a business, add a website, a database, a domain or a mailbox, connect a repository and deploy from it, take a backup, or move a site and follow the move. Each one is limited to the business you allowed, at the level you chose.
Code is pushed to your own git server through Fleet, then built on a build server of yours in a sandbox that holds no keys. An app’s settings, like its keys and passwords, are stored sealed.
$39 a month for the whole fleet.
Assistant access is included. An assistant subscription is yours, and only if you want one: Fleet works without it.
Signup is by invitation while we set up each fleet with its owner. A person reads every request and replies.