Standard cron checks once a minute and rounds everything to that boundary. Our own KiteCron scheduler ticks every second and fires jobs down to a true 1-second interval — with a live activity view and failure alerts the moment something breaks.
For a handful of jobs that don't need to be split-second
For sites running a real number of scheduled jobs
For high-volume Dhru Fusion or trading-adjacent workloads
Need a higher interval or job limit than Pro? Ask us — we can set up a custom plan.
Ordinary cron checks for due jobs once a minute. Ask it for "every second" and it either can't, or it silently rounds to the nearest minute boundary — you find out something was late when whatever was downstream times out. Our scheduler ticks every second, server-side, and fires anything due right then. Set an interval as tight as 1 second on the Pro plan and it actually runs every second, not a rounded approximation of one.
The scheduler ticks every single second and fires anything due right then — down to a genuine 1-second interval on the Pro plan, not a rounded approximation.
Watch runs land as they fire, with 24h / 7d / 30d aggregates of total runs and failures — no endless log file to scroll through.
Every target URL is checked against private, loopback and cloud-metadata addresses, both when a job is created and on every single run.
Paste 30–50+ cron URLs at once and create them all in one request, at the interval and alert settings your plan allows.
Pick the interval and job limit you need, then order through our billing system — your login for cron.hostinap.com is set up right after.
Paste a URL to call on a schedule (or just log a heartbeat), pick your interval, and set your failure alert thresholds.
Runs land in your live activity view every second. If something breaks, you hear about it right away — not after a client tells you.
Standard cron only checks for due jobs once a minute, so an "every second" schedule either can't run or gets rounded to the nearest minute. Our scheduler ticks every second server-side and fires anything due right then.
Each job either calls a URL (a webhook / HTTP request) or logs a heartbeat message. Webhook jobs are ideal for triggering Dhru Fusion syncs, keeping an endpoint warm, or pinging any HTTP service on a schedule.
Every job tracks consecutive failures. You get an in-app notification and an email after a set number of failed attempts, plus Telegram alerts on Growth and Pro when a job has been failing continuously for a set number of minutes.
Yes, on the Growth and Pro plans. Paste one URL per line and we create them all in a single request, at the interval and notification settings you choose, respecting your plan's job limit.
Job URLs are validated against private, loopback, link-local and cloud-metadata addresses (SSRF protection), both when a job is created and on every run.
Yes, any time — move from Starter to Growth or Pro as your job count or timing needs grow, and we'll adjust your interval and job limit accordingly.
