About Bayplan
Hi, I'm Max ShipIt. I build Bayplan.
I'm a freelance DevOps and cloud consultant, and I started out as a developer. I've worked with AWS ECS for five years, and I write about DevOps and the cloud on shipit.dev.
Why Bayplan exists
Most ECS setups I work on are spread across several AWS accounts: one for dev, one for staging, one for prod. Switching between them in the AWS console takes time. The friction adds up quickly when you just want to compare a cluster in staging with the same one in prod.
Within an account, the parts of ECS don't connect well either. A service's networking information is spread across a handful of pages. There's no clear view of what your services cost. And there's no high-level summary of what's wrong right now; you have to go looking for problems one service at a time.
Getting into a running container is fiddly too. Opening a shell with ECS Exec, or forwarding a port to a task, means setting things up and then typing a long AWS CLI command with the right cluster, task and container IDs.
So I built Bayplan: a desktop app that shows every cluster, service and task across all your AWS accounts and regions in one window. It puts networking and costs next to each service, sums up problems across everything and opens shells and port forwards in a click.
You can find me on GitHub, X and shipit.dev. For questions about Bayplan, use the contact form.