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 →The operational map of your entire IT
See all of your IT. From business service to rack unit.
From one CMDB, Eywo Stratum calculates the impact on services – for incidents, changes, patching and costs – including the redundancy of clusters and replication. For IT operations in regulated organisations that want to decide from the same data and be able to prove it.
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.
StandardCMDB and dependency map
- 36 classes: services, applications, databases, VMs (VMware, Hyper-V, Azure Stack Hub, OpenShift Virtualization, public clouds), IBM Power (LPAR, VIOS), physical servers, containers, storage, SAN, network, OT
- Discovery API with matching, full sync and retirement; CSV and Excel import, manual creation
- Versions and history of every change: who, when, what and from where
- Data quality and inconsistency checks
- Layered dependency map, outage simulation and single points of failure
- Redundancy-aware impact: clusters, HADR, Data Guard, PowerHA, HyperSwap
- Inventory of OS, software, disks and network cards; OS, software and hardware lifecycle
StandardVMware virtual network and disks
- Distributed and standard virtual switches, port groups and VLANs
- Virtual machines and VMkernel adapters linked to port groups
- Host uplinks to leaf switches – impact from the virtual to the physical network
- VM disks in the server inventory; a shared or RDM disk as its own item
- Disks linked to datastores automatically during discovery
- “Disks and storage” data quality check
StandardIncidents and requests
- The affected service, impact and resolver team are suggested from the CMDB item
- Priority from impact and urgency, major incidents
- Request catalogue with forms, approval, due dates and fulfilment steps
- A request that changes infrastructure continues as a change
- Configurable workflow: states, transitions and permissions
StandardSLAs and business hours
- Response and resolution SLAs in business hours with calendars and holidays
- Pause, service, customer and default SLAs
- Monthly SLA performance and warnings before a breach
StandardChanges and maintenance windows
- Standard, normal and emergency change models with steps and lead time
- Impact calculated before submission
- Slots only inside maintenance windows, outside freezes and collisions
- Rolling execution item by item
- Outage approval by the service owner, change manager, CAB
- Change calendar and a filterable overview of maintenance windows
StandardOne approvals queue
- Outages, requests, price proposals and patch agreements in one place
- One ownership rule, fallback approver
- Every rejection with a reason
BusinessEvent management
- Ingest from Zabbix, Prometheus/Alertmanager, Checkmk, Grafana and an API
- Deduplication, flapping, filtering and suppression during changes
- Situations by CMDB topology with a probable cause
- Incident from a situation in one step or automatically
- Live event stream, optionally via Kafka
BusinessPatch and vulnerability management
- Scanner findings import, vulnerabilities by server and service
- Actively exploited vulnerabilities and deadlines by severity
- Patch agreement: standing window, pre-approved patching, expedited mode
- Wave plans and changes from the plan in one step
BusinessData centres and contracts
- Site, data centre, room, aisle, rack and rack unit with visualisation
- Service contracts, item coverage, expiry dates and vendor SLAs
- Incident escalation to the vendor according to the contract
BusinessAI assistant
- Incident drafts from situations and similar incidents
- Draft customer communication
- Change review before approval
- Optionally an on-premise model. A person always decides.
EnterpriseCosts, billing and price list
- FOCUS cost import, currency conversion at the CNB rate
- Costs by customer, project and business service
- Pivot tables and monthly billing data
- Service price list and server calculator; price changes approved by the service owner
- Application capacity model: users, peak load and tiers
EnterpriseCustomer separation
- A customer’s users see only their own data, including costs
- Roles scoped to a customer, team or item
- Sync with a primary CMDB (ServiceNow, SMAX) via external IDs
StandardGovernance, security and audit
- 14 scoped roles, a RACI matrix checked against permissions
- SSO and API tokens for service accounts
- Five-year audit trail, before and after state for configuration
- Email and Slack notifications by rules and templates
- Deployed as SaaS or a container on OpenShift; works on mobile too
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
Stratum and other tools
Using ServiceNow, Jira, OpenText or CA? See when Stratum 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. Stratum 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. Stratum 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. Stratum 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
- VMware virtual network and disks
- Incidents, requests and service catalogue
- Changes, 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
- 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.
Blog
From the blog
IT management challenges and how we approach them.
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
Rolling out ITSM without a six-month project
Introducing a new ITSM tool does not have to mean months of workshops and consultants. Start with one area, bring over the data you already keep in Excel, and check readiness before you go live.
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.