Manufacturing in 2026 means simultaneous demands: Industry 4.0 transformation, NIS2 compliance (manufacturing of critical products is in scope), edge compute at production sites, AI-driven quality control, and increasing sovereign-cloud requirements for industrial IP. The architectural answer is a coherent platform that runs at HQ, regional sites, and production-floor edge — under one operational model.
Ænix builds platforms for manufacturing organizations across the EU, DACH, and Central Asia.
Pairs with: Ænix Private Cloud Platform — multi-DC + edge architecture for industrial IT/OT, built to support NIS2 for critical-product manufacturing, air-gap support for OT networks.
What manufacturing teams come to us for
- Edge cloud at production sites — Industry 4.0 workloads close to machinery
- NIS2 readiness — manufacturing of critical products is in scope
- Sovereign cloud for industrial IP — design data, formulations, supply-chain data
- AI workloads — quality control, predictive maintenance, supply-chain optimization
- Hybrid: cloud for analytics, edge for operations
Why manufacturing architecture is different
- Edge compute is core, not optional — production-floor latency requirements
- Long depreciation cycles — manufacturing equipment lasts decades; platform must work with multiple hardware generations
- OT/IT convergence — operations technology meeting information technology
- Long retention — quality, traceability, regulatory data with multi-decade requirements
- Industrial IP protection — design data and formulations have higher confidentiality than typical enterprise data
Cozystack pattern for manufacturing
- Multi-site operations: HQ + regional + production-floor edge under one platform
- Air-gapped deployment for the most sensitive workloads (industrial IP)
- Multi-tenant for cross-BU and joint-venture separation
- AI infrastructure for quality control and predictive maintenance
Where the platform sits in the Purdue model
The platform lives at Levels 3 and 3.5 — site operations and the DMZ — and does not reach down into Levels 0 to 2. Controllers, PLCs, SCADA and the safety systems stay exactly where they are, on their own network, under their own change control. What runs on the platform is the layer above: MES and historians, OPC-UA collectors and unified-namespace brokers, quality-inspection inference, the data pipeline out to the corporate level, and the VM-packaged industrial applications the vendor supports on one specific OS.
The IEC 62443 framing follows from that placement: the platform is one or more zones with defined conduits into the OT network, so segmentation is a design property rather than a firewall exception list. Cilium network policy defines the conduits, Tenant CRD boundaries separate a line, a site or a joint-venture partner, and the whole thing runs air-gapped where the site security concept requires it. Component-level certification for the industrial devices remains the device vendors’ obligation — that is not something an infrastructure platform can grant.
What the floor does when the uplink dies. This is the question that decides the architecture, so the answer should be plain: a site cluster keeps running. Control never depended on the platform in the first place, because it lives below it. The site’s own workloads — the historian, the local inference for inspection, MES functions running on site — keep serving from local storage, with their state replicated inside the site rather than to headquarters. What stops is what should stop: replication upward, central dashboards refreshing, cross-site aggregation. When the link returns, buffered data drains and the site resynchronizes. Production does not wait on a WAN circuit or on a control plane in another country, which is also why a hyperscaler edge service is a poor fit for a factory.
Companies running platforms built with Ænix
Hosting providers running Ænix Public Cloud Platform in production
Hosting providers running Ænix Public Cloud Platform in production. No manufacturing customer is named. The closest written-up deployment with the same structural pattern — multi-site, tenant-isolated, operated by the customer — is the sovereign public cloud case study.
- Data sovereignty — industrial IP protection
- NIS2 compliance — critical-products regulatory
- Sovereign AI — AI on industrial data
- Cozystack
Ænix created Cozystack (CNCF Sandbox project) and co-maintains it with maintainers from other companies. On top of it we offer three platforms — Public Cloud, Private Cloud and AI.