Deployment Options
IronFlock supports three deployment models. Every model delivers the same platform capabilities — app management, dashboards, data collection, AI services, and remote access — but differs in where the infrastructure runs and who manages it.
| Cloud | Appliance | Private Cloud | |
|---|---|---|---|
| Hosting | IronFlock cloud | Pre-configured box on-site | Your DMZ / VPC |
| Target user | General | Machine manufacturers / OEMs | IT departments with Kubernetes expertise |
| Device connectivity | Internet required | Local network only | Local network only |
| Infrastructure setup | None | None — ships ready to use | Customer provisions K8s cluster |
| App Store | Full access | Synced from online store | Synced from online store |
| System updates | Automatic | Manual | Manual |
| AI services | Included | Requires LLM API access or custom model | Requires LLM API access or custom model |
| App development (AppStudio) | Multi-account | Single master account | Multi-account |
| Acts as edge device | No | Yes | No |
Choose Your Deployment
IronFlock Cloud
The default, fully managed deployment. Sign up, flash a device, and start building. No infrastructure to install or operate. The right choice for any project where devices have internet access and there are no data-residency restrictions.
IronFlock Appliance
IronFlock in a box. A pre-configured, self-contained box that ships ready to use. Designed for machine manufacturers and OEMs who want to deliver IronFlock together with their machines. Plugs into the local network — no DMZ, no VPC, no Kubernetes required. Doubles as both the platform server and an edge device.
IronFlock in Private Cloud
The enterprise deployment model. Run the full IronFlock system in your own DMZ, VPC, or on-premises datacenter. Designed for organizations with strict data-residency, regulatory, or air-gap requirements — classified environments, industrial plants, and compliance-driven industries (EU Data Act, NIS2, CRA, IT-SiG, KRITIS).
Benefits for App Distributors
All three deployment models follow the same separation of concerns. IronFlock handles all infrastructure and IT complexity — app distributors focus exclusively on their domain expertise.
What IronFlock Handles
Regardless of where it runs, IronFlock continues to take care of everything beneath the application layer:
- App lifecycle management — install, update, and rollback across all devices from the IronFlock UI
- Remote service and logs — access device logs and terminal sessions over the secure tunnel
- Data and message routing — the WAMP messaging layer works identically in every deployment mode
- Built-in standards — alarms, dashboards, and data storage are available out of the box
- Compliance-ready infrastructure — keeping data within your network (Appliance / Private Cloud) satisfies requirements such as EU Data Act, NIS2, CRA, IT-SiG, and KRITIS
What App Distributors Focus On
Because IronFlock absorbs all IT complexity, app distributors only need to provide:
- Edge logic — the application code that runs on the device (
Dockerfile+ your business logic) - Branded assets — your own name, logos, and product identity in the app UI
- Domain expertise — laser calibration, predictive maintenance, quality inspection, or whatever your industry problem is
No IT infrastructure knowledge is required. The same app that works in the IronFlock cloud works on an Appliance or in a private-cloud deployment without code changes.
Role of System Integrators
For complex industrial environments, system integrators may extend IronFlock deployments with:
- Industry-specific OT protocol bridges (OPC-UA, Modbus, PROFINET)
- Customer ecosystem integrations (MES, ERP, SCADA)
- Custom network segmentation or hardware provisioning
The system integrator configures the IronFlock stack; the app distributor delivers apps into it — each role stays in its own lane.