On-premises
The organization owns the infrastructure
continON runs inside the organization’s own data centre. Data and operation never leave its control.
Who holds each responsibility
- InfrastructureClient
- DataClient
- HostingClient
- OperationsCREA-KO
continON/Deployment Options
Deployment follows the requirement.
Where continON runs is an operational decision, not a default. The right environment depends on who must control the data and how the organization is governed — and CREA-KO carries responsibility for implementation and upgrades whichever is chosen.
Choosing an environment
The same continON core runs in every environment. What changes is who holds each responsibility: infrastructure and hosting shift by model, while data stays with the organization and operations with CREA-KO throughout.
Private infrastructure
Control required, hosting delegated
A dedicated private environment the organization governs, without operating the hardware directly.
Who holds each responsibility
- InfrastructureClient
- DataClient
- HostingCREA-KO
- OperationsCREA-KO
Cloud
Standard requirements, faster start
Approved cloud deployment where operational requirements allow it.
Who holds each responsibility
- InfrastructureCREA-KO
- DataClient
- HostingCREA-KO
- OperationsCREA-KO
Not every capability behaves identically in every environment. The right model is decided against actual requirements, not assumed.
CREA-KO’s part
Implementation and upgrades, under contract.
A deployment decision is the start of a long relationship. The organization keeps control of its data and its environment; CREA-KO implements the chosen model, then maintains and upgrades it across its working life — so the platform keeps pace with the organization instead of aging in place.
Where should your platform and data live?
On-premises, private or cloud — you decide who holds the infrastructure and the data, and CREA-KO implements and maintains what you choose.