An Evra Tool

Cron jobs that never fail silently.

Schedule recurring HTTP requests, monitor every execution and receive email alerts when jobs fail or recover.

Included with every Evra plan — alongside Rankevra, Optimevra, Promevra.

A cron job you can actually see

A crontab on a server tells you nothing until something has already gone wrong. Cronevra records every execution and tells you the moment one starts failing.

Schedule it your way

A visual builder for every X minutes, hourly, daily or selected weekdays — or write the cron expression yourself. Both compile to the same schedule, evaluated in the time zone you choose.

See every execution

HTTP status, duration, attempt number and a short response preview for every run. Filter by job, status, code or date.

Know the moment it breaks

One email when a job goes from working to failing — not one per failed run — and one when it recovers. No alert storms.

Retries that make sense

Automatic retries on the plans that include them, each recorded as its own attempt so you can see what actually happened rather than only the final outcome.

Secrets stay secret

Bearer tokens, headers and request bodies are encrypted with AES-256-GCM, decrypted only when the request is sent, and never returned to your browser after saving.

Refuses to be a proxy

Private networks, loopback, link-local and cloud metadata endpoints are blocked — at save time, at run time and on every redirect.

How it works

1
Point it at a URL
A GET or POST to any public HTTPS endpoint. Add headers, a bearer token or a JSON body if it needs them.
2
Test it first
Send the request once, right now, and see the real status, duration and response before you activate anything.
3
Pick a schedule
Visually or as cron, in your time zone. Cronevra shows the next five runs before you save.
4
Get told when it breaks
Every run is recorded. If one fails, you get an email — and another when it recovers.

One Evra plan, every Evra product

Cronevra does not have its own subscription. Your Evra plan sets your Cronevra limits, and the same plan covers Rankevra, Optimevra, Promevra too.

Starter

$39 / month

or $390 a year — 2 months free

One site, all four tools.

Choose Starter on Evra

Cronevra on this plan

10 active cron jobs
25,000 executions per billing period
Every 10 minutes
7 days of execution history
1 automatic retry on failure
15-second request timeout

Growth

Scale

$359 / month

or $3,590 a year — 2 months free

Agency-level limits everywhere.

Choose Scale on Evra

Cronevra on this plan

200 active cron jobs
1,000,000 executions per billing period
Every minute — near real-time monitoring
90 days of execution history
2 automatic retries on failure
30-second request timeout

Subscriptions are sold and billed by Evra. The same plan also covers Rankevra, Optimevra and Promevra — there is nothing separate to buy for Cronevra, and buying elsewhere in the family unlocks Cronevra at the equivalent tier automatically.

Questions

Do I need a separate Cronevra subscription?

No. Cronevra is an Evra product, and one Evra plan covers all of them. If you already subscribe through Rankevra, Optimevra or Promevra, your Cronevra limits are already set — sign in with the same account and it is there.

Is this a separate account?

No. Cronevra authenticates against the same Evra account you already have. Signing in here is signing in to Evra.

How often can jobs run?

Hourly on Free, every 10 minutes on Starter, every 5 on Growth and every minute on Scale. The floor and the execution allowance are set together, so every plan can actually afford to run its jobs at the cadence it permits.

Will it email me every time a job fails?

No. You get one email when a job transitions from working to failing, and one when it recovers. A job failing every five minutes sends one email, not twelve an hour.

Can it call an endpoint on my private network?

No. Cronevra runs from shared infrastructure, so requests to localhost, private IP ranges, link-local addresses and cloud metadata endpoints are refused — including when a public URL redirects to one. The target has to be reachable from the public internet.

What happens to my jobs if I hit a limit?

Nothing is deleted. New jobs are prevented once you are at your job limit, and executions are skipped — and recorded as skipped, so you can see it — once the period allowance is used. Everything resumes when the period resets.

Does it store my responses?

Only a short preview, capped by your plan and scanned for credential-shaped strings before it is written. Full response bodies are never stored.

What methods are supported?

GET and POST. PUT, PATCH and DELETE are not supported yet: a scheduled DELETE against a mistyped URL is destructive, and the retry logic would repeat it.