Skip to content

Fully managed document infrastructure

Design documents.Connect your data.Generate anywhere.

Design professional templates, connect them to your business databases, even behind your firewall, and generate production-ready PDFs and labels through API. Fully managed: nothing to install.

Start buildingView documentation
How Prynt works: a SQL query reads invoice data from an Oracle database into a dataset, the dataset fields are bound to a template on the Designer canvas, an API call renders the published template, and the result is a PDF invoice.
Hosting
Fully managed
Hosted in the EU. Nothing to install or upgrade
Data sources
Oracle first
PostgreSQL too; more databases and REST coming
Private databases
Outbound-only Gateway
No inbound ports; credentials only your Gateway can read
Rendering
POST /v1/render
One authenticated call per PDF or ZPL label

The problem

Your application knows the data. Prynt knows how to turn it into documents.

Documents are where business software meets customers, carriers and auditors. Too often their layout lives inside the application: tied to its release cycle, rewritten for every customer, owned by whoever last touched the code.

Prynt moves documents out of your code. Templates are designed visually, bound to your data with SQL, versioned and published, then rendered by one API call from any system.

What you no longer do

  • Hardcode PDFs in application code

    Coordinates, fonts and page breaks buried in business logic.

  • Change programs to change a layout

    A new logo or a moved field should not need a release.

  • Maintain custom Crystal Reports

    Aging report files and desktop tooling that few people still know.

  • Duplicate document logic

    The same invoice rebuilt in every product, service and integration.

  • Write per-customer HTML templates

    Forked markup for every customer, converted to PDF and hoped for the best.

Before · layout in your code

page.DrawText(order.CustomerName, x: 42, y: 118, size: 9);
page.DrawText(order.Number, x: 410, y: 118, size: 9);
foreach (var line in order.Lines) {
    if (y > 760) { page = doc.AddPage(); y = 96; }
    page.DrawText(line.Description, x: 42, y: y += 14);
    // TODO: customer 2231 wants the VAT column moved
}

After · one call, layout outside the code

POST /v1/render
{
  "template": "delivery-note",
  "environment": "production",
  "parameters": { "orderId": 5521 }
}

200 OK · application/pdf

Workflow

From database to document in five steps.

One workflow for every document type. Developers own the data and the integration, designers own the layout, and nobody waits for a release.

  1. 01

    Connect

    Register the databases your software already uses. Credentials are encrypted at rest and connections are read-only.

  2. 02

    Query

    Write SQL in the built-in IDE with a schema explorer and completion. Bind variables become template parameters.

  3. 03

    Design

    Lay out pages visually with bands, tables, groups and conditions. Drag a column onto the page and it is bound.

  4. 04

    Publish

    Validate and publish an immutable version, then promote it from development to staging to production.

  5. 05

    Generate

    Call one endpoint with the template and its parameters. The response is the finished PDF or ZPL label.

Features

Everything a business document needs.

A complete toolchain, from the SQL that reads the data to the bytes of the PDF, built for documents that have to be right every time.

  • Visual Designer

    A precise canvas with bands, rulers, guides and snapping. Real page sizes, measured in millimetres.

    bands · rulers · snapping

  • SQL Data Binding

    Datasets from SQL with bind parameters. Drag a column onto the page and the field is bound.

    datasets · parameters · relations

  • Oracle Integration

    First-class Oracle support: schema explorer, procedures and packages, REF CURSOR results.

    schemas · procedures · cursors

  • Versioned Templates

    Editable drafts, immutable published versions, rollback and side-by-side comparison.

    draft · publish · rollback

  • REST API

    Render any published template with one authenticated HTTP call, from any language.

    POST /v1/render · OpenAPI

  • PDF Engine

    Server-side rendering with embedded fonts, images and exact pagination. No browser involved.

    fonts · images · pagination

  • Dynamic Tables

    Detail rows, groups, subtotals and headers that repeat on every page the table spans.

    groups · subtotals · page breaks

  • Conditional Layout

    Show, hide or switch sections with expressions evaluated against the data of each document.

    expressions · visibility

  • Barcode & QR

    Code 128, EAN, QR, Data Matrix and PDF417, in PDF documents and in ZPL labels for thermal printers.

    1D · 2D · ZPL

  • Multi Environment

    Development, staging and production, each with its own data sources, versions and API keys.

    dev · staging · production

  • Team Collaboration

    Organizations, workspaces and roles for the developers, designers and reviewers of each document.

    workspaces · roles

  • Audit Log

    Every publish, render and permission change, with who did it, when, and the correlation ID.

    who · when · correlation ID

