Pricing
Four plans, one price list. Free is 50 renders a month; Hobby is $5 for 1,000, Pro is $19 for 10,000 and Scale is $49 for 50,000. Every plan is a monthly allowance, never credits. Cancel in one click and get the unused part back.
| Plan | Price | Renders a month | About per 1,000 | Renders a minute | Cache hits a minute | At once | Watermark |
|---|---|---|---|---|---|---|---|
| Free | $0 | 50 | - | 10 | 600 | 1 | Yes, on OG images, PDFs and screenshots |
| Hobby | $5.00 a month | 1,000 | $5.00 | 20 | 600 | 1 | No |
| Pro | $19.00 a month | 10,000 | $1.90 | 60 | 600 | 2 | No |
| Scale | $49.00 a month | 50,000 | $0.98 | 120 | 600 | 2 | No |
The Free plan puts a small watermark on OG images, PDFs and screenshots. Paid plans never do. Allowances reset on the first of each month, 00:00 UTC, for everyone. "At once" is how many of your renders may run at the same time.
What counts as a render
- Counted: a successful render that was not already in the cache.
- Not counted: a cache hit, a request that fails with a 4xx or a 5xx, a timeout, or a busy answer.
- A page that answers 404 still gets a picture of the 404, and that is counted. It is what you asked for.
When you reach your allowance
Renders stop with a 402 error that says how many you used and when it resets. We never bill more, there is no metered overage, and there is no automatic upgrade: we never move you to a higher plan. You change plan only by clicking. Upgrading mid-month lifts the limit at once.
Two requests can be in flight when you hit the line, so you may end a render or two over. Those are never billed.
Cancel and refund
One click on your dashboard. The plan ends at once, you drop to Free, and the unused part of the period is refunded pro rata, rounded down to the cent. The confirmation screen shows the exact amount first. There is no retention offer and no form. Payments are handled by Polar, who is the merchant of record and deals with sales tax.
What a render costs us
Method: we measure the mean time a render takes from our own usage records over the last 30 days. We treat that as one CPU core busy for that long, and multiply by what our server costs per CPU-second (its monthly price divided by its cores times the seconds in a month). That gives the cost of 1,000 renders. The payment processor's fee comes on top and is not included.
The number is not measured yet. We publish it here, with the margin on each plan, once the service has real traffic to measure.