Brian Holt

<start of post>

I'm finally sharing what we've been working on!

For the last six months, my team has been obsessed with one goal: making database migrations feel like they don't exist. If you've ever had a deployment fail because of a schema mismatch or spent three hours manually rolling back a production change, you know exactly why this matters. It's the kind of tedious, high-stakes work that keeps developers up at night.

We built Flux to handle the heavy lifting for you. You just point it at your repo, and Flux automatically generates the migration scripts, tests them in an isolated shadow database, and flags potential breaking changes before they ever hit your main branch. It also means you get full version control for your schema; every change is tracked, every rollback is a single click, and it integrates directly with your existing CI/CD pipeline. It's honestly been a game changer for our internal workflows.

We're calling this "Invisible Infrastructure" because you shouldn't have to think about it. This isn't a tool you spend all day in—it's a tool that stays out of your way so you can actually write code.

Check out the beta here: https://flux.dev/beta

I'm really proud of what the team has pulled off. Give it a spin and let me know if it saves you a headache this week.

(The docs are still a work in progress, so bear with us as we polish the edges!)

<end of post>