Introduction

Prynt is fully managed document generation infrastructure for business software. You design document templates in a visual editor, bind them to your business data with SQL, publish versioned releases and generate production-ready PDFs (and ZPL labels) by calling one API endpoint from any system. Prynt runs in the cloud, hosted in the European Union: there is nothing to install, except the optional Gateway next to databases on a private network.

How it works#

Every document follows the same path, whatever its type:

• A data source connects Prynt to a database you already use: Oracle first, PostgreSQL too.
• Datasets read the data of a document with SQL. Bind variables such as :invoiceId become template parameters.
• The template lays out the page: bands, text, tables, groups, images and barcodes, bound to dataset fields.
• Publishing creates an immutable version, promoted through your environments.
• Your application calls POST /v1/render with the template code and its parameters and receives the finished document.

Your data stays protected#

• Databases on a private network stay private: the Prynt Gateway runs next to them and connects out to Prynt, so no inbound port is ever opened.
• Credentials are written once and never shown again. With the Gateway they are encrypted for it in your browser, and Prynt Cloud cannot read them.
• Every query is read-only, with timeouts and row limits, and every query is audited. The API accepts template codes and parameters, never SQL.
• Cloud databases connect directly over TLS with certificate verification, from Prynt's published static egress IPs.

Who it is for#

Software companies and ERP vendors that ship documents to their customers, developers and system integrators who connect business systems, and IT departments that want document layouts out of application code. Developers own the data and the integration; designers and consultants own the layout.

Where to start#

• QuickstartConnect a database, design a template and render your first PDF.
• API OverviewThe render endpoint, API keys and error handling.
• ConceptsTemplates, datasets, data sources, parameters, environments.
• OracleUsers, grants, procedures and REF CURSOR datasets.

New here? The Quickstart takes about fifteen minutes.