# Stilla – CMDB, ITSM and an operational map of your IT > Stilla brings CMDB, incidents, changes, event management, patching and costs together on one dependency map. Redundancy-aware service impact. SaaS or OpenShift. URL: https://stilla.eywo.digital/en/ Language: en Last updated: 2026-10-27 Calmly run IT # Chaos under control. No surprises. Stilla 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. [Choose an edition →](https://stilla.eywo.digital/en/editions/)[Download datasheet](https://stilla.eywo.digital/en/datasheet/) 1. 01Business services 2. 02Applications 3. 03Databases 4. 04Servers and containers 5. 05Virtualisation and cloud 6. 06Virtual network and disks 7. 07Storage and SAN 8. 08Network and segments 9. 09Data centre One dependency map across every layer. Incidents, changes, alerts and costs all know which service they affect. 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. 01 ### A CMDB nobody trusts Data goes stale, people keep their own spreadsheets and ask colleagues during incidents. **Solution**Versions and history for every change, data quality checks, discovery, import and sync with a primary CMDB. [Read the article →](https://stilla.eywo.digital/en/blog/cmdb-nobody-trusts/) 02 ### Impact discovered after the outage Whoever plans a change often does not know which services it will hit. **Solution**A layered dependency map, outage simulation and impact calculated before a change is submitted. [Read the article →](https://stilla.eywo.digital/en/blog/impact-before-outage/) 03 ### Approvals lost in email Outages, requests and prices are approved in different channels and nobody knows what is pending where. **Solution**One approvals queue, one ownership rule, every rejection with a reason. [Read the article →](https://stilla.eywo.digital/en/blog/change-approvals-without-email/) 04 ### Patching as a monthly negotiation Every window is negotiated again and critical vulnerabilities wait. **Solution**A patch agreement with the service owner, a pre-approved window, wave plans and an expedited mode. [Read the article →](https://stilla.eywo.digital/en/blog/patching-without-monthly-negotiation/) 05 ### Thousands of alerts, no situation Monitoring reports symptoms, not causes. People stop reading. **Solution**Deduplication, suppression during changes and grouping into situations using CMDB topology. [Read the article →](https://stilla.eywo.digital/en/blog/monitoring-noise/) 06 ### Costs not linked to services Cloud and data centre invoices cannot be attributed to services or customers. **Solution**FOCUS cost import, costs by service and customer, a price list with an owner. [Read the article →](https://stilla.eywo.digital/en/blog/what-does-a-service-cost/) 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. [How it works →](https://stilla.eywo.digital/en/solutions/) Features ## Features Modules that share their data. Switch on only the ones you need. Standard ### CMDB 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 with item neighbourhood and grouping by class; impact and root-cause items always on top - 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 - OpenShift inventory import down to the physical layer: nodes, OpenShift Virtualization VMs, hosted clusters, network and ODF Standard ### VMware 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 Standard ### Incidents and requests - The affected service, impact and resolver team are suggested from the CMDB item - Priority from impact and urgency, major incidents with a review and corrective actions - Parent incident for a mass outage; child incidents close with it - 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 Standard ### SLAs 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 - Measured service availability against the SLA target Standard ### Problems and known errors - A problem from an incident, a major incident review or a post-change review - Problem suggestions from recurring incidents on the same item - Root-cause analysis, workaround and a known error record - The incident resolver sees the known error and its workaround - Fix through a change, closure only after verification Standard ### Changes 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 - Approval level by risk from a questionnaire, minimum number of approvers - Separation of duties: neither requester nor implementer approves their own change; delegations with an audit trail - Closure with an outcome and a post-change review - CMDB edits only with a change, including rack placement or part replacement - Change calendar and a filterable overview of maintenance windows Standard ### One approvals queue - Outages, requests, price proposals and patch agreements in one place - One ownership rule, fallback approver - Every rejection with a reason Business ### Event 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 Business ### Patch 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 Business ### Data 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 Business ### AI assistant - Incident drafts from situations and similar incidents - Draft customer communication - Change review before approval - Optionally an on-premise model. A person always decides. Business ### Procurement and IT asset management - Asset cards linked to the CMDB, handover protocols and cost centres - Accounting and tax depreciation, disposal through a disposal committee - Purchase request → approval by the cost-centre owner, and by finance above a limit → order → receipt - Supplier invoices with order – receipt – invoice matching - Spare-part stores at data centres: minimum levels, transfers, issue against an incident or change, RMA - Software licences: entitlements, assignments and compliance with installations in the CMDB Enterprise ### Costs, 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 Enterprise ### Customer 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 Standard ### Adoption roadmap and rollout governance - Discovery workshop wizard: goals with KPIs, area maturity, data availability, profile and modules - Priorities by impact and effort, rollout waves respecting dependencies and capacity - Workstreams per module with tasks, owners, milestones and readiness checks - Approved baseline, slippage with reasons and go / no-go steering committee decisions - KPIs measured by Stilla every week and a steering committee report Standard ### Governance, 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 →](https://stilla.eywo.digital/en/nis2-dora/) Comparison ### Stilla and other tools Using ServiceNow, Jira, OpenText or CA? See when Stilla makes sense instead of them and when alongside them. [Comparison →](https://stilla.eywo.digital/en/compare/) 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. Stilla 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. Stilla 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. Stilla 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. [All use cases →](https://stilla.eywo.digital/en/solutions/#pouziti) 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. CIO / IT director “Are operations under control, and can I prove it?” [More for this role →](https://stilla.eywo.digital/en/roles/#cio) - 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 →](https://stilla.eywo.digital/en/roles/#ops) - 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 Service owner “What is happening to my service, and what is being asked of me?” [More for this role →](https://stilla.eywo.digital/en/roles/#owner) - One approvals queue - Maintenance window and patch agreement for the service - Dependency map and single points of failure - Service price list and costs Change manager “May this change go ahead, when, and who approved it?” [More for this role →](https://stilla.eywo.digital/en/roles/#change) - 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 →](https://stilla.eywo.digital/en/roles/#sec) - 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) IT finance “What does a service cost, and whom do we bill?” [More for this role →](https://stilla.eywo.digital/en/roles/#fin) - 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 - 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 [Order Standard →](https://stilla.eywo.digital/en/order/?edice=standard) 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 [Order Business →](https://stilla.eywo.digital/en/order/?edice=business) ### 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 [Order Enterprise →](https://stilla.eywo.digital/en/order/?edice=enterprise) 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 Stilla? Stilla 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 Stilla 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 Stilla include? CMDB and dependency map, VMware virtual network and disks, incidents and requests, problems and known errors, SLAs, changes and maintenance windows with approval audit, one approvals queue, event management, patch and vulnerability management, data centres and contracts, procurement and IT asset management including depreciation and spare parts, an AI assistant, costs and billing (FinOps), customer data separation and an audit trail. All modules share one set of data. ### How is Stilla 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 Stilla 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 Stilla 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. [CMDB·25 October 2026 ### 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](https://stilla.eywo.digital/en/blog/virtual-network-in-the-cmdb/)[Governance·25 October 2026 ### 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](https://stilla.eywo.digital/en/blog/nis2-dora-evidence/)[Rollout·15 October 2026 ### 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](https://stilla.eywo.digital/en/blog/itsm-without-half-year-project/) [All articles →](https://stilla.eywo.digital/en/blog/) Next step ## 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. [Choose an edition →](https://stilla.eywo.digital/en/editions/)