Native Typst. Invoices & Factur-X in <6ms on 96% less compute.
If you use an AI coding assistant like Claude Code, Cursor, or GitHub Copilot, you can add sub-millisecond PDF generation to your app in minutes using agent skills.
Edit live JSON variables on the left. Watch the local Rubrol engine recompile vector SVG in real time. Download certified ISO 19005-3 PDF/A-3b & ISO 19005-2 PDF/A-2b binaries instantly.
Legacy document generation relies on headless browser virtualization. Spawning Chrome or Gotenberg instances requires 250MB resident memory per worker, unpredictable GC pauses, and 2,000ms+ render latencies. Rubrol embeds a native vector layout engine directly into your process or sidecar, compiling production PDFs in under 6 milliseconds with absolute mathematical determinism.
Every invoice generated via Puppeteer spins up a full WebKit/Blink layout engine, executing JavaScript, evaluating CSS cascades, and allocating huge DOM node trees before rasterizing to print media.
Rubrol compiles structured documents into native vector PDF/A-3b, PDF/A-2b, and SVG. Zero browser overhead, zero Node.js bridging, and native ISO 19005-3 & ISO 19005-2 compliance built directly into the binary.
| Vector Spec | Chromium / Puppeteer | Rubrol Sidecar |
|---|---|---|
| Compile Latency | 2,400ms | 5.8ms |
| Memory Footprint | 250MB | 24MB |
| Max Concurrency | 40 req/s | 1,200 req/s |
| PDF/A-3b & Factur-X (ISO 19005-3) | Requires 3rd party CLI | Native Zero-Copy |
When processing 200,000 monthly invoices, running headless browser clusters drains tens of thousands of dollars in AWS Fargate and CPU allocations. By reducing compute times by 96% and shrinking RAM from 250MB to 24MB, Rubrol amortizes its cost within days.
Calculate Your Cluster SavingsDuring high-volume month-end billing cycles, generating 300,000 corporate invoice runs regularly caused V8 memory leaks and pod evictions. Rubrol lowered our 99th-percentile response time from 2,400ms to 5.8ms while reducing compute overhead by over \$180,000 annually.
Rubrol replaced our 16-pod Chromium cluster with a single sidecar. Our p99 latency dropped from 2,400ms to 5.8ms while completely eliminating out-of-memory container restarts during end-of-month billing cycles.
Deploy as a microsecond sidecar in Kubernetes, run serverless via Docker, or link natively into Python, Node, Go, and Rust via REST or Unix sockets.
Runs alongside your application containers with zero external database or Redis dependency. Pure in-memory compilation.
Automatically packages syntactically validated Cross-Industry Invoice XML directly into the PDF/A-3b catalog stream.
The layout engine guarantees identical pixel-level layout and kerning across any architecture or cloud provider.
Written in memory-safe compiled Rust. No V8 garbage collection storms, no lingering zombie Chrome renderer processes.
No marketing fluff. Brutalist engineering breakdowns of why legacy Chromium breaks under European e-invoicing laws, and the exact code to fix it before the 2026 mandates hit.
Standard Stripe PDFs fail French and German B2B laws under EN 16931. Learn how to plug Rubrol into your Stripe webhook to inject compliant XML and ISO 19005-3 PDF/A-3b in under 160ms.
An autopsy of why Chrome Skia fails ISO 19005-3 catalog attachments and drains AWS compute budgets with memory leaks, plus the modern Typst replacement architecture.
Mustangproject is the reference German ZUGFeRD tool, but deploying a heavy JVM in Kubernetes triggers OOM kills and cannot render visual documents. Here is the Rust alternative.
Decades of remote code execution CVEs, AGPL-3.0 licensing traps, and zero EN 16931 validation. How memory-safe Rust eliminates PostScript attack surfaces entirely.
Gotenberg requires periodic browser killing to survive memory leaks and consumes 2GB-4GB of RAM per pod. Why high-throughput billing systems drop Chromium for 5.8ms Typst compilation.
Turnkey European EN 16931 compliance backed by automated Schematron validation. Generate audit-ready electronic invoices and regulatory receipts directly in your service without foreign EDI toolchains.
View Compliance SuiteOpen-source core under LGPLv3. Scale with production-grade financial templates and enterprise compliance validation. Flat transparent billing.
Open-source vector engine for local CLI development & Docker evaluation.
Annual commercial license for SaaS startups & high-throughput billing systems.
Turnkey EU compliance suite with certified EN 16931 & Schematron validation.
Just like Sidekiq, Rubrol Community is 100% free and open source under the GNU Lesser General Public License v3.0 (LGPLv3). You are free to run it locally, inspect the source, and use it in your development infrastructure without paying a dime.
Free forever for local development, Docker evaluation, CLI scripts, and open-source projects. You can dynamically link or invoke the sidecar without having to open-source your proprietary business code.
Replaces the LGPLv3 with a traditional commercial agreement for production SaaS deployments. Unlocks unlimited execution, turnkey EU Factur-X / Schematron verification, and private GitHub repository access.
Rubrol operates on the transparent Sidekiq commercial open-core model. Everything you need to know about subscriptions, private template vaults, and commercial rights.
Rubrol Pro and Rubrol Enterprise are commercial extensions and licensing agreements for the Rubrol engine. They provide commercial SaaS rights that replace the GNU LGPLv3, private GitHub template vault access, cryptographic 1-year offline license keys, turnkey European e-invoicing compliance (Enterprise), and direct developer support.
We do not offer pre-sales sales demos or trial keys. Rubrol Community is 100% free, open-source, and available on GitHub under GNU LGPLv3 for evaluation and local development. If Rubrol works for your architecture, you can purchase an annual subscription to Pro or Enterprise. If you are not satisfied with the result, write to support@rubrol.com within 14 days and we will issue a full refund.
For Rubrol Pro ($1,800/yr), pricing is flat and transparent with zero discounts or promotions. For Rubrol Enterprise ($4,800/yr), multi-year commitments or custom cluster volume agreements are available for high-throughput organizations. Email enterprise@rubrol.com for custom quotes.
The open-source core is licensed under the GNU Lesser General Public License v3.0 (LGPLv3). Rubrol Pro and Enterprise are commercial licenses that replace the LGPLv3 with a traditional proprietary agreement for production SaaS deployments, removing open-source linking obligations.
Every organization running Rubrol in production for commercial SaaS applications must purchase an annual subscription ($1,800/yr). There is no limit to the number of Docker containers, Kubernetes pods, CPU cores, or developer machines used by that organization. Your subscription renews automatically each year.
Every organization deploying Rubrol for European e-invoicing compliance (EN 16931) must purchase an Enterprise subscription ($4,800/yr). It includes certified ISO 19005-3 PDF/A-3b container generation, embedded Factur-X / ZUGFeRD 2.2 XML, built-in Schematron semantic validation (XRechnung 3.0), French Chorus Pro and German DIN 5008 templates, dual vault access (rubrol-pro-vault + rubrol-enterprise-vault), 2025-2028 regulatory updates, and priority Slack/email support.
You can purchase in seconds via Stripe Checkout:
• Buy Rubrol Pro ($1,800/yr)
• Buy Rubrol Enterprise ($4,800/yr)
Enter your GitHub Username during checkout. You will automatically receive an invitation granting access to the private template vault, and a signed 1-year cryptographic license key (RUBROL_LICENSE_KEY=RBL-LIC-...) will be issued immediately.
Yes. Purchase a Rubrol Enterprise subscription and email support@rubrol.com. We will cancel your existing Pro subscription and prorate the unused balance back to your credit card immediately.
We email you an automated reminder one week before annual subscription renewal. If your card cannot be charged, Stripe retries 3 times over a 7-day period. If payment continues to fail, your subscription is canceled, private GitHub vault repository access is revoked, and your offline license key will not be renewed upon expiration.
The standard commercial license covers your organization's own SaaS infrastructure and internal servers. If you need to distribute Rubrol binaries or containers embedded directly inside an on-premise software appliance delivered to external third-party customer hardware, contact enterprise@rubrol.com for an OEM Appliance License.
Licenses are not transferable between different corporate entities. You can transfer a license between employees or GitHub accounts within the same organization by emailing support@rubrol.com with your Stripe customer email.
Your purchase provides private GitHub vault repository access and an offline cryptographic license key. The license agreement requires you to keep these access credentials confidential. Do not commit your license key to public git repositories or public container registries.
Yes. Your developers and CI/CD runners require the RUBROL_LICENSE_KEY environment variable to compile production documents without evaluation limits. Store it securely in your secret manager (e.g. AWS Secrets Manager, GitHub Actions Secrets, HashiCorp Vault, Doppler, or local .env).
Ensure your environment variable RUBROL_LICENSE_KEY starts with RBL-LIC-. Run rubrol license verify from the CLI or inspect container logs on startup. If the key has expired or the signature was modified, the engine will output a clear error message indicating whether the token was malformed or expired.
Yes, up to 14 days after purchase. If Rubrol does not fit your infrastructure or workload, write to support@rubrol.com and we will refund 100% of your payment.
Rubrol Pro is credit card only via Stripe. For Rubrol Enterprise, annual invoicing with payment via ACH, wire transfer, or corporate purchase order is available for qualified corporate accounts. Contact enterprise@rubrol.com to arrange an invoice.
If an unfamiliar charge appears on your card statement, please contact support@rubrol.com before initiating a bank dispute. Disputes result in immediate automated suspension of license keys and vault access. We resolve billing issues and refunds quickly and politely.
Rubrol runs 100% locally within your own Docker containers, Kubernetes pods, or bare-metal servers. Customer documents, invoice data, and PII are processed entirely in memory and never leave your infrastructure. There are zero outbound document telemetry calls, zero third-party analytics scripts, and zero cloud dependencies.
Deploy Rubrol as a Docker sidecar in your Kubernetes pod or VPC. Send JSON, receive compliant PDF/A-3b documents with zero cloud data transmission.
POST http://localhost:8080/v1/render