01 / Hosting
Where your solution runs
In Germany or on-premises within your own infrastructure. We set up the environment and plan backup and recovery. The location commitment also covers model inference, logs and backups.
After launch
Your workflow is running.
We make sure it stays supported.
Systems change. Interfaces do too. EVORI can take care of hosting, maintenance and further development of your AI solution, with an agreed operating model and clear responsibilities.
02 / Maintenance
Keep existing functionality working
Monitor operational health, investigate faults, update dependencies and address interface changes. Maintenance windows, response times and escalation procedures are defined.
03 / Further development
Improve with a clear purpose
Prioritise new requirements, test changes and coordinate releases. Additional features receive their own scope and approval.
For your AI workflows
Germany or on-premises
We operate your AI workflows entirely in Germany or on-premises within your own infrastructure. This covers all data and processing steps, including model inference, logs and backups.
Before a pilot is approved, the specific architecture must be reviewed with your IT team: provider and model, data flows, locations, access, deletion, logs and backups. The approved configuration forms the basis for operations.
This commitment applies to client workflows. The website, appointment booking and website analytics are covered separately in our privacy policy.
One operator. Clear responsibilities.
Your team operates the solution
We hand over documentation and knowledge. You take responsibility for day-to-day operations; individual maintenance or development work can be commissioned separately.
EVORI supports operations
We take on the agreed technical tasks. Your department remains responsible for business decisions, approvals and access to company data.
What is listed separately in the proposal
- One-off takeover and setup
- Ongoing support and maintenance scope
- Hosting, licences and usage-based model costs
- Additional development and changes
The service targets we agree
24/7 on-call support, guaranteed availability, response times and recovery targets apply when specifically agreed. Processing in Germany or on-premises is the fixed operating framework. A support period after implementation is not an unlimited maintenance contract.
We only take over an existing solution after reviewing its architecture, access, documentation and risks, and its suitability for this operating framework.
For IT, departments and decision-makers
Four approvals before production use.
This is a review framework, not a security or service commitment that has already been fulfilled. The specific architecture and responsible people are defined for your project.
Approved sourceProcessing & validationHuman approvalTarget system
At every handoff, review access rights, stored data and responsibilities. Providers and storage locations have not yet been selected for your project.
01 · IT + data protection
Data & integration
Which service may process which source?
Document systems, interfaces, test access, data types, providers and regions, access roles and retention periods. Explicitly review model training and subprocessors.
02 · Department + EVORI
Quality & acceptance
When is the workflow good enough?
Agree examples, errors and edge cases, human checkpoints and measurable acceptance criteria. Testing only straightforward success cases is not enough.
03 · Process owners + team
Team & participation
Who uses, reviews and decides?
Document roles and training needs. Involve the works council where applicable. Clarify use of learning and activity data before rollout.
04 · Operator + department
Operations & incidents
What happens if something fails?
Assign responsibility for monitoring, cost limits, backups, recovery, escalation and falling back to the previous process. Record response times in the contract.
Already have a pilot? Discuss the remaining questions →