INVO can run in our managed cloud infrastructure, in a cloud your organization controls, or in an on-premise environment. The deployment architecture, access, security, integrations and support model are defined together during Solution Design.
The same platform. Three deployment models.
Deploy it your way
The simplest way to launch.
INVO runs in infrastructure managed by INVO. Suited to organizations that want to limit their own infrastructure involvement and leave environment maintenance with the vendor.
INVO in your cloud environment.
The system can be deployed in cloud infrastructure the customer controls. Suited to organizations with their own cloud governance, networking, access management and security standards.
INVO in your own data center.
For customers who need the system to run in their own data center or private environment, an on-premise model is available.
Choose the right model
The exact split of responsibility, the scope of maintenance and the infrastructure requirements are agreed during Solution Design and depend on the deployment model chosen.
| Area | INVO Cloud | Customer Cloud | On-Premise |
|---|---|---|---|
| Infrastructure owner | INVO | Customer | Customer |
| Hosting environment | Cloud managed by INVO | Customer cloud | Customer infrastructure |
| Infrastructure management | INVO | Joint / customer | Joint / customer |
| Deployment | INVO | Joint | Joint |
| Network policies | INVO environment | Customer policies | Customer policies |
| Access policies | Configured jointly | Customer standards | Customer standards |
| Integration with internal systems | Yes | Yes | Yes |
| Updates | Managed rollout | Coordinated | Coordinated |
| Monitoring | Defined for the model | Defined for the model | Defined for the model |
| Backups | INVO | Defined jointly | Defined jointly |
| Operating system / platform | INVO | Customer | Customer |
Security and stability need a clear split of responsibility between INVO and the customer’s IT team. We define who owns each element from the start.
Separate environments
A rollout should use separate environments for configuration, testing, acceptance and live operation.
We test changes before they reach the real operation.
Layered security
Seven layers, each with its own owner and its own controls.
Who the user is and how their identity is confirmed.
Roles, permissions and organizational scope.
Business logic and operating rules.
Protection and separation of operating data.
Controlled connectivity between environments.
The environment the platform runs in.
Visibility of events and changes.
Identity and access management
Access to INVO is controlled at the level of users, roles and permissions.
Access to functionality according to the user’s role.
Access can be limited to a defined part of the organization.
Separate permissions for administrators.
Configurable access rules depending on the customer architecture.
In enterprise environments, users should not have to manage yet another independent set of accounts if the organization already runs central identity management. During deployment design we can include integration with your existing identity provider.
Protect your operating data
In an operating system it matters not only what the current state of the data is, but how it got there.
What is recorded
Continuity of operation
A production system needs an agreed way to respond to failures and to events that affect availability.
The backup model depends on the chosen infrastructure model and your own policy. During Solution Design we define the following.
For environments that require a disaster-recovery plan, we define a recovery architecture appropriate to the chosen deployment model.
System status
What can be monitored
Scope depends on the deployment model. You cannot manage an environment whose state you cannot see.
Secure rollout
The security architecture is designed as part of the implementation, not added after the system is running.
We do not assume one infrastructure and security model for every customer. During the rollout we can work through the following areas with your IT team.
As part of the implementation we can prepare the documentation needed to agree the architecture with IT and Security.
Infrastructure & security
Show us your current architecture, IT standards and security requirements. Together we will decide whether INVO Cloud, Customer Cloud or an on-premise deployment fits best, and how INVO should join your existing environment.
