Start faster with cloud operation
For many teams, cloud operation is the fastest way to introduce Ordinavo. Provisioning, updates and the technical foundation can be organized centrally while the company focuses on processes and teams.
Operating model
Depending on project requirements, Ordinavo can be provided as a cloud solution or in an individually coordinated operating environment. Companies can digitize operational processes without losing sight of infrastructure requirements.
For many teams, cloud operation is the fastest way to introduce Ordinavo. Provisioning, updates and the technical foundation can be organized centrally while the company focuses on processes and teams.
For organizations with special requirements around data sovereignty, network structure, internal IT rules or integrations, on-premise or dedicated operating models can be evaluated project by project.
The right operating model depends on timeline, infrastructure, data flows and internal requirements.
| Topic | Cloud | On-premise / dedicated |
|---|---|---|
| Entry | fast | project-specific |
| Operation | centrally organized | customer-specific |
| Updates | simpler | coordinated |
| Infrastructure | Ordinavo-side | customer- or project-side |
| Integrations | through secure interfaces | also possible with internal systems |
For productive use, availability, updates, backups, monitoring and recovery must be considered. Ordinavo should be treated as an operational part of business processes.
Backup and recovery concepts should fit productive use.
Monitoring and troubleshooting support stable operation.
The update strategy depends on the selected operating model.
Access to operating environments must be limited and controlled.
Customer records, visit reports, attachments, timeline history and integration logs can be operated in a managed cloud setup or in customer-controlled infrastructure, depending on the selected deployment model.
| Area | Operational note |
|---|---|
| Customer records | Customer, location and contact records can be operated in managed cloud or customer-controlled infrastructure depending on the deployment model. |
| Visit reports and attachments | Reports, free text, photos and files need retention and access policies that match the operational process. |
| Timeline history | Timeline entries aggregate existing records and should follow tenant and deployment retention policies. |
| Integration logs | Import jobs, mapping warnings and webhook delivery logs support transparency and troubleshooting. |
| On-premise responsibility | On-premise does not automatically create compliance. It changes who controls infrastructure, backups, network boundaries and local retention. |
Connect operations
When Ordinavo Connect is connected with customer portals, terminals, ERP systems or partner platforms, network access, API endpoints, authentication, webhooks and data flows must fit the hosting model.
No. Depending on the project, cloud, on-premise or dedicated operating models can be evaluated.
For trials and first pilot projects, cloud operation is usually the fastest start.
Yes. The operating model should be selected so API endpoints, networks and security requirements fit the integration.
For productive use, backup, recovery and update strategies should be aligned project by project.
Yes. Hosting, security, privacy and integrations are central topics for larger rollouts.
We review cloud, dedicated operation, Connect integrations and security requirements for your rollout.