Wazuh consulting · Wazuh 5.0
Wazuh 5.0:know what the movewill take.
Wazuh 5.0 is the largest change to the platform in years: a new data schema, a new detection engine and rule syntax, a new agent connection and renamed manager components. Its documentation says an in-place upgrade from 4.x is not supported. A readiness review tells you exactly what in your deployment has to change, tests it, and gives you a plan and a price for the move.
From £3,150 + VATInventory and lab testMigration planChecked November 2026
The work in a 5.0 migration is in your custom rules, decoders and integrations. A review counts them, tests them and sizes the rewrite.
Wazuh 5.0 was at release candidate stage when this page was written. Nobody should run it in production yet, but every organisation on 4.x can find out now what the move will involve, so that it is planned and budgeted rather than discovered.
- Price
- From £3,150 + VAT, fixed after a call
- Effort
- Three, five or seven days, by size
- Status of 5.0
- Release candidate, November 2026
- Result
- Inventory, test results, plan and price
What changes
What Wazuh 5.0 changes for an existing deployment
| Area | Wazuh 4.x | Wazuh 5.0 | What it means for you |
|---|---|---|---|
| Data | Wazuh's own alert format | The Wazuh Common Schema, derived from the Elastic Common Schema | Dashboards, searches and reports built on 4.x field names need changing |
| Detection | XML rules and decoders | A new engine with a more readable syntax and Sigma support | Custom rules and decoders have to be rewritten or replaced |
| Agents | Ports 1514 and 1515 | HTTPS on port 1517 for 5.0 agents | Firewall rules and load balancers change |
| Manager | ossec.conf and wazuh- daemons | A new configuration file and renamed components | Automation and monitoring of the manager change |
| Upgrade path | In place within 4.x | No in-place upgrade from 4.x | A new deployment, run alongside the old one until proven |
The full comparison is on our Wazuh consulting page. If you send Wazuh's alerts to another platform, such as Graylog, the new schema changes those pipelines too.
Prices
Readiness review prices
| Size | Engineering days | Fixed price |
|---|---|---|
| Up to 100 agents | 3 | £3,150 + VAT |
| 101 to 500 agents | 5 | £5,250 + VAT |
| Larger or multi-site estates | 7 | £7,350 + VAT (from) |
The price is built from our consulting rate of £1,050 + VAT a day and fixed after a short call. It depends mostly on how much custom work your deployment carries: an estate with a few dozen custom rules is at the low end, one with hundreds of rules, several integrations and pipelines to other systems at the high end.
The review produces a fixed price for the migration itself. Clients on our Premium support plan have major upgrades planned with them as part of the plan.
How it works
What the review involves
Stage 01
Inventory
Every custom rule, decoder, list, integration, active response, agent group and pipeline, and the agent versions and operating systems in use.
Stage 02
Classify
What carries over, what has a 5.0 equivalent, what must be rewritten and what is no longer needed.
Stage 03
Lab test
A 5.0 build in a lab, with a sample of your rules rewritten and your real log samples replayed through it.
Stage 04
Plan
The order of the move, the parallel-running period, rollback, and the effort and price of each stage.
Stage 05
Walkthrough
An hour with your team on the findings and the decision of when to move.
Questions
Questions about upgrading to Wazuh 5.0
Can we upgrade Wazuh 4.x to 5.0 in place?
No. Wazuh's documentation says an in-place upgrade from 4.x is not supported. The move is a new 5.0 deployment run alongside the old one, with agents and rules moved across in stages.
When should we move to Wazuh 5.0?
Not while it is a release candidate. Once it is generally available and its first fixes have shipped, plan the move for a quiet period, after a readiness review has sized the work.
How much does a readiness review cost?
£3,150 + VAT for up to 100 agents, £5,250 + VAT for up to 500 agents, and from £7,350 + VAT for larger estates, fixed after a short call.
Will our custom rules still work?
Not as they are. 5.0 has a new detection engine and rule syntax, and fields must match the new schema, so custom rules and decoders need rewriting. The review tells you how many and how long.
Do we have to move at all?
Not immediately. Wazuh 4.14 continues to receive releases. But 5.0 is where the platform is going, so plan for it.
Wazuh 5.0
Plan the move before it plans you.
Thirty minutes on what your deployment carries and a fixed price for the review.