Status & reliability

Is rasterly up? See for yourself.

No dashboard theatre. This page runs a real render the moment you open it, so the status below is live, not a green light someone forgot to flip.

Checking live…

Running a live render against the production API…

The image on the right was captured just now, by the same endpoint your integration would call. If it rendered, the pipeline is healthy end to end: browser pool, queue, and delivery.

Components
API & key servicechecking…
Rendering pipelinechecking…
Provenance & verifychecking…

Checks run live from your browser against api.rasterly.dev each time you load this page. Public daily-uptime history is being tracked and will appear here as it accrues — we would rather show real data than a wall of green we backfilled.

New, and not hiding it

rasterly launched in August 2026. We are not going to pretend there are ten years of track record behind it, because the honest version is more useful to you than a fake one.

Founder-run, direct line

The person who built it answers hello@rasterly.dev. No ticket queue, no tier-one script. Bugs get fixed the same day, most of the time within the hour.

Try before you trust

Free key in one call, 100 renders, no card. Point it at your real workload and benchmark it against your current vendor before you move a single production call.

No lock-in

The request is the same shape as Urlbox and ScreenshotOne — change a hostname and a key. If it does not hold up, you switch back in minutes.

Priced on cost

$0.90 per 1,000, extract included, no credit multiplier. We win by being cheaper to run, not by being a bigger brand.

What happens when something fails

  • Failed renders should not cost you. A call that does not return your bytes is a call we do not want to bill — errors are not a successful render.
  • SSRF is refused, not configured. Every target URL is resolved and checked before a page opens; localhost, *.local, and any private, link-local or cloud-metadata range (like 169.254.169.254) is rejected with a 403. Enforced by default.
  • We do not sit on your content. A capture is rendered, returned, and dropped. rasterly is a pipe, not an archive of your pages.
  • Timeouts are bounded. Slow targets fail fast with a clear error instead of hanging your request, so your own latency stays predictable.
  • Incidents get posted here. If the API degrades, this page is where you will see it — no spin.

The SLA

A commitment we hold ourselves to on paid plans — written plainly, because an SLA you need a lawyer to read is not a promise, it is a hedge.

99.9% monthly uptime

Target for the core API — screenshot, PDF, read, extract, template and render. That is ~43 minutes of allowed downtime a month, and we aim well under it.

Failed renders are free

An error is not a successful render. A call that does not return your bytes is never billed and never draws down your quota — enforced in the metering, not a goodwill gesture.

Same-day human support

Founder-run: hello@rasterly.dev reaches the person who wrote the code. Most issues answered within the hour, no tier-one script.

Incidents posted here

Degradation and maintenance are announced on this page. Planned maintenance is posted at least 24 hours ahead and does not count against uptime.

Service credits

If we miss the target in a calendar month, request a credit within 30 days and we apply it to your next invoice:

Monthly uptimeCredit on next invoice
99.0% – < 99.9%10%
95.0% – < 99.0%25%
< 95.0%50%

Uptime = successful minutes ÷ total minutes in the calendar month. Excluded: announced maintenance, and failures outside our control (your network, a target site being down or blocking us, or a broad upstream/DDoS event). To claim, email hello@rasterly.dev with the email on your key and the affected window. Applies to Starter/Growth/Scale; the free tier is best-effort. Need a signed SLA or higher target for procurement? We will do that on Scale — just ask.

Want it tested against your exact workload?

Send the URLs or params you render today and we will run them through rasterly and send back the outputs and timings, side by side.

Email hello@rasterly.dev or grab a free key