Single site
One datacenter, one operator
To be announced
- One site, unlimited switches and ports
- Traffic measurement and billing basis
- Rack elevation and inventory
- Persian and English interface
- Community documentation
Pricing
Pricing
What each tier contains is settled. The figures are not, and this page would rather say so than show a number that has to be un-quoted later.
Prices are being finalised. What is listed below is what each tier includes; get in touch through the documentation if you need a figure before this page has one.
Operator
Several sites, a team
To be announced
- Everything in Single site
- Unlimited sites
- External monitoring sources
- Proxies for out-of-band ranges
- Roles and individual exceptions
- Programmatic access
Estate
Multi-region, with support
To be announced
- Everything in Operator
- Multi-region deployment
- Priority support
- Assisted migration from an existing system
About pricing
What is counted?
Sites and features, not ports and not traffic. A tier that charges by the port punishes you for measuring more of your own network, which is the opposite of the point.
Is it self-hosted?
Yes, always. It runs on your machine, on your network, against your database. Nothing about the licensing changes that.
Can I run it against my estate first?
That is the recommended way to adopt it. Import the estate, measure alongside whatever you already run, and compare over a full billing cycle before anything depends on it.