Add a repo in two clicks. Ship on every push.
Connect your GitHub project in a couple of clicks. After that, every push is built and deployed automatically, with zero downtime, all on your own hardware.
Deploy a GitHub repository
Push to deploy, automatic HTTPS, one-click databases and S3 backups, all running on a server you own. It costs nothing, because your hardware does the work. We are just the control plane.
Add a service to atlas
Deploy a GitHub repository
Add a database to atlas
Add a cache to atlas
web
acme/web · main
api
acme/api · main
postgres
Postgres 16
Run Taxiway on any host: a major cloud, a budget VPS, or hardware in your own rack. Switch providers whenever you like, and your projects come with you.
The parts of a managed platform that actually matter: deploys, observability, storage and domains, all running on hardware you control.
Connect your GitHub project in a couple of clicks. After that, every push is built and deployed automatically, with zero downtime, all on your own hardware.
Deploy a GitHub repository
Your server, your rack, your rules. Taxiway runs on ARM64 and AMD64, and all it needs is Docker installed and ports 80 and 443 open. Your apps and data never leave your machine.
Name your server / production-01
DoneConnect your server
Run this command on your Linux server as root.
curl -fsSL https://setup.taxiway.cloud | sudo bash -s -- a1b2c3d4e5f6
The Taxiway agent collects logs from all your apps automatically, live and searchable. No sidecars, no pipeline to build, no need to become a DevOps engineer.
We record metrics from every app, and the server itself, 24/7, kept for up to 30 days. Set custom alerts on anything. No separate team babysitting Grafana. It works the second you deploy.
CPU
% of host vCPUs
Every app gets a free on.taxiway.cloud subdomain, so you can share a working demo instantly. Bring your own domain when you're ready. DNS and one-click SSL are handled for you.
frontend
frontend.on.taxiway.cloud
Object storage with a standard S3 API, stored on your hardware. We run and manage SeaweedFS for you behind the scenes. No AWS bill, no setup.
uploads
S3 bucket · SeaweedFS
Architecture
A control plane holds the desired state. An agent on your server makes reality match it. That is the whole idea, minus the eighteen months of learning it usually costs you.
Nobody wants to spend their time managing a database. We give you proven, tested databases you can deploy in one click, with the secrets linked straight into your app.
Relational database with automatic backups.
In-memory store for caching and queues.
Open-source, community-driven Redis fork.
Column store for fast analytical queries.
Time-series database for metrics and events.
The classic relational database, ready fast.
Document database for flexible data.
S3-compatible object storage on your disk.
Message broker for background jobs.
In development
Every other tool on this list gives you a website on a phone screen. Taxiway is getting a proper Swift app, because the moment you need to look at production is almost never the moment you are sitting at your laptop.
Not available yet. It ships when it is good.
production-01
Written with the losing rows left in. Every one of these tools beats Taxiway at something, and each page says exactly what.
A platform this good shouldn't cost you a subscription to run on hardware you already rent. Everything expensive happens on your VPS: your builds, your containers, your databases, your backups. We hold the configuration. That's cheap, so it's free.
And if you ever want rid of us, nothing breaks. Your containers keep running, your backups are already in your own bucket, and your data was never anywhere else to begin with.
Lloyd Owen
Founder · 10+ years in DevOps
Pricing
Not a free tier. Not free for three projects. The whole platform, on as many servers as you like, for nothing, because a control plane this good should not cost you a subscription to run software on hardware you already pay for.
What you get
No card. No trial clock. Bring a server and go.
Your server, and nothing else. A £4 VPS runs a surprising number of small apps. If you use S3 backups you pay your storage provider directly, because the files go to your bucket, not ours.
Because your hardware does all the expensive parts. Builds, containers, databases, log collection and backups all burn your CPU and your disk. We hold configuration and metadata, which is cheap. There is no per-container cost for us to pass on to you.
Two things, and I would rather say them here. Taxiway is not open source, so you are trusting me to keep it running. And while your containers keep serving traffic no matter what happens to us, starting a new deploy needs our control plane to be up.
Possibly, for things only companies need: SSO, audit logs, a support agreement. What is free today stays free. I am not going to build your infrastructure on a free plan and then put a meter on it.
Entirely optional, and it unlocks nothing, because there is nothing to unlock. It just means I can keep spending evenings on this instead of billable work. Sponsors get my ear first when something breaks.
The honest version, including the parts that don't flatter us. If something's not here, get in touch. I'm happy to talk specifics.
Compare with the alternativesActually free: every feature, unlimited projects, unlimited servers. The catch, stated plainly: Taxiway isn't open source, so you're trusting me to keep it going, and starting a new deploy needs our control plane to be up. Your running containers don't care either way.
Because your server does all the expensive work. Builds, containers, databases, log collection and backups all burn your CPU and your disk, not ours. We store configuration and metadata, which costs very little per user. There's no meter running behind the scenes for me to pass on to you.
Both are good, both are open source, and both need a control panel you host plus inbound SSH into every server. Taxiway's agent connects outbound only, so you never expose a port, and there's no panel of yours to patch. It's one Go binary rather than a PHP or Node app with its own database.
Your Docker containers keep running exactly as they are. Nothing about serving traffic involves us. Your database backups are already in your own S3 bucket in a standard format. You'd lose the dashboard and push-to-deploy, not your applications or your data.
No, and that's the point. The agent dials out to us over a single WebSocket on port 443. Nothing on your server listens for Taxiway, so it works behind NAT, on a home connection, or on a box with no public IP at all. The only ports you open are 80 and 443, for your own visitors.
Any server you can run Docker on: a £4 VPS, a home server, or bare metal in a rack. ARM64 and AMD64 both work. Install the agent with one command, connect your repo, and push.
It was meant to be, and it still might be. I maintain it alone, and publishing an agent that holds the Docker socket on your production server is a commitment to a disclosure process and a patch turnaround that one person cannot honestly promise right now. So it stays closed for the moment, and opens as the project grows. If open source is a hard requirement today, Coolify or Dokku are genuinely good answers and I'd rather point you at them than waste your time.
The full reasoningA native iOS and iPad app is in development, written in Swift. It's not out yet, and it'll cost nothing when it lands.
Point Taxiway at a server you own, connect your repo, and push. That's the whole setup, and it costs nothing.