CentOps joins monitoring events and configuration items into one map of your services. On top of it you run incidents, changes and architecture – and you know the impact of every change and outage in advance, including cluster and replication redundancy.
CentOps is the operational control layer for IT and business services. From monitoring events and configuration items it builds one service map, and on it you run incidents, changes and architecture – from alert to roadmap.
Three principles that hold for every module.
Incidents, changes, patch plans and monitoring situations all calculate impact the same way, including clusters, replication and mirrored storage.
Connect monitoring (Zabbix, Prometheus or commercial tools) and discovery. No dozens of connectors to other systems to maintain.
Operations, changes and architecture in one application. What breaks today feeds the plan for next quarter.
Three steps from first data to running your services. No six-month implementation project.
Monitoring sends events; discovery or an import provides configuration items. You need no other integrations.
Items, relationships and owners form one dependency map. Events are matched to items and grouped into situations.
Incidents, problems, changes, patching and the architecture roadmap all work on the same map and the same impact calculation.
Modules that share their data. Switch on only the ones you need.
Architecture, costs, suppliers, service resilience and the rollout roadmap – decisions made before anything needs fixing.
Every change with impact, window and approval, purchasing and assets from order to retirement – configuration changes only with a change.
From the first alert to a restored service and from a request to its fulfilment, with as few people as needed.
The configuration database, dependencies, access, audit and the AI assistant that Plan, Build and Run all rely on.
What operations look like when processes share the same data.
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.
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.
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.
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.
“What is on fire, who does it affect and who is working on it?”
More for this role →“Which vulnerabilities threaten which services, and when will they be fixed?”
More for this role →The beta is open to at most 10 companies. You get the full application and a team that walks you through the rollout.
After 6 months we offer a paid edition, or hand over a data export and delete the instance.
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.
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.
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.
As SaaS operated by Eywo, in your own Cloudflare account, or as a container on your OpenShift. The interface works on mobile too.
CentOps is in public beta: free for 6 months for at most 10 companies, with your own instance in the EU and rollout help. After the beta we offer a paid version, or hand over a data export.
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.
IT management challenges and how we approach them.
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.
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.
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.
Connect monitoring and discovery and see your service map within the first week. The beta is free for 6 months.
We reply in your language. Messages are translated automatically; every reply is written by a person from our team.