Alternatives
Products that do what Underlayer does
Catch, edit, and retry failed webhooks & cron jobs
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9SJ
Hey HN, I'm the maintainer of node-cron (5M+ downloads/month), and I recently built Sidequest.js, a background job runner for Node.js inspired by Oban (Elixir) and Sidekiq (Rails). It solves some common problems I saw with libraries like node-cron: - Jobs don’t block your API: they run in isolated worker threads - No Redis or vendor lock-in: use Postgres, MySQL, SQLite, or MongoDB - Supports retries, uniqueness, concurrency, snoozing, prioritization - Comes with a CLI and a simple dashboard - Works great in monoliths and doesn’t require extra infra Quick start (no signup needed):…
2025 · docs.sidequestjs.com
- 10
- 11
- 12WF
Hello HN, We’d like to show you our project — Nohooks[0]. The aim is to add webhooks to platforms that do not natively support webhooks. We really believe many APIs can provide a better developer experience by providing webhook notifications to enable us to automate more things. Nohooks works by intelligently polling the integrated platform's APIs, determining if a change has occurred, and generating webhook events. Nohooks currently supports webhooks from Notion’s Databases, Render’s Services & Deployments, and DigitalOcean’s Droplets. We will add more in the coming days and improve the…
2023 · nohooks.io
- 13
- 14
- 15
- 16AA
Hi HN, Here's a tool I wrote for retrying fallible commands. Nothing groundbreaking here, this is a tool that's been made many times (and several have been submitted to Show HN). Though this one does have a more comprehensive feature set than most. I hope one or two people will find it useful. I wrote `attempt` for two reasons: - To have a more featureful alternative to `wait-for-it.sh` for use in Docker Compose. Specifically to apply migration scripts to a database that may not be up yet. I wanted to be able to inspect the error messages from my migration tool & retry on connection errors.…
Sep 2025 · github.com
- 17IM
Mar 2026 · github.com
- 18
- 19
- 20
- 21IA
2024 · github.com
- 22
- 23IC
In my last project, I was struggling to create and monitor cron jobs. So, instead of creating hundreds of standalone scrips and executing them with cron, I decided to turn those scripts into multiple endpoints. Next, I created a single service that I could schedule HTTP requests to those endpoints and monitor its execution. No more scripts, now everything is endpoints that I can run manually at any time I turned this scheduler service into a Micro-SaaS so you don't have to build it yourself: beew.io I know you can Schedule HTTP requests with Zapier but come on... I will not pay 50 bucks for…
2021
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →