One subscription, sized to your estate.
Every module, every connector and every copilot comes with the platform, on one contract. What follows is how the number is arrived at, and why it is not printed here.
Three commercial decisions, made once.
They are the reasons the number behaves the way it does, and they are the same for every customer.
One platform subscription
All 15 modules, 2,000+ connectors and 41 named copilots come with the platform. There is no module you unlock later and no connector billed on its own.
Sized to your estate
The number follows the estate under management: how much data moves, how many sources feed it, and how many pipelines run. A small estate costs less to license and less to run.
Never per seat
Adding an analyst to the platform does not change the bill. Per-seat pricing quietly charges you for adoption, which is the opposite of what a governed platform should encourage.
Six inputs, in both directions.
Each of these raises the figure as it grows and lowers it as it shrinks. You will see where your estate sits on every one of them during scoping.
Estate size
Data under management and the volume moving through the platform. This is the largest single input.
Sources and pipelines
How many systems connect, and how many pipelines run against them. Two hundred pipelines is a different platform from twenty.
Deployment model
Your cloud, your own region, on-premises, or fully air-gapped. Each has a different delivery and support profile, and we will show you where yours lands during scoping.
Integration surface
Standard connectors are included. A source with no connector, or a system that needs a bespoke route, is scoped work.
Scope of automation
How much runs without a person: scheduled pipelines and dashboards, or ProcBot procedures and Sherlock remediations acting on production.
Managed operations
Whether your team runs the platform or ours does. Priced separately from the licence.
The POC is a paid engagement, and that is the point.
A free pilot is a demo with your logo on it. A paid one is a project with a success measure, an engineer assigned, and a date.
Your data, your connectors
It runs on your systems in your environment. Nothing is demonstrated on sample data that behaves better than yours does.
A success measure agreed before it starts
Written down at the start, assessed at the end, and reported honestly whichever way it goes.
Credited if you proceed
The fee is credited into the platform subscription. If you decide against it, you keep the findings and the architecture we produced.
Run it yourself, or have our team run it.
The subscription covers the platform. Operating it is a separate choice: your team can run it, or VisionWaves engineers can operate it alongside you under a scoped engagement priced on its own.
This is worth raising early rather than late. The platform is young enough that the deepest operational experience with it sits with the people who built it, and a plan for that is part of a serious deployment.
Why there is no figure on this page.
Enterprise estates differ by orders of magnitude. A single published number would be wrong for almost everyone reading it: high enough to lose the teams it would suit, low enough to mislead the ones it would not.
Scoping takes about a week. It produces a figure grounded in your own systems, your own pipeline counts and your own deployment constraints, and you get the architecture that came out of it whether or not you buy anything.
Seven pricing questions, answered plainly on the FAQ: what moves the number, whether the POC is paid, and why there is no figure on this page.
Get a figure grounded in your estate.
A scoping conversation with an engineer, then a number you can take to a budget holder.