Compliant e‑invoices in every market you operate.

Deployed where you choose. Contained where it matters.

Validate against schema, business and tax rules. Exchange over Peppol. Archive as PDF/A‑3. Run it in our cloud or inside your own network when data cannot leave.

Launching February 2027

One email when we launch. Nothing else, and no list we did not tell you about.

What we are building

01 Global E‑Invoicing Issue and receive across changing mandates
02 Validation & AI Advisory Detect tax, fraud and coherence risks
03 Peppol Network Access Point, SMP and trusted delivery
04 PDF/A‑3 Engine Create archive‑ready hybrid invoices
05 Enterprise Deployment Dedicated to you, operated by us
06 Self‑Hosted Docker inside your own network boundary

Cloud, or inside your own network.

What the platform does

Validate before it is rejected

Four layers — syntax, schema, business rules, then market-specific tax rules. Every finding cites the exact rule ID and field path.

RULE
BR-CO-10 Sum of line amounts PASSED
BR-S-08 VAT category taxable PASSED
BR-45 VAT breakdown present REVIEW

Exchange over Peppol

Access Point and SMP, with AS4 delivery and the receipts to prove it.

PEPPOL NETWORK
Invoice AS4 Delivered
Credit note AS4 Delivered
Invoice response AS4 Pending

Archive as PDF/A-3

Hybrid invoices with the structured XML embedded. Human-readable and machine-readable in one file.

ISSUED DOCUMENT
Factur-X France READY
ZUGFeRD Germany READY
Peppol BIS 3.0 Belgium READY

Three ways to run it

The same platform in all three. You choose where the invoice data lives, and you can move between them without re-integrating.

Managed

We run it in our cloud. Fastest to start.

Single-tenant, in the provider and region you choose.

Your cloud (BYOC)

Your AWS, Google Cloud or Azure account. You keep the data.

Invoice data stays in your stack; the console holds control-plane metadata only.

Self-hosted

Docker Compose or Kubernetes on your hardware.

Runs inside your perimeter. Block every egress but Peppol delivery and it still validates, renders and archives.

Deployment is self-serve at launch: pick the mode, the provider and the region, and the console runs a preflight check before anything is created.