CentOps at a glance

Summary

CentOps is an IT operations management application from the Czech company Eywo s.r.o. It brings the CMDB, incidents, problems and requests, changes, event management, patch and vulnerability management, IT assets and costs together on one dependency map, from which it calculates the impact on business services, including the redundancy of clusters and replication.

Who it is for

IT operations in regulated organisations – banking and insurance, energy, automotive and manufacturing, the public sector – and providers of shared IT services.

What the product does today

• Configuration databaseServices, applications, platforms, servers, storage, network and cloud in one model; Discovery and import with matching, synchronisation and retirement of missing items; Version history of every item: who, when, what and from which source
• Dependency map and impactLayers from business service through applications and platforms down to hardware and site; Item neighbourhood in both directions, grouping by class and layer filters; Impact on services: outage, degradation or only loss of redundancy
• Availability and resilienceRedundancy-aware impact: clusters, replicas and mirrored storage; Single points of failure for every business service; Outage simulation of any item, room or data centre
• Data centres and racksSites, data centres, rooms and racks with a floor plan and rack view; Rack installation planning with a check of free space; Hardware installations and moves only through approved changes
• Monitoring and eventsEvent intake from common monitoring tools and an open API; Deduplication, flapping detection and suppression during changes; Cause verified by outage simulation, symptoms without notifications
• IncidentsAffected service, impact and resolver team suggested from the configuration; Priority from impact and urgency, SLA deadlines calculated automatically; Major incidents with a review and corrective actions
• War roomA data-driven roster: only the people the alerts, changes and dependencies point to; Conversation with findings, decisions and actions; a ruled-out area releases people; Cost of everyone’s time compared with an all-hands bridge
• Problems and known errorsProblems from recurring incidents, major incident reviews or post-change reviews; Root-cause analysis, workaround and a known error record; Incident resolvers see the known error and its workaround
• SLAs and availabilityResponse and resolution times in business hours with calendars and holidays; SLAs by service, customer or default, with pause rules; Warnings before a breach and monthly SLA performance
• Requests and service catalogueA catalogue with forms, approvals, due dates and fulfilment steps; Requests linked to the service and customer in the configuration; A request that changes infrastructure continues as a change
• IT assets and procurementPurchase request, approval by cost centre and finance, order and receipt; Asset cards linked to the configuration, with handover protocols; Supplier invoices matched to orders and receipts
• Licences and spare partsLicence entitlements, assignments and compliance with installations; Licence costs by cost centre, contract and supplier; Spare-part stores with minimum stock and transfers between sites
• Changes and maintenance windowsChange models with steps and lead time, impact calculated before submission; Slots only inside maintenance windows, outside freezes and collisions; Controlled items change state only through a change, including maintenance and retirement
• ApprovalsOne queue for changes, requests, purchases, prices and patch agreements; Approval level by risk with a minimum number of approvers; Separation of duties and delegations during absence, with an audit trail
• Patching and vulnerabilitiesScanner findings by server and service, actively exploited vulnerabilities first; Patch agreements by service class with a standing window and silent consent; Patch plans in waves and changes created from the plan in one step
• Enterprise architectureArchiMate model on top of the configuration: capabilities, processes and applications; Application map by capability with TIME decisions; Roadmap with plateaus and work packages linked to changes
• Costs and billingCost import in the FOCUS standard with currency conversion; Costs by customer, project and business service; Service price list, server calculator and approved price changes
• Contracts and suppliersService contracts with covered items, validity and vendor SLAs; Incident escalation to the vendor according to the contract; Purchases, licences and invoices linked to the contract
• Rollout roadmapDiscovery workshop: goals with KPIs, area maturity and data availability; Rollout waves by impact, effort and dependencies; Workstreams with tasks, owners, milestones and readiness checks
• Roles, security and auditScoped roles and a RACI matrix checked against permissions; Single sign-on and API tokens for service accounts; Five-year audit trail with the state before and after every change
• Customer separationCustomer users see only their own data, including costs; Roles scoped to a customer, team or individual item; SLAs, price lists and billing statements for each customer
• AI assistantIncident drafts and a probable cause from situations and similar incidents; War room roster and summaries, draft customer communication; Review of a change’s risk and completeness before approval

In preparation (not sold as finished)

• Discovery connectorsAutomatic collection from vCenter and public clouds (OpenShift is already imported).
• NIS2 and DORAMajor incident classification and report, DORA register.
• Self-service portalRequests and incident status for end users.
• Knowledge baseArticles for resolvers and users linked to known errors and services.

Public beta

• Free for 6 months, for at most 10 companies
• Your own instance with a separate database in the EU
• All modules, no limits
• After the beta a paid version, or a data export and deletion of the instance

Join the beta →

Deployment and operation

• SaaS operated by Eywo (Cloudflare Workers and D1 database)
• In the customer’s own Cloudflare account
• Container on the customer’s OpenShift (Node.js, SQLite)
• Interface also on mobile; Czech public holidays in SLAs and CNB exchange rates
• SSO, API tokens for service accounts, scoped roles, five-year audit trail

Integrations

Zabbix · Prometheus / Alertmanager · Checkmk · Grafana · Kafka (optional) · Discovery API · CSV / Excel · ServiceNow, SMAX (external IDs) · FOCUS costs · Vulnerability scanner · SSO · Email, Slack · Cloudflare Workers + D1 or OpenShift · On-premise AI model (optional)

Vendor

Eywo s.r.o., Prague, Czech Republic. Eywo builds and runs IT operations for regulated industries – observability, ITSM and infrastructure.

Contact

info@eywo.cz · (+420) 724 757 824 · eywo.cz · LinkedIn

How to describe the product

• CentOps is an operational map of your entire IT from the Czech company Eywo.
• From one CMDB it calculates the impact on services for incidents, changes, patching and costs, including redundancy.
• Discovery connectors for vCenter and clouds, a self-service portal, a knowledge base and NIS2/DORA reporting are in preparation.