A CMDB nobody trusts
Data goes stale, people keep their own spreadsheets and ask colleagues during incidents.
SolutionVersions and history for every change, data quality checks, discovery, import and sync with a primary CMDB.
Read the article →Calmly run IT
Chaos under control. No surprises.
CentOps brings your CMDB, incidents, changes, monitoring and costs together on one dependency map. You know the impact of every change and outage in advance, including cluster and replication redundancy. Less manual work, fewer calls at night and better sleep for IT operations in regulated organisations.
See beneath the surface
We bring the CMDB, incidents, changes, monitoring and costs together on one dependency map. Every operational decision starts from the same data – and the people responsible for operations go home with peace of mind.
Challenges
Challenges we solve
IT operations rarely fail on technology. They fail because nobody has the full picture: who the owner is, what depends on what, when production may be touched and what it costs.
Impact discovered after the outage
Whoever plans a change often does not know which services it will hit.
SolutionA layered dependency map, outage simulation and impact calculated before a change is submitted.
Read the article →Approvals lost in email
Outages, requests and prices are approved in different channels and nobody knows what is pending where.
SolutionOne approvals queue, one ownership rule, every rejection with a reason.
Read the article →Patching as a monthly negotiation
Every window is negotiated again and critical vulnerabilities wait.
SolutionA patch agreement with the service owner, a pre-approved window, wave plans and an expedited mode.
Read the article →Thousands of alerts, no situation
Monitoring reports symptoms, not causes. People stop reading.
SolutionDeduplication, suppression during changes and grouping into situations using CMDB topology.
Read the article →Costs not linked to services
Cloud and data centre invoices cannot be attributed to services or customers.
SolutionFOCUS cost import, costs by service and customer, a price list with an owner.
Read the article →Solution
How we solve it
We do not start with forms, we start with data. Every process sits on one CMDB and one rule for who the owner is. That is why incidents, changes and costs understand each other.
Impact from one graph, redundancy included
Clusters, HADR, Data Guard, PowerHA, HyperSwap and paired SAN fabrics are taken into account when impact is calculated. Incidents, changes, patch plans and monitoring situations all use the same calculation.
Accountability for regulated operations
An owner for every service, scoped roles, a RACI checked against permissions and an immutable five-year audit trail. Evidence for NIS2 and DORA reporting is in preparation.
One application instead of several products
CMDB, ITSM, event management, patch management and FinOps share one set of data. You switch modules on when you need them – not as add-on products.
Fast rollout, local operation
SaaS or a container on your own OpenShift. Czech and English, local holidays in SLAs, CNB exchange rates, a public price list and a step-by-step rollout with a readiness check.
Features
Features
Modules that share their data. Switch on only the ones you need.
Plan: strategy and planning
Architecture, costs, suppliers, service resilience and the rollout roadmap – decisions made before anything needs fixing.
- Availability and resilienceStandard
- Enterprise architectureEnterprise
- Costs and billingEnterprise
- Contracts and suppliersBusiness
- Rollout roadmapStandard
Build: change and delivery
Every change with impact, window and approval, purchasing and assets from order to retirement – configuration changes only with a change.
- IT assets and procurementBusiness
- Licences and spare partsBusiness
- Changes and maintenance windowsStandard
- ApprovalsStandard
- Patching and vulnerabilitiesBusiness
Run: operations and support
From the first alert to a restored service and from a request to its fulfilment, with as few people as needed.
- Monitoring and eventsBusiness
- IncidentsStandard
- War roomBusiness
- Problems and known errorsStandard
- SLAs and availabilityStandard
- Requests and service catalogueStandard
Platform: the shared foundation
The configuration database, dependencies, access, audit and the AI assistant that Plan, Build and Run all rely on.
- Configuration databaseStandard
- Dependency map and impactStandard
- Data centres and racksBusiness
- Roles, security and auditStandard
- Customer separationEnterprise
- AI assistantBusiness
NIS2 and DORA
What we can evidence today and what is in preparation
The dependency map, service owners and an immutable audit trail are the foundation for NIS2 and DORA. See what is available today and what is in preparation.
NIS2 and DORA →Comparison
CentOps and other tools
Using ServiceNow, Jira, OpenText or CA? See when CentOps makes sense instead of them and when alongside them.
Comparison →Use cases
Use cases
What operations look like when processes share the same data.
01
Planned outage of a database cluster
The change manager creates a change. CentOps calculates the affected services, offers a slot inside the maintenance window and outside any freeze, and sends the outage to the service owners for approval. Alerts from affected servers are suppressed during the change.
02
A storage failure at night
Monitoring sends hundreds of events. CentOps groups them into one situation with a probable cause in storage, opens a major incident with the affected services and escalates to the vendor according to the service contract.
03
A critical vulnerability on a Friday
The scanner import flags an actively exploited flaw. CentOps shows the affected servers and services, sets a deadline by severity and creates a change in one step from the patch agreement’s expedited mode.
04
Monthly billing data
Costs from clouds, OpenShift and the data centre are loaded in FOCUS format, converted at the Czech National Bank rate and broken down by customer, project and service. Finance gets the data without spreadsheet work.
Who it’s for
Who it’s for
For IT operations in banking and insurance, energy, automotive and manufacturing, the public sector and shared-service providers. Every role sees the same data, but asks different questions.
- SLA performance by service and month
- Costs by service and customer
- Audit trail and RACI for audits and regulation
- Step-by-step rollout with measurable readiness
Head of operations
“What is on fire, who does it affect and who is working on it?”
More for this role →- Situations from monitoring instead of thousands of alerts
- Incidents with suggested service, impact and team
- Major incidents with vendor escalation
- Team queues and SLA deadlines
- One approvals queue
- Maintenance window and patch agreement for the service
- Dependency map and single points of failure
- Service price list and costs
- Impact calculated before submission
- Windows, freezes and collisions in the calendar
- Change models and CAB
- Change review by the AI assistant
Security
“Which vulnerabilities threaten which services, and when will they be fixed?”
More for this role →- Scanner findings import
- Actively exploited vulnerabilities with deadlines
- Expedited patching mode
- Scoped roles, SSO and an immutable audit trail
- Evidence for NIS2 and DORA (in preparation)
- FOCUS costs from clouds, OpenShift and the data centre
- Showback and chargeback by customer
- A price list with an owner and approved changes
- Monthly billing data
Editions
Editions
Start with what you need today. Move to a higher edition without migrating data.
Standard
For organisations that want a reliable CMDB and managed ITSM processes.
€990
per month
- CMDB, dependency map and redundancy-aware impact
- Service availability and resilience
- Incidents, requests and service catalogue
- Problems and known errors
- Changes with approval audit, maintenance windows and calendar
- SLAs and business hours
- One approvals queue
- Roles, RACI, SSO and audit trail
- Excel import and readiness check
Recommended
Business
For operations that want to connect monitoring, security and vendors.
€2,390
per month
- Everything in Standard
- Event management and situations
- Patch and vulnerability management
- Data centres and racks
- Service contracts and vendors
- Procurement, IT assets, depreciation and spare parts
- AI assistant
Enterprise
For shared-service providers and large organisations.
from €5,900
per month
- Everything in Business
- Costs, billing and price list (FinOps)
- Customer data separation
- Sync with a primary CMDB
- Priority support
Indicative prices excluding VAT, per environment. We prepare an exact quote based on scope and deployment model.
Questions and answers
Frequently asked questions
What is CentOps?
CentOps is an operational map of your entire IT. From one CMDB it calculates the impact on business services – for incidents, changes, patching and costs – including the redundancy of clusters and replication. It is made by Eywo s.r.o., based in Prague.
Who is CentOps for?
For IT operations in regulated organisations: banks and insurers, energy, automotive and manufacturing, the public sector and shared service providers. It is used by CIOs, operations leads, service owners, change managers, security and IT finance.
Which modules does CentOps include?
22 modules in six groups: services and configuration (configuration database, dependency map, availability and resilience, data centres), detect and correct (monitoring, incidents, war room, problems, SLAs), request and fulfil (catalogue, IT assets and procurement, licences and spare parts), change and deploy (changes, approvals, patching), strategy and portfolio (enterprise architecture, costs, contracts, rollout roadmap) and governance and security (roles, audit, customer separation). The AI assistant works across modules; all share one set of data.
How is CentOps deployed?
As SaaS operated by Eywo, in your own Cloudflare account, or as a container on your OpenShift. The interface works on mobile too.
How much does CentOps cost?
Indicatively Standard €990, Business €2,390 and Enterprise from €5,900 per environment per month, excluding VAT. We prepare an exact quote based on scope and deployment model.
Does CentOps do automatic discovery?
Today data arrives through the discovery API (with matching, full synchronisation and retirement), CSV and Excel import, or synchronisation with a primary CMDB. OpenShift inventory (nodes, OpenShift Virtualization, hosted clusters, network and ODF) is imported with a read-only tool. Connectors for automatic collection from vCenter and public clouds are in preparation.
Blog
From the blog
IT management challenges and how we approach them.
One switch down is not a service down
Impact analysis that ignores redundancy reports hundreds of "degraded" items and wakes people up for alerts that only repeat one cause. CentOps now calculates impact and event correlation from what would actually happen.
Business5 min read
The virtual network in the CMDB: from port group to leaf switch
Between a virtual machine and the physical network sits a layer most CMDBs do not see – virtual switches, port groups and host uplinks. Yet this is exactly where it is decided which services a network change will touch.
Standard3 min read
NIS2 and DORA: what operations must be able to evidence
Both regulations ask the same question – do you know which services an outage hits, who is responsible for them and what changed when? Without a reliable dependency map, the answers are assembled by hand, often under time pressure.
Standard3 min read
Next step
Choose an edition →Start with a pilot in one area.
Pick a customer or a department and its key services. After the pilot we review SLAs, changes and costs together – and you decide on expansion with peace of mind.