Developers

One API call. One production‑ready document.

Publish a template once, then render it from any language, platform or job scheduler. Your code sends data references, Prynt returns the document.

  • API keys scoped to one environment, revocable at any time
  • Errors as RFC 9457 problem details, with errorCode and correlationId
  • Parameters validated against the template before rendering
  • The PDF in the response body: nothing to poll, nothing to assemble
Read the API referenceCreate an API key
1curl -X POST https://api.prynt.it/api/v1/render \2  -H "Authorization: Bearer prynt_live_..." \3  -H "Content-Type: application/json" \4  -d '{5    "template": "invoice",6    "environment": "production",7    "parameters": { "invoiceId": 18425 }8  }' \9  -o invoice-18425.pdf
200 OKapplication/pdf
HTTP/1.1 200 OKContent-Type: application/pdfContent-Length: 48213Content-Disposition: attachment; filename="invoice-18425.pdf"X-Correlation-ID: 4bf92f3577b34da6a3ce929d0e0e4736

Data sources

Built for real business databases.

Connect Prynt to the databases your business software already uses. Oracle comes first, because that is where a large share of ERP data lives; PostgreSQL is supported too.

Native Oracle access
Tables, views and synonyms in the schema explorer; procedures, packages and REF CURSOR results as datasets.
Bind variables as parameters
Every :name in your SQL becomes a typed template parameter, validated before the query runs.
Read-only by design
Datasets only read. Connections are pooled per environment and credentials never reach the browser.
Behind your firewall
Keep the database private and reach it through the Prynt Gateway, outbound only.
Oracle documentation

Data sources

workspace · erp

Oracle Database

ERP_PROD · production

Available
host
erp-db:1521
service
ERP
access
read-only
latency
4 ms
ERP_PROD › Packages › PKG_INVOICE › GET_LINES (p_id IN NUMBER, p_cur OUT SYS_REFCURSOR)
  • PostgreSQLDatabaseAvailable
  • SQL ServerDatabaseComing soon
  • MySQLDatabaseComing soon
  • REST APIsHTTP JSONComing soon

Secure data access

Your database never has to be public.

Prynt is fully managed in the cloud. For databases on a private network, install the lightweight Prynt Gateway next to them: it connects out to Prynt, runs read-only queries locally and sends back only the results.

Outbound only
The Gateway opens a TLS connection out to Prynt on port 443. No inbound ports, no port forwarding, no VPN.
Credentials sealed for your Gateway
Your browser encrypts database credentials with the Gateway's public key. Prynt Cloud stores a blob it cannot decrypt.
Read-only, always
Only the SQL of your datasets runs, in read-only transactions with timeouts and row limits. The API never accepts SQL.
Checked twice
The Gateway repeats the read-only checks and enforces its own limits, so even a forged request cannot write.
A key that stays on your server
The Gateway signs in with a private key generated on your machine. Revoke it in Prynt and it is cut off at once.
Every query audited
User or API key, data source, environment, duration and rows for each query. Never the data values.
How the Gateway worksSecurity overview
The Prynt Gateway, inside your network next to the Oracle database, opens an outbound TLS connection through the firewall to Prynt Cloud, hosted in the EU. No inbound port is opened, the database is not exposed, and the database credentials are encrypted so that only the Gateway can read them.

