Deploy where your operations and security policies require
Run the KENIS platform in our managed cloud or inside your own network. Every option comes with the same guardrails and security controls, so you choose based on your IT strategy, not on compromises.
Deployment options
Three ways to run KENIS
KENIS Cloud
We host, monitor, and maintain the platform in our secured cloud network.
- Fully managed hosting and monitoring
- Upgrades and patches handled by KENIS
- Encrypted site-to-cloud connectivity
- Active/passive disaster recovery across two regions
- Fastest path to go-live
Client Network
Deploy on-premises or in your private cloud so data never leaves your environment.
- Your data center or cloud subscription
- Data stays inside your network
- Aligned with your IT and security policies
- Fits your change-management process
Hybrid
Keep real-time equipment control on-site and run management and analytics in the cloud.
- Low-latency control at the site edge
- Central dashboards across facilities
- Store-and-forward if connectivity drops
- Cloud tier protected by two-region disaster recovery
- Scale sites without re-architecture
Compare
Choosing the right model
| KENIS Cloud | Client Network | Hybrid | |
|---|---|---|---|
| Who runs the infrastructure | KENIS | Your IT team, supported by KENIS | Shared: site edge by you, cloud by KENIS |
| Where data lives | KENIS secured cloud | Inside your network | Control data on-site, analytics in the cloud |
| Upgrades and patches | Managed by KENIS | Scheduled through your change process | Coordinated between teams |
| Disaster recovery | Active/passive across two cloud regions | Aligned with your DR plan and secondary site | Cloud tier active/passive across two regions; site edge keeps running |
| Best for | Fast start and lean IT teams | Strict data residency and security policies | Multi-site operations needing low-latency control |
Disaster recovery
Active/passive across two regions
For KENIS Cloud and Hybrid deployments, the platform runs active in a primary cloud region with a passive standby in a second, geographically separate region. If the primary region goes down, operations fail over to the standby so work keeps flowing between WMS and the floor.
- KENIS Cloud
- Hybrid (cloud tier)
Primary region
- Serves all live traffic
- Processes WMS, WCS, and equipment messages
- Replicates data to the standby region continuously
Secondary region
- Warm standby, kept in sync
- Same configuration and security controls
- Takes over live traffic on failover
Continuous replication
Messages, configuration, and platform state replicate to the standby region so it is ready to take over.
Health monitoring & failover
Health checks detect a regional outage and trigger a controlled failover, automatically or with operator approval.
Message durability
Durable queues and store-and-forward at the site hold messages during failover and replay them in order once the standby is active.
Agreed RTO and RPO
Recovery time and recovery point objectives are agreed with you and built into the design.
Regular DR drills
Scheduled tests verify failover and failback, with results shared with your team.
Planned failback
Return to the primary region in a planned window once it is healthy again.
Hybrid
Real-time equipment control stays at the site edge, so the floor keeps running during a cloud failover. Store-and-forward holds messages until the standby region is active.
Client Network
KENIS designs recovery to fit your own DR plan, data centers, and secondary site.
Guardrails and security in every deployment
- Role-based access and least-privilege accounts
- Encryption in transit and at rest
- Network segmentation between enterprise IT and floor (OT) systems
- Approval gates before AI-suggested corrections reach live systems
- Complete audit trail for every message, change, and reprocess
- Separate development, test, and production environments
Process
How a deployment comes together
- 01
Assess
Review infrastructure, network, security, and compliance requirements with your IT team.
- 02
Design
Choose the deployment model and define environments, connectivity, and access.
- 03
Build & secure
Stand up development, test, and production environments with guardrails in place.
- 04
Validate
Run security, performance, integration, failover, and user acceptance testing.
- 05
Go live & operate
Cut over, monitor, and support the platform through HyperCare and beyond.
Ready to integrate your warehouse stack?
Tell us about your WMS, WCS, and automation goals. We will help you find the right approach.