Charts in the inbox
Mail clients run no JavaScript. A PNG renders in every client, Outlook included.
Signups for the week are in the chart below.
ChartKit Cloud
The same ChartSpec, rendered on our servers. Put the URL in an <img>, an email, a README or a PDF. No chart runtime anywhere.
Edit the spec on the right. The image and its URL update as you type, and that URL already works.
Free, no key. 120 renders / min. Free images carry a small chartkit.dev mark.
Send
No SDK. GET returns the file. POST returns JSON with the SVG or base64 PNG, plus a url.
curl -sG https://cloud.chartkit.dev/render \
--data-urlencode 'spec={"version":"1","type":"bar","title":"Signups by month","data":[{"m":"Jan","n":72},{"m":"Feb","n":98},{"m":"Mar","n":87},{"m":"Apr","n":128},{"m":"May","n":115},{"m":"Jun","n":158},{"m":"Jul","n":149},{"m":"Aug","n":188}],"encoding":{"x":"m","y":"n"},"a11y":{"alt":"Signups by month, January through August, ending at 188."}}' \
--data-urlencode format=svg \
-o chart.svgPlace
The same URL, dropped into four places that cannot run JavaScript. Nothing else changes.
Mail clients run no JavaScript. A PNG renders in every client, Outlook included.
Signups for the week are in the chart below.
Point the image at the render URL. Change the spec and the doc updates. No committed PNGs.
The agent writes the spec and hands back a URL. Nothing to render on its side.
Your report builder fetches the SVG and drops it on the page. Vector, so it prints clean.
Trust
These are the headers from a repeat GET of the signups spec on cloud.chartkit.dev. The numbers match that response.
format · w · h · scale · themeSVG unless format=png. Width and height go up to 4096. PNG scale is 1 to 4, and a PNG holds at most 4 million pixels (width × height × scale²). theme and background are query params. There is no dpr param.
one yearSame spec, same URL, cached for a year. Change one byte and the URL is a different image.
repeat GETA second GET of this signups spec returned HIT. The first request was a miss and did not send cf-cache-status.
X-ChartKit-CacheThe worker sets miss or hit for its own map, and edge when the Workers cache serves the GET.
X-ChartKit-WatermarkGET /render sets this to 1 and draws the chartkit.dev mark. A valid key on POST stores an unmarked chart at /c/<id>. The worker does not log spec bodies. Specs over 1,800 characters, and keyed renders, are stored.
X-ChartKit-Ok1 when the chart was drawn. X-ChartKit-Errors lists CK codes when it was not. X-ChartKit-Repairs counts patches. This response had 0 repairs.
This 200 does not include a rate-limit header. Over 120 renders a minute from one IP, counted per Cloudflare location, the response is 429 with Retry-After, X-RateLimit-Limit, and X-RateLimit-Remaining: 0. The ceiling is the same with or without a key. There is no public status page.
Own
Cloud runs the MIT renderer that ships in the package. The local server is the same handler, so a GET still includes the mark.
Pay
Same spec, same output. A key removes the chartkit.dev mark. The 120/min ceiling does not change.
Pricing is to come. To use Pro now, email todd@toddgarland.com.