Introduction: what the Enterprise installation is

It is the same application as the public portal. Not a stripped-down branch, not a separate build: the same program, the same engine, the same ten tools, the same nine languages. The difference hangs on one setting:

"InvoiceApi": { "Deployment": { "Mode": "OnPremise" } }   // the default would be "Cloud"

The Windows installer writes this value itself; it is not to be changed.

Why a single setting

Everything that only makes sense in the public portal is cleared away once at that point — instead of being guessed at across twenty pages.

What OnPremise does

Area	Effect
Third-party analytics	analytics services are not integrated; the content security policy then permits only your own origin — no external host remains in it
Plan limits	every tenant counts as unlimited (invoices, seats, templates, formats, API calls). The counters keep running, they simply no longer limit anything
Billing	the payment endpoints are not registered at all; the pricing and plan pages answer with 404
ERP surfaces	SAP IDoc, UN/EDIFACT, bulk import and invoice data capture through the API run productively rather than as trial access; the “Enterprise” notice card does not appear
Funnel notices	the account prompt, the API hint and the number-range hint are hard off, not configurable
Search engines	sitemap.xml → 404, llms.txt/indexnow.txt → 404, robots.txt → Disallow: /, every page noindex
Quality corpus	off unless explicitly set — invoice contents are then not filed
Public address	the cloud default is cleared; links in email are derived from the respective request as long as the address is not set (with a warning in the log)
Sign-in	password in addition to the sign-in link. In the cloud no account has a password hash
First run	the setup page exists only here — see First run

What OnPremise does not switch off: the tools themselves

Validating, viewing, converting, creating, extracting, combining, PDF import, invoice data capture, batch processing and bulk import are all present.

What remains reachable here too

/health, /formats, /openapi/v1.json and the interactive API explorer /api-docs — served entirely from your own host, without a CDN.

The steps to a running installation

1. Check the system requirements
2. Installation on Windows
3. First run — the first administrator account
4. Adjust the configuration
5. Set up data and backup
6. Connect monitoring