Everything your businesses run on, part by part.
What Fleet does for each business, each server and each backup, in the order you would think about them.
Each business kept whole.
Its websites and apps, its database, its domains, its email and its backups, together in one place, on whichever of your servers it runs.
Your businesses, or your clients’. A client is a business too. Move one, close one or change one, and the others do not notice.
riversidebakery.comWordPress · hetzner-1
order.riversidebakery.comApp · hetzner-1
ordersBeside the app · included in backups
4 mailboxeshello@, orders@, jo@, sam@
Today, 03:10A second copy on contabo-2
Websites and apps
WordPress, plain websites made of files, and apps built from code. As many as the business needs, each on whichever of your servers suits it.
A database beside it
An app gets its own Postgres database on the same server. WordPress gets its MariaDB database. Both are backed up with the site and move with it.
Settings kept sealed
The keys and passwords an app starts with are stored sealed. You enter them once and they are never shown again.
Upload size, per website
Set how large a file each website accepts, from 1 MB to 1 GB. A photo site and a brochure site do not need the same limit.
Closing one is not a panic
Removing a business starts a 30-day clock you can stop. Its backups outlive it.
Starts empty, grows later
A new business can be just a name. Add its websites, domains and email when you are ready.
Servers from any provider, on one screen.
Rented on your own accounts, from whoever you like. Fleet watches them all the same way.
Any provider, one line
Paste one line on a Linux server you rent anywhere and it installs what it needs. Servers you already run come in without rebuilding what is on them.
It only calls out
The line opens nothing on your server to the internet. The server makes its own connection out to Fleet.
Every server, every minute
Processor, memory and disk, reported every minute. The last two days are kept minute by minute, and hourly after that.
A job for each server
Give each server its role: websites, builds, backup storage or mail.
Free up space
One button removes unused old images and build leftovers. Never data.
A private network between them
Your servers talk to each other over a private, encrypted network, whichever companies they are rented from.
A terminal only when you open one
A terminal on a server opens only when you open a window for it, with a code from your authenticator app. It closes itself, and every command is written down with its output.
Otherwise, a fixed list of jobs
Fleet asks your servers for named jobs, like “back this up”, “start this site” or “restore this”. Never a command.
Backups that survive a bad day.
Every night, databases included, with a second copy on another of your servers.
A backup on the same machine as the site is gone the day the machine is. So the copy that matters lives somewhere else, and the server it came from cannot reach it.
Every night, by default
Files, and databases dumped properly rather than copied mid-write. Mail and the keys that sign it are included.
A second copy, fetched by another server
Another of your servers fetches its own copy. The first server holds no key to it, so if a provider loses a server, or somebody breaks into one, the copy on the other survives.
Encrypted, if you like
Switch on AES-256 encryption. Fleet turns it on only after you confirm you have saved the key somewhere of your own.
You can see what each server holds
Every backup server lists its backups by business, and the date each is kept until. Files with no record are shown to you, never deleted.
Checked, not just taken
Archives are checked every 14 days, so the day you need one is not the day you find out.
Restore to the right place
Restoring puts a backup back on the right machine. Fleet checks it first, and asks for a code from your authenticator app.
Keep one forever
Mark a backup to keep for good, or download one with a link that works once.
Fleet backs itself up too
Every hour. The thing that knows where your backups are is backed up as well.
Email on your own domains, if you want it.
Fleet can run a mail server on one of your servers, with mailboxes and aliases on your domains. Or you keep the email you have and use Fleet for everything else.
Mailboxes and aliases
Add them per business, on its own domains. A password is shown once, when the mailbox is made.
The records, written for you
When the domain is on Cloudflare, Fleet writes the MX, SPF, DKIM and DMARC records. Otherwise it shows you exactly what to enter.
One login, one address
A mailbox cannot send as another address. Mail and its signing keys are in the nightly backup.
Running your own mail server does not guarantee every message lands in the inbox. Nobody can promise that, and we will not.
Point a domain without learning how.
With Cloudflare connected
Adding a domain to a business writes its records for you. Fleet can also add the domain to your Cloudflare account in the first place.
Without Cloudflare
Fleet shows exactly which records to enter where you bought the domain.
Certificates look after themselves
Issued and renewed automatically, and checked on the server itself rather than assumed. If one is close to running out, you hear about it first.
Move a site without losing the weekend.
One button, to a cheaper server, a bigger one, or away from a provider you have had enough of.
Cancel at any point before the switch and nothing public changes.
- 14:02CheckedThe new server has room and the web role.
- 14:03Copy built on contabo-2hetzner-1 keeps serving everyone.
- 14:06Ready for you to checkThe copy opens at the real address, in your browser only.
- 14:19Finished by youThe last changes copied. The site paused for 20 seconds.
- 14:20Database comparedEvery table matched, row for row.
- 14:21SwitchedSecure from the first visitor. The old server forwards stragglers.
01
A checklist first
Fleet checks the new server has room and the right role before anything is copied.
02
The copy is built
On the new server, while the old one keeps serving everybody.
03
You look at it
The copy opens at the real address, in your browser only, before anyone else is switched.
04
The last changes are copied
The site pauses for seconds while this happens. About twenty seconds on a real move.
05
The database is compared
Table by table, for Postgres, before the switch.
06
Switched
The certificate goes with it, so the first visitor gets a secure site. The old server forwards stragglers.
The site pauses for seconds while the last changes are copied. Not zero, and we will not pretend otherwise.
Git servers and mail servers are not moved this way.
Push the code. The site updates.
Connect an app to a repository on your own git server, and every push builds it and puts it live.
Your own git server
The code lives on a Gitea server of your own, not on somebody else’s service.
Built in a sandbox
Each build runs on a build server of yours, in a sandbox that holds no keys.
Connecting one asks for a code
Linking a repository to a business needs a code from your authenticator app, like the other risky buttons.
An assistant can build one business, once you allow it.
An assistant like Claude asks Fleet for one business and shows you a four-digit code. Nothing starts until you allow it in Fleet, it cannot see your other businesses, and its access ends within eight hours.
Inside the dashboard there is Orion, an assistant of Fleet’s own. Ask it about your fleet in plain words. Every change it wants to make waits for you to approve it.
$39 a month for the whole fleet.
However many businesses and servers you run. A one-time $250 setup, where we bring your businesses in with you. Your servers you pay your provider for directly.
Signup is by invitation while we set up each fleet with its owner. A person reads every request and replies.