Prynt Cloud · EU

Prynt Cloud

API · render engine · templates

Your network

Prynt Gateway

runs on your server

Oracle Database

read-only user · private

Ways to connect · always read-only

  • Prynt Gateway

    Recommended

    For databases on-premise or in a private network. A lightweight service next to the database; the only thing you install.

    Windows service · Linux · Docker

  • Direct connection

    For databases already in the cloud: TLS with certificate verification, reachable only from Prynt's published static egress IPs.

    Oracle TCPS · PostgreSQL verify-full

  • Least privilege, guided

    Prynt gives you the script for a read-only database user and warns you when the configured user could write.

    read-only user · privilege warnings

Use cases

Every document your software produces.

Prynt is not an invoice generator. It is general document infrastructure: the same designer, data binding and API for every page your business prints, sends or archives.

  • Invoices

    Tax-compliant layouts per company and country, totals computed from the data.

  • Delivery Notes

    Shipping documents with signature areas and barcodes for the warehouse.

  • Orders

    Purchase and sales orders, confirmations and quotes from the same data.

  • Labels

    Shipping and product labels as PDF, or as ZPL straight to thermal printers.

  • Packing Lists

    Per-package contents, weights and checks, grouped exactly as packed.

  • Certificates

    Certificates of conformity and analysis, test results and approvals.

  • Statements

    Account statements with running balances that span as many pages as needed.

  • ERP Reports

    Operational reports with groups, subtotals and charts, printed or archived.

  • Custom Documents

    Anything your business prints: if the data is in a database, it is a template.

Fully managed

One managed document service for all your systems.

Prynt runs the API, the render engine and your templates for you, in the European Union. Every application calls the same API, so a layout change reaches every system at once; only the optional Gateway runs on your side.

ERP, WMS, CRM and custom applications call the Prynt API, fully managed in the EU. The API passes the request to the report engine, which reads your databases (directly over TLS, or through the outbound-only Gateway) and produces PDF documents and ZPL labels.

Your systems

ERP

orders · invoices

WMS

shipments · labels

CRM

quotes · contracts

Custom app

anything with data

Prynt

Prynt API

POST /v1/render

  • API keys · environments
  • Template registry · versions
  • Runs · audit log

Report Engine

managed render workers

  • Datasets · expressions
  • Layout · pagination
  • Fonts · images · barcodes
  • Reads Oracle, PostgreSQL and your other databases

Output

PDF

application/pdf

ZPL label

thermal printers

Nothing to install
Design in the browser, render through the API. No servers, no upgrades, no report runtime to maintain.
Hosted in the EU
The platform and the processing of your data run in the European Union, designed around the GDPR.
Data not kept
Rows read for a document are used to render it and then discarded; only the PDFs you choose to keep are stored.
Isolated per organization
Every workspace has its own data sources, credentials, API keys and audit trail.

Pricing

Plans for every stage, from first template to OEM.

Pricing will be published before general availability. Start building today; nothing is billed until plans are announced.

Compare plans

  • Developer

    For developers evaluating Prynt and building a first integration.

    Coming soon

    Pricing before general availability

    Start building
    • Visual Designer
    • Oracle and PostgreSQL data sources
    • Prynt Gateway for private databases
    • REST render API

  • Business

    Most teams

    For software companies and teams generating documents in production.

    Coming soon

    Pricing before general availability

    Start building
    • Everything in Developer
    • Development, staging and production
    • Team workspaces and roles
    • Audit log

  • Enterprise

    For ERP vendors, integrators and organizations with strict security requirements.

    Contact us

    Tailored to your organization

    Contact us
    • Everything in Business
    • Multiple Gateways for high availability
    • Custom data retention
    • Partner and OEM terms

Start building your first document.

Connect a database, design a template and render it through the API, all in one afternoon.

Start buildingView documentation