Engineering notes
How it actually works.
Taxiway is written in Go by one developer, and these are the internals in the detail I would want if I were the one evaluating it. Real protocol frames, real failure modes, real gaps.
Why Taxiway isn't open source yet
It was meant to be, and it still might be. The honest reason it is closed today is not that closed source is safer, it is that I maintain it alone and cannot yet staff what publishing it would commit me to.
Read itHow Taxiway handles backups
A database dump goes from a container on your host, straight to a bucket you own, over a connection we are not part of. We only ever learn that it happened.
Read itHow Taxiway deploys without dropping a request
A container swap looks atomic and is not. Here is the exact window where a Traefik pool serves a dead backend, why labels cannot close it, and the retry middleware that does.
Read itHow Taxiway connects to your server without SSH
Every other self-hosted platform opens a port on your server and connects in. The Taxiway agent dials out over one WebSocket, and nothing on your machine listens. Here is the whole protocol, frame by frame.
Read itStart deploying in minutes.
Point Taxiway at a server you own, connect your repo, and push. That's the whole setup, and it costs nothing.