Priced per deployment, not per seat.
Your user count never changes the bill. Shield and Alertio are licensed separately or together, and every plan starts with a conversation — access is by invitation while we onboard early clients.
One product, in a non-production environment, with our help getting it standing.
Time-boxed. At the end we both decide whether to continue.
Includes
Shield or Alertio running in production, licensed annually per deployment.
Scope, environment count and support level set the figure. We quote after a call.
Everything in Pilot, plus
Both products as one engagement — the front door and everything behind it.
One onboarding, one point of contact, one renewal date.
Everything in Production, plus
We publish no list price because scope moves it too much to be useful — environment count, tenant count, and whether you want us on a call at 2am all change the number. We would rather quote you honestly than publish a figure that never applies to anyone.
What each plan includes.
Every capability below is built and running today. Nothing here is on a roadmap.
| Capability | Pilotevaluation | Productionone product | Programboth products |
|---|---|---|---|
| Scope | |||
| Products included | One | One | Both |
| Environments | One, non-production | Production + staging | Production + staging |
| End users | Unlimited | Unlimited | Unlimited |
| Tenants or agents | 1 | Multiple | Multiple |
| Self-hosted | ✓ | ✓ | ✓ |
| Identity & access — Shield | |||
| Identity sources (MySQL, LDAP/AD) | 2 | 2 | 2 |
| MFA methods | 6 | 6 | 6 |
| CAPTCHA providers | 5 | 5 | 5 |
| Network policy signals | 13 | 13 | 13 |
| Device posture checks | 11 | 11 | 11 |
| Read-only against your user store | ✓ | ✓ | ✓ |
| Detection & response — Alertio | |||
| Correlation patterns | 7 | 7 | 7 |
| Response action types | 8 | 8 | 8 |
| Transparent risk scoring | ✓ | ✓ | ✓ |
| Shield sign-ins correlated in Alertio | — | — | ✓ |
| Visibility | |||
| Hash-chained audit log | ✓ | ✓ | ✓ |
| Offline audit verifier | ✓ | ✓ | ✓ |
| SIEM export (CEF, RFC 5424) | ✓ | ✓ | ✓ |
| Outbound webhooks | 17 events | 17 events | 17 events |
| Prometheus metrics | ✓ | ✓ | ✓ |
| Operations | |||
| Encrypted backups, verified daily | — | ✓ | ✓ |
| Key rotation runbooks | — | ✓ | ✓ |
| Offboarding with an undo window | — | ✓ | ✓ |
| Term | Time-boxed | Annual | Annual |
| Support | Setup help | Business hours | Priority |
Before you ask.
The ones we get every time.
- Why is there no price on this page?
- Because scope moves it too much for a list price to mean anything. Environment count, tenant count and support level all change the figure. A short call gets you a real number rather than one you have to caveat.
- Can we self-host?
- Yes, and most people should. Both products ship as Docker Compose stacks designed to run inside your own infrastructure. Shield's AI analysis defaults to a local model so your code never leaves the deployment.
- What happens to our users?
- Nothing. Shield reads your existing user store and never writes to it. If you remove Shield, your application still has every account it had before.
- Do we need Wazuh already?
- For Alertio, yes — it is a layer on top of a Wazuh deployment rather than a replacement for one. We can help you stand one up as part of a pilot.
- Is there a free tier?
- Not a self-serve one. There is a pilot, which is free for its duration and comes with our time — which at this stage is more useful to you than a rate limit.
- What are we actually buying?
- A licence, the software, and us. VERISCO is a final-year engineering project, so you are buying working systems and direct access to the people who built them — not a support contract from a company with a sales floor.
Tell us what you run.
The fastest way to a number is a short conversation about your environment — the framework, the user store, and how many places it runs.