EU-hosted rendering for sensitive documents
Rendering sits closer to sensitive data than teams expect: invoices, receipts, reports, certificates and customer exports all flow through an HTML-to-PDF or URL-to-PNG call. MOJAQ processes renders in Helsinki, with no US transfers and a DPA included, so document content never leaves Europe. For products serving European customers, rendering is part of the data path, and keeping that path EU-hosted makes procurement straightforward.
POST html or url, get PDF or PNG
The API is deliberately direct: send raw HTML when your app already builds templates server-side, or a URL when you want to capture an existing page or dashboard. Choose pdf or png and receive the bytes. No headless-browser fleet to run, no queue of one-off scripts.
curl -X POST "https://api.mojaq.com/v1/render" \
-H "x-api-key: $MOJAQ_API_KEY" \
-H "Content-Type: application/json" \
-o invoice.pdf \
-d '{"format":"pdf","html":"<h1>Invoice</h1><p>Total: EUR 120.00</p>"}'Rendering inside a consolidated stack
A product that generates PDFs usually also needs error tracking for failed jobs, analytics on document pages, uptime on the render endpoint and realtime updates when async jobs finish. With MOJAQ, render is one capability of a six-tool EU-hosted platform behind a single API key, so the rendering you ship is already wired into the rest of your observability.
Questions
What can I render?
POST either html or url to /v1/render and receive a PDF or a PNG.
Where is my data processed?
In Helsinki, Finland, in the EU, with no US transfers and a DPA included.
What does it cost?
Free during the open beta, with no fixed end date.