Why VeloxFactory?

A lean stack without a JVM. VeloxFactory runs on a modest virtual server, on the machine next to your printer, even on a Raspberry Pi.

• check_circle Runs where PHP runs, no Java runtime and no application server.
• check_circle Fewer moving parts: fewer updates, fewer failures, lower hosting costs.
• check_circle A plain stack your team can understand and maintain.

No transaction fees, no price per document, page or API call, no expensive subscription. Whether you create a hundred documents a month or a hundred thousand, the software costs do not grow with your volume.

• check_circle No surprise invoice after a busy month.
• check_circle Your own hardware or a server you already pay for is enough.

You decide where VeloxFactory runs: on premises or with a hosting provider of your choice in the EU. Customer data and documents do not pass through a third party's cloud.

• check_circle History with automatic purge after a retention you set.
• check_circle API tokens with fine grained permissions.

VeloxFactory does not need an internet connection. It runs in isolated production networks and fully air-gapped environments, everything it needs is on your own server.

• check_circle Rendering, printing and scheduling keep running when the internet is down.
• check_circle Made for production halls and warehouses with separated networks.

From installation to the first PDF in about 30 minutes. Upload a template, the parameters are detected, one call renders the document.

• check_circle No project of several weeks before the first document.
• check_circle Parameters, fields and resources of a .jrxml are detected automatically.

If it can send an HTTP request, it can create documents: ERP, shop, warehouse management, your own software or a small script.

• check_circle REST with a bearer token, one POST with a JSON body is enough.
• check_circle Data in the request or live from MySQL, MariaDB, PostgreSQL and SQL Server.
• check_circle An MCP server with 89 tools for AI assistants.

Typically 800 ms from scan to label, over 4,000 labels per day at one customer. Fast enough for the warehouse, the packing table and the checkout.

• check_circle Queues with retries and rate limits.
• check_circle Locks against double job runs.

Every render carries a trace id. Request, response and PDF are kept in the history, so you can always answer the question "what was sent, when, and why".

• check_circle Search, re-print and re-send from the history record.
• check_circle Print, mail and scheduled jobs with status and run log.

Any layout from a 40 x 60 mm label to a multi-page report, designed in Jaspersoft Studio. You choose the output and where the data comes from.

• check_circle Output as Base64, URL or straight into a print task.
• check_circle Logos and images as shared resources, overridable per render.
• check_circle The frontend and the API offer the same functions.

Templates are standard .jrxml files designed in Jaspersoft Studio, the free designer for JasperReports, not a proprietary format. Your templates stay yours.

• check_circle Open components, runs on your own infrastructure.
• check_circle Built on a public API, nothing hidden.

From template to printer: rendering, print queue and Windows print service, Scan2Print, mailing, scheduling and history. Start with rendering and add the rest when you need it.

• check_circle No separate tools for printing, mailing and cron jobs.
• check_circle Mailing and scheduling without code.

You talk directly to the people who build VeloxFactory. Developed and supported by kiwi software & consulting in Germany.

• check_circle One contact person instead of a support portal.
• check_circle Help with templates and integration, in German or English.