Document infrastructure
PDF infrastructure for teams that need a clearer document delivery path.
Generate PDFs from HTML, URLs, and template data with queueing, retries, delivery controls, and batch workflows built for live product and operations use.
Support transactional documents, scheduled reports, customer exports, and internal operations without owning rendering infrastructure yourself.
Built forsmall team and business workloads
Use casesinvoices, statements, reports, contracts
Operating modelRendering through an API, queueing, and batch delivery
Workflow
One document system from render request to delivered output.
Solid Relay handles the operational work that usually accumulates around PDF delivery: orchestration, retries, batch runs, and the handoff from render request to finished file.
01
Submit work
Send a render request from your application.
Send HTML, URL, template data, or scheduled job input through one API path instead of wiring custom rendering logic into every workflow.
POST /v1/render
template: invoice_v4
customer: Northwind
period: 2026-0202
Run reliably
Let the platform handle orchestration and recovery.
Requests move through queued workers with retry handling, concurrency controls, and batch support designed for ongoing product workloads.
Queued32
Rendering11
Retries3
03
Deliver output
Return finished documents without manual follow up.
Produce customer PDFs, internal reports, and batch exports through the same delivery path with predictable output and clearer visibility.
Platform
A product layer for document generation, not just a render endpoint.
Solid Relay is designed for teams that want document infrastructure to behave like the rest of their application stack: explicit, observable, and easier to operate as volume grows.
Why teams switch
Most internal PDF systems start as one render path and gradually turn into browser maintenance, queue cleanup, retry logic, storage decisions, and support incidents.
Move document generation out of ad hoc jobs and into a managed system.
Centralize rendering, execution flow, and document delivery so engineering, operations, and support all work from the same system instead of debugging separate paths across the product.
Consistent rendering without browser fleet maintenance.
Generate PDFs from HTML, URLs, or templates without owning worker orchestration, retries, or fragile browser automation.
Clearer insight into requests, failures, and usage.
Track what ran, what failed, and what is consuming capacity before document issues become customer incidents.
Support individual renders and scheduled batch runs in the same platform.
Start with a single integration path, then grow into higher volume, concurrency controls, and recurring document workflows.
Use cases
Built for the documents that customers, finance teams, and auditors actually depend on.
Best suited for document workflows that affect revenue, customer experience, or compliance.
Billing and account documents
Generate invoices, statements, receipts, payment summaries, and tax-ready exports from live application data without creating a separate internal rendering system.
- Invoices and receipts
- Statements and billing summaries
- Tax and finance exports
Contracts, confirmations, and onboarding packets
Deliver transactional PDFs at the right point in the customer journey with output consistent enough to feel like part of the product rather than an afterthought.
Reports, archives, and scheduled document runs
Support compliance snapshots, operational reports, archive bundles, and recurring document production without building separate scripts for each department.
Pricing snapshot
Start with a single workflow, then grow into production volume.
Pricing is structured to let teams validate one workflow first, then expand into higher throughput, larger documents, and more operating headroom without changing the integration model.
Commercial model
Limits are explicit: monthly volume, concurrency, request rate, and document size all scale with the plan. Most teams begin on Starter and expand from there.
Free
$0/mo
For evaluation and the first integration work.
Best when you are validating render quality, testing inputs, and proving the first document path.
PDFs50
Req/min2
Parallel1
- 3 saved templates
- 1 API key
- 3 queued batches
Starter
$29/mo
For the first live workflow and a broader rollout path.
Best when one customer or internal workflow is live and you need clearer plan limits.
PDFs2,000
Req/min10
Parallel2
- 25 saved templates
- 5 API keys
- Higher monthly volume
Professional
$79/mo
For higher throughput and delivery that uses webhooks.
Best when delivery speed, webhook callbacks, and more sustained operational headroom are required.
PDFs10,000
Req/min50
Parallel5
- Webhook notifications
- 10 API keys
- 25 queued batches
Operational confidence
Adopt it like infrastructure, not a fragile sidecar service.
Document workflows become painful when they are critical to the business but operationally invisible. Solid Relay is built to make rendering behavior clearer, failure modes easier to review, and scaling decisions less reactive.
Execution through queued workers with explicit retry handling.
Move away from brittle standalone jobs and toward a rendering path with clearer recovery behavior.
Understand what ran, what failed, and where capacity is going.
Track requests, usage, and delivery behavior before PDF issues become support tickets or missed deadlines.
Start narrow, then expand into templates, batches, and higher throughput.
Teams can integrate one workflow first, validate it in live use, and scale without replacing the model.
Next step
Put one document workflow on a path you can keep using.
Start with one render path, validate it in live use, and expand into templates, batch runs, and higher throughput only when the workflow proves its value.
Create an account and work from the docs.
Best when you already know the first workflow you want to move into live use.
Review rollout, pricing, and fit before you commit.
Useful if the workflow is critical to revenue or you want help choosing the right plan and path.