Riverbed
Trace every API call back to the line that made it
APIs Analytics Paid
Back to archive
Belfry
Week 31Alerting that groups by cause, not by metric
Analytics Analytics
Visit site
belfry.dev
All time
About
Belfry launched in week 31 and finished at number 4. Its full listing is kept here as part of the archive.
Where Belfry fits
Belfry sits in the analytics corner of most stacks, and is aimed at teams who have outgrown doing this part by hand. It runs on Web, and is free to start with paid tiers for teams.
It is a closed-source product, so evaluate it the way you would any vendor you plan to build a workflow around.
What you get on day one
Archived listing, and final vote count preserved, no longer accepting votes. 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.
What it does
- Archived listing
- Final vote count preserved
- No longer accepting votes
Feedback 3
Feedback is public and shown to the maker.
Sign in- Mara Ellis @maraellis 2d
Been 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.
- Devin Roy @droy 3d
The plain-language summaries are the killer feature. My non-technical PM can review migrations now, which I did not expect to ever type.
- Sana Qureshi @sanaq 4d
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.