Product updates and platform changes

We've changed our company and product name from PDFRender to Saliox, and moved to a new home at saliox.com. This is a name and legal entity change only — the product, infrastructure, and team behind it are exactly the same.

• • Your API keys, account, settings, and templates are unchanged and continue to work as-is
• • Update your API base URL to https://saliox.com/api/v1 — see the API note below
• • Update any bookmarks or documentation links to saliox.com
• • Billing, plans, and pricing are unaffected

As part of the move to Saliox, /api/v1 now only accepts requests made to our primary domain, saliox.com. Requests to any other hostname pointing at our infrastructure — including the old pdfrender.io domain — will be rejected. The rest of the site is unaffected; this restriction applies to the API only. No changes are needed on your end beyond making sure requests are sent to https://saliox.com/api/v1.

The PDF generation server has been upgraded from a shared CPU instance to a 8 vCPU / 16GB Dedicated CPU stack. This eliminates CPU contention from other tenants during peak periods, resulting in faster generation times and more consistent performance under concurrent load. Puppeteer rendering, compliance processing, and image-heavy documents should all see a noticeable improvement.

Users can now generate documents from reusable JSON templates instead of only rendering public URLs or raw HTML.

• • Added template builder support in the dashboard
• • Added template-based API payload handling
• • Added starter templates for invoices, receipts, letters, and reports

Refreshed the docs layout, added clearer code examples, and improved the first-run experience across the dashboard.

Added support for expanded watermark, delivery, and storage settings on the main generate endpoint.

Fixed a timeout issue affecting some larger pages with heavier CSS and external assets during generation.

Updated job scheduling and worker allocation to improve queue handling during peak usage periods.

Customers can now configure their own storage destination for generated files and return URLs from their own bucket or CDN.

• • Added AWS S3 and S3-compatible provider configuration
• • Added custom storage path routing
• • Added dashboard connection testing for storage setup

Updated plan display and usage information in the dashboard to make limits, entitlements, and upgrade paths easier to understand.

Added PNG and JPG capture support for pages and previews alongside standard PDF generation.