Each subsidiary its history
Own system, own processes, own resistance. “Unify from the top” usually fails on weight — not on technology.
Case study · group & holdings
Monday, 8:30 a.m. The board wants Q1 figures — five subsidiaries, three ERPs, zero Excel marathon.
Group depth without data mixing.
Two years ago, “everyone on one ERP” failed. Since then the holding lives with reality: Munich on SAP, Hamburg on Odoo, Prague on legacy, two more subsidiaries in between. Each with its own history — and its own data space.
The holding CEO opens the federation board. 23 items await cross-site approval — procurement, consolidation, compliance. Nothing is mixed. The proprietary federation keeps separation, the thread is visible.
The CFO sees Q1 consolidation prepared: open items, three variances with source and reason. He approves — only then do figures land in the board report. What used to be two weeks of Excel is one look and one click.
IT leadership connected Vienna this week — new single-tenant, adapter active, SSO from group identity management. No migration project. Rollout in days, not years.
Procurement in Munich needs capacity in Hamburg. HEINI prepares cross-site approval — who sees what is fixed. 8:55 a.m. Done. Consolidation is prepared, not forced.
Separate where it matters. Connected where it helps.
5 subsidiaries3 ERPsProprietary federation Available today
heini · Monday morning
8:30
Open federation board 23 items · 5 sites
8:40
Review Q1 consolidation 3 variances explained
Procurement MUC → HAM capacity · parallel review
8:50
CFO approves figures → board
8:55
Report ready 0 Excel · 0 mixed
Consolidation prepared, not forced
Holdings need overview without disempowerment — HEINI connects subsidiaries via proprietary federation, each data space stays its own.
Roadmap: Multi-site with separate data spaces and consolidation prep is live in the enterprise tier. Direct BOM hand-over between plants via federation is in progress — what stands, stands; what comes, we say.
The starting point in a group
Why unification fails — and what still has to work.
Overview without disempowerment
The holding needs stock, cases, figures — without disempowering sites and without mixing data.
Compliance across borders
GoBD, GDPR, ESPR, supply-chain law — the auditor asks across sites. Who has the proof, and where is it?
Supply chain breaks off
Needs and BOMs stop at the group border — email, phone, manual hand-over. Friction that eats money.
Starting point
Heterogeneous is the norm.
Holdings live with SAP, Odoo and legacy side by side. HEINI starts where you stand — not with an ERP dream that takes years.
5 subsidiaries · 3 ERPs · no big-bang project.
Herzstück federation
Connected — without mixing.
Each site in its own single-tenant. Federation — a proprietary system — connects in a controlled way: roles see their own, the holding sees what awaits approval.
Separate data spaces · one approval layer.
Consolidation
Prepared, not forced.
Quarterly figures, open items, variances with reason — HEINI prepares across sites. Only what you approve flows into the group report.
Q1 today: 3 variances explained, 1 click to report.
Rollout
Site by site.
Vienna this week, next subsidiary next month — adapters, SSO, own stack. IT keeps control, the holding keeps the thread.
New site in days — not years.
Supply chain
Beyond the group border.
If a supplier or sister company also runs HEINI, needs flow more directly — from tender to machine. The more partners use HEINI, the less friction.
BOM hand-over via federation — expansion in progress, core stands.
What the group Monday looks like
Open federation board
All sites, all open approvals — one look instead of five email chains.
Review consolidation
Figures prepared, variances explained — CFO approves.
Connect next site
Single-tenant, adapter, SSO — without stopping running operations.
In depth
What the holding needs in depth.
Proprietary federation
The connection layer between subsidiaries — controlled, audit-proof, not mixed.
Single-tenant per subsidiary
Own stack, own encryption on Hetzner in Falkenstein.
Heterogeneous ERPs
SAP, Odoo, legacy — connected via adapters, not replaced.
Holding approval
Cross-site cases only on OK — with log.
Consolidation
Quarterly reports prepared — flow only after approval by CFO or holding.
SSO & RBAC
Rights from group identity management — no shadow role system.
Audit-proof log
Every step exportable — for auditors, tax audit, GDPR.
Quarterly audit packs
Across sites, reviewer-ready — enterprise tier.
Supply-chain federation
Partners on HEINI: more direct needs — expansion path communicated honestly.
Dedicated CSM
Fixed contact for rollout and adapters — not anonymous tickets.
Trust
Group depth without group weight.
Each site in its own single-tenant. Federation — proprietary system — connects without mixing. Audit-proof log across all subsidiaries, hosting exclusively in Germany.
Proprietary federationSeparate data spacesSSO · Enterprise
Let’s talk about your structure.
30 minutes on sites, ERPs and federation — Daniel Heinen leads the demo himself, no sales team in between.
FAQ
What holdings and IT leadership ask.
Must we unify our ERPs?
No. The case shows the norm: SAP, Odoo and legacy side by side. HEINI connects, does not replace.
How do data stay separate?
Each subsidiary its own single-tenant and data space. Federation connects in a controlled way — without sharing storage.
Who approves across sites?
You define roles and approval paths — holding, CFO, IT per case. HEINI prepares, humans decide.
Is federation really proprietary?
Yes. Federation is a proprietary system — the architecture for controlled connection between sites.
How fast is a new site live?
Often in days: single-tenant, adapter, SSO — no ERP migration project. Scope depends on the adapter.
What about the supply chain?
Core stands: separate data spaces, cross-site approval. Direct BOM hand-over via federation is in progress — we say so honestly.
Where is the data?
Operational data on Hetzner servers in Falkenstein, Germany — single-tenant. For AI inference on the SaaS platform, EU sub-processors with US parent companies may apply per the DPA; the marketing website (Umami) has no third-country transfer in normal operation.
Which tier?
Enterprise tier: federation, SSO, SLA, DPA, custom adapters, dedicated CSM — on request.
Your holding. Your subsidiaries. One thread.
30 minutes on your sites and ERPs — Daniel Heinen leads the demo himself.