What Tickbase does

Schedule HTTP jobs with a URL and a schedule. Every execution fires on time — and when something breaks, you find out before your users do, with retries you can trust and logs you can audit.

Pre-launch: Tickbase is pre-launch. The multi-tenant hosted core — accounts, API keys, plan enforcement, Stripe provisioning — is built and tested; the hosted service opens at launch.

Interval + cron schedules

Schedules as plain intervals (seconds) or cron expressions (croniter). The scheduler reloads config every 30s — edit jobs without restarting.

HTTP jobs with full control

GET/POST with custom headers, basic auth, and request bodies. Per-job timeouts, retry counts, and backoff base.

Smart retries

Network errors, timeouts, 5xx, and 429 retry with exponential backoff + jitter. 4xx never retry — client errors are terminal, not retried forever.

Consecutive-failure alerts

Per-job alert thresholds: after N consecutive failed runs, fire webhook + email + SMS. State persists across restarts.

Full run history

Every attempt appended to JSONL: status, latency, HTTP code, error. GET /v1/runs with n and job_id filters; GET /v1/jobs lists your definitions.

Hosted API + CLI

Jobs are managed over REST with your tenant API key — create, list, update, delete and run-now — with run history scoped to your account. The CLI (add/remove/list/run/serve) remains for operators and self-hosting.

Honest scope: this page describes what the v1 product does today. Roadmap items are labeled as roadmap — we don't sell features that don't exist yet.
See pricingRead the docs