Browse and edit data, run SQL across hundreds of databases, schedule verified backups and watch every server, for MariaDB, MySQL and PostgreSQL. Self-hosted, so your credentials never leave your servers.
$ curl -sSL https://fleetdock.dev/install.sh | sudo sh
Real screenshots from a Fleetdock install. No mock-ups.
Open any table on any server and change rows in place. Every save is journaled, so a mistake is one click to undo, even days later.
Preview shows the rows an UPDATE or DELETE will touch, before and after, without committing. Explain draws the query plan as a tree and points at the slow step.
Run a migration, a fix or a report on up to 500 databases at once, and see what each one returned, with a CSV export of everything.
Fleetdock snapshots each database's schema and shows a timeline of what changed, with a script to go back to any earlier version. Compare two databases to get the script that makes them match.
Schedule backups to your own S3, R2 or MinIO bucket with retention, then let Fleetdock restore each one into a scratch database to prove it works.
CPU, memory, disk and connections for each machine, plus live sessions and the slowest statements on every database server.
No Kubernetes, no cloud account, no sign-up. Day to day, the fleetdock command handles status, updates and diagnostics.
2 vCPU and 4 GB of RAM is enough to start, with ports 80 and 443 open. A domain is optional: the installer can give you a free sslip.io name with HTTPS.
The installer asks for a domain and an admin email, installs Docker if needed and starts Fleetdock behind automatic HTTPS. It prints your login at the end.
Add any MariaDB, MySQL or PostgreSQL server Fleetdock can reach (hosted ones like RDS too), or install the agent on a machine to create database containers there.
When databases are spread across many servers, the operations that keep them healthy stay manual, inconsistent, and invisible. Fleetdock standardizes them.
Every provision, backup, and fix is a shell session on a specific host. Knowledge lives in someone's terminal history.
Backups run from ad-hoc crontabs with no shared status. You find out a job stopped when a restore fails.
Database passwords end up in env files, chat messages, and wikis with no rotation or central control.
Moving a database means hand-assembling dump, transfer, and import steps — and hoping nothing drifts.
Fleetdock sits between running everything by hand and giving your databases to a managed cloud provider — you keep the infrastructure and gain the operations layer.
| Capability | Manual operations | Managed cloud database | Fleetdock |
|---|---|---|---|
| Where your data and credentials live | Your servers | The provider's cloud | Your servers |
| One view of every database | Spreadsheets and SSH | Per provider and region | Yes, across all servers |
| Browse and edit data | CLI or a desktop client per host | Separate tool | In the browser, with undo |
| Run SQL on many databases | Shell loops | Not built in | Fleet query, up to 500 at once |
| Backups | Cron jobs you maintain | Included | Scheduled, to your own bucket, test-restored |
| Move a database to another server | Dump, copy, import by hand | Within one provider | Backup, restore, verify in one step |
| Cost | Your time | Grows with every database | Free and open source |
Comparison reflects implemented Fleetdock capabilities. Fleetdock does not provide automatic failover or high availability.
Every day-to-day operation becomes a consistent, tracked action instead of a bespoke shell script — the same way on every server.
Launch isolated MariaDB, MySQL, or PostgreSQL instances with a generated root password, a named data volume, and a published port — as a Docker container on a connected server.
Learn moreTrack node availability, CPU, memory, disk, and connection metrics from 30-second heartbeats, plus per-instance health and a fleet-wide overview.
Learn moreRun manual or scheduled backups with each engine's native dump tool — gzipped and checksummed — streamed to S3, Cloudflare R2, or any S3-compatible bucket with retention.
Learn moreRestore from any backup through a tracked operation that verifies the artifact checksum before touching the target and reports the restored table count.
Learn moreMove a database to another instance or server with a backup → restore → verify saga — no hand-assembling dump, transfer, and import scripts.
Learn moreCreate application credentials with scoped profiles for external apps. Instance and storage secrets are encrypted at rest; public access routes through the Fleetdock Gateway.
Learn moreExpose databases to applications outside your private network through the Fleetdock Gateway — one stable port per database, CIDR allowlists, and disabled by default.
Learn moreFleetdock separates the control plane from the servers that run your databases, so you operate the whole fleet from one place without opening shells.
The central control plane. It serves the dashboard and API, tracks every operation, and stores fleet metadata in PostgreSQL.
A lightweight service on each database node. It enrolls with a single-use token, heartbeats health, and executes approved operations locally.
Your own servers. Provisioned MariaDB, MySQL, and PostgreSQL instances run in isolated Docker containers; the Manager never touches a node except through its agent.
An optional HAProxy service colocated with the Manager. It exposes stable, CIDR-gated TCP endpoints for external applications — one port per database, with config owned by the control plane.
Fleetdock Manager
Control plane · UI · API · worker
Agents enroll over a single outbound HTTPS connection and execute only approved operations on their own node.
Fleetdock holds credentials for your entire fleet, so its security model is explicit — including the boundaries it does not yet cover.
Agents register with short-lived, single-use tokens, then authenticate with their own bearer token — revocable and rotatable per server.
The dashboard session lives in an HttpOnly, SameSite=Strict cookie with CSRF protection, out of reach of page script.
Instance passwords and storage keys are envelope-encrypted with a key you control, and re-wrapped on rotation.
Backups stream to object storage through time-limited presigned URLs — agents never receive your storage credentials.
Owner, admin, operator, and viewer roles plus custom roles from a permission catalog, with scoped API tokens.
External database access routes through the Fleetdock Gateway with CIDR allowlists — disabled by default, with application credentials instead of root passwords.
Every mutating action is a tracked operation with status and history, alongside an audit log of changes.
Rotate the encryption and JWT secrets, revoke API tokens, and suspend accounts to cut off sessions immediately.
SSO/OIDC and 2FA are on the roadmap, not yet available. The agent runs as root (required to drive Docker) inside a sandboxed systemd unit. Gateway TLS is passthrough only in the current MVP. See the security documentation for the full trust model and mitigations.
Fleetdock is designed for the specific problem of operating many isolated database instances across many servers.
Manage isolated databases for every customer from one control plane.
Operate many customer database instances across multiple servers.
Provision and maintain database instances for clients.
Manage customer databases without sharing manual server access.
Offer managed database operations on customer-controlled infrastructure.
Replace scripts, spreadsheets, and undocumented procedures.
Fleetdock is Apache-2.0 licensed and runs entirely on infrastructure you control. Read the code, file issues, and follow the roadmap in the open.
A Go control plane and agent with a Next.js dashboard, released in the open.
Can't find your answer? Open an issue on GitHub; it's the fastest way to reach the maintainers.
Yes. Fleetdock is open source under the Apache-2.0 license, and you run it on your own server. You pay only for the machine it runs on.
No. Fleetdock runs entirely on infrastructure you control and sends no telemetry. Database passwords and storage keys are encrypted at rest with your own key, and backups go to the S3-compatible bucket you choose.
MariaDB, MySQL and PostgreSQL: on your own servers, in Docker, or hosted ones such as Amazon RDS or Neon that Fleetdock can reach over the network.
No. A database Fleetdock can reach directly is connected with just its address and a login. The agent is optional: install it on a machine when you want Fleetdock to create database containers there, report the machine's CPU, memory and disk, or back up databases that aren't reachable from outside.
A Linux server with Docker (the installer adds it if it's missing); 2 vCPU and 4 GB of RAM is enough to start. The one-line installer sets up automatic HTTPS. On a Mac or Windows PC it runs locally for evaluation.
Run fleetdock update. It backs up Fleetdock's own data first, then moves to the latest release. fleetdock doctor checks DNS, certificates and reachability if something looks wrong.
No. Fleetdock manages, backs up and monitors your databases, but it doesn't replicate them or fail over between servers. Keep using your existing replication setup for that.
One command installs it on your own server. Connect your first database in a minute.