On-Premise & Air-Gap
Choose public cloud with data residency, private cloud or self-hosted SIMORIN, including restricted-network and air-gapped environments without internet access.
Operate where your environment requires.
Deployment requirements differ by organization. Alongside public cloud with data residency and private cloud, SIMORIN can be self-hosted on-premise with restricted connectivity or in an air-gapped environment with no internet access.
Public Cloud with Data Residency
Discuss the required hosting region and data-location boundaries as part of deployment planning.
Explore →Private Cloud
Plan a dedicated deployment around your organization’s networking, administration and operating requirements.
Explore →Self-Host on-premise
Run within your own infrastructure and define the internal services, access routes and administrative responsibilities.
Explore →Restricted Network
Define allowlisted connections and the permitted routes between SIMORIN and your managed systems.
Explore →Air-Gap — no internet
Plan operation inside an isolated network, including local dependencies and offline update, evidence and maintenance procedures.
Explore →Operational planning
Agree identity, backup, recovery, update and support procedures appropriate to the selected deployment.
Explore →From scope to verified outcome
- Define network isolation, data-location and operating requirements.
- Map local services, dependencies and integration endpoints.
- Plan installation, updates, backups and support within those boundaries.
- Validate workflows and recovery procedures in the intended environment.
In your operations
An organization needs management inside a network without internet access. Plan local identity and managed-system connections, establish approved offline update procedures and validate the operational workflows inside that boundary.
A deployment plan aligned with your connectivity, data location and operational requirements. External SaaS connections require a permitted network path; an air-gapped installation can only reach services available inside its boundary.
Build the scope around your environment.
Review your systems, operational priorities, required integrations and approval boundaries with our team.