A few words about Crontap

Hey Indie Hackers 👋

I’m launching Crontap, a simple way to schedule recurring API calls and webhooks without setting up servers, cron daemons, or glue code you’ll forget about in 3 months.

The idea is pretty simple:

You pick a schedule.
You add a URL.
Crontap calls it for you.

That’s it.

I built it because cron jobs are one of those boring-but-critical things that every product eventually needs:

• send a daily report

• sync data every 10 minutes

• trigger a webhook

• run a cleanup job

• ping an endpoint

• kick off a background task

• check if something is still alive

But the options always felt a bit annoying.

Either you’re managing cron on a server, dealing with cloud scheduler setup, wiring up permissions, or using a big automation tool that feels like overkill when all you really want is:

“Call this endpoint every Tuesday at 9am.”

Crontap is meant to be the lightweight version of that.

It supports cron expressions, plain-English schedules, per-schedule timezones, custom headers, JSON payloads, retries, logs, failure alerts, and integrations with tools like Slack, Discord, Zapier, Make, and n8n.

I also recently added uptime monitoring, because it felt like the same job in reverse: instead of “call this URL on a schedule,” it’s “check this URL on a schedule and tell me if it breaks.”

So now schedules and uptime checks live in the same place.

The goal is not to replace huge automation platforms.

The goal is to be the clean little tool you reach for when you just need reliable scheduled HTTP calls without making a whole project out of it.

I’d love feedback from the Indie Hackers community on:

1. Is the landing page clear enough?

2. Does the “cron jobs without servers” angle make sense?

3. What use cases would you expect to see examples for?

4. Would you use this for side projects, client projects, or production apps?

Here’s the site: https://crontap.com

Happy to answer questions about how I built it, the tech behind it, pricing, or what I’m working on next.