DriftQL
Type-safe database migrations that review themselves
Rate limiting that explains its own decisions
Sandbar snapshots your container after the slow parts of the build and restores it on every pull request. Reviewers get a live URL before the CI badge finishes turning green.
Shorewall sits in the apis corner of most stacks, and is aimed at teams who have outgrown doing this part by hand. It runs on Web, and is a paid product.
It is a closed-source product, so evaluate it the way you would any vendor you plan to build a workflow around.
Snapshot and restore in under 2s, and database seeding per branch, automatic teardown on merge, works with any dockerfile. The setup is deliberately small: the maker's argument is that a tool you have to schedule a migration for is a tool you will not adopt.
Whether that holds for your team depends on what you already run. The listing below and the feedback from other makers are the fastest way to find out.
Feedback is public and shown to the maker.
Sign inBeen using this on a 40-table schema all week. The rollback generation alone saved me twice. One request: a dry-run flag that prints the SQL without touching anything.
The plain-language summaries are the killer feature. My non-technical PM can review migrations now, which I did not expect to ever type.
Works well with Postgres. MySQL support felt a bit behind, the enum diffing missed a case for me. Filed an issue and got a response the same day.