New in v0.87.0: Office templates & report migration

The self-hosted document platform

Your documents.
Your workflow.
Your infrastructure.

Design in the visual editor, bring your Office files, or start with code. Generate, review and deliver documents on infrastructure you control.

Full product evaluation. Flat production licensing. No per-render fee.

PE Document workspaceSelf-hosted
Invoice generated by Pulp Engine, with customer details, line items and totals
Your template + your dataA document, ready to go.
PDFDOCXPPTX*XLSXCSVHTML
Actual PDF examples from our starter templates. View the output
Build and run on your terms.

One platform. Different starting points.

Start where your team works.

Authors get a workspace. Developers get an API. Everyone works toward the same finished document.

01

Design it visually.

Build paged reports, bind your data and reuse your brand. Give authors an editor they can make their own.

Explore authoring
02

Bring your Office files.

Use tagged Word, Excel and PowerPoint sources. Or import a legacy report and review what carries over.

Explore Office and migration
03

Build it into your app.

Call the API, use an SDK or embed the editor. Connect document generation to the tools your team already uses.

Explore integrations

Beyond the render button

A document is part of a process.

See all capabilities
  1. 01 / Create

    A first draft with a future.

    Design visually, fill an Office source or import a legacy report. Bind data, add rules and preview the result.

    Authoring tools
  2. 02 / Review

    Bring changes into the open.

    Separate drafts from published versions. Compare changes, request approval and keep review comments in context.

    Team governance
  3. 03 / Deliver

    Get it where it needs to go.

    Generate on demand or on a schedule. Send through configured delivery channels and follow the job to completion.

    Automation and delivery

For the people wiring it together

Your app calls.
Pulp Engine delivers.

A REST API with named OpenAPI contracts, maintained SDKs, asynchronous jobs and webhooks. Keep templates out of application code, without losing control of them.

  • TypeScript, Python, .NET, Java, Go and PHP clients
  • CLI for sync, validation, testing and migration
  • Embeddable editor and guided forms
  • MCP tooling and automation integration sources
Find your integration

SDK and connector publication status is listed on the integrations page.

A template, some data, a PDF.
curl https://your-pulp-engine.example.com/render/pdf \
  -H "X-Api-Key: your-render-key" \
  -H "Content-Type: application/json" \
  -d '{
    "template": "invoice",
    "data": { "customerName": "Acme Corp", "amount": 12345 }
  }' \
  --output invoice.pdf

Built to live in your environment

Keep your documents
close to your data.

Run the rendering service alongside your application. Choose storage, identity and isolation settings that fit your deployment.

Read the deployment guide
01

Your infrastructure

Docker images for AMD64 and ARM64, Kubernetes deployment guidance, and PostgreSQL, SQL Server or file storage.

02

Your access rules

Tenant boundaries, template permissions, approval workflows and configurable OIDC, SAML and SCIM.

03

Your operating model

Audit events, usage analytics, quotas, backup tooling and explicit render-isolation choices.

Predictable licensing

More documents. Same licence.

Production licences from USD $399/year. Your infrastructure costs stay yours; Pulp Engine adds no per-render charge.

See pricing

*PPTX output is beta. Office-source templates retain their native format; PDF conversion requires the optional conversion service. See availability and limits.

Your first document starts here

Make your next document a better workflow.

Explore the editor in your browser, or evaluate the full product on your own infrastructure.

Start free evaluation Try the playground Free evaluation. Commercial licence for production.