Zedmos

Licensing

How licensing works

Three tiers, one rule that never changes: a lapsed licence makes the console read-only and never stops a firewall. Prices are quoted, not published - the button at the end of the page asks for one.

Free

Evaluate it on your own traffic

  • 3 firewalls, 30 days, every feature
  • One organisation
  • Hosted console at console.zedmos.com, or self-hosted
  • After 30 days the console goes read-only. It is never blocked, and no firewall stops enforcing
  • Your configuration survives an upgrade
Start free

Team

One organisation, a fixed number of firewalls

  • Licensed per firewall, in packs
  • One organisation with branches
  • Subscription by card; the invoice comes from Germany
  • A missed payment starts a 14-day grace period with full function, then read-only
  • No per-device count on the firewall
Request a quote

MSP

Many organisations, billed monthly in arrears

  • Multi-tenant: unlimited organisations, unlimited firewalls
  • Billed on the firewall count at month end, for the month that just ran
  • A ramp period at the start; a committed minimum, if any, is agreed in the partner contract
  • 21-day grace period on a missed payment, then read-only. Firewalls keep enforcing throughout
  • White-label on the console and on the box
  • Not-for-resale licences for your lab and demos, on request
Request partner pricing

Prices are quoted, not published. A quote names the tier, the firewall count, the term and the invoice entity, and it is the price you renew at.

What happens when a licence lapses

Enforcement is never the lever. The console degrades in steps; the firewalls do not.

  1. ActiveEverything works.
  2. GracePayment failed or the term ended: full function, with a banner. 14 days on Team, 21 on MSP.
  3. Read-onlyChanges in the console are refused. Every firewall keeps enforcing the policy it holds. Free stays here indefinitely.
  4. BlockedAfter a long lapse on a paid tier, the console's admin interface closes. The firewalls still enforce. Nothing is deleted.

Not-for-resale licences

A partner needs a firewall they can break. An NFR licence covers a lab and a demo estate at no charge, for as long as the partnership stands. It is granted on request, not gated behind a tier.

Per firewall
The unit of licensing. No device count
Monthly
MSP tier, billed in arrears on the month-end count
Never
A lapsed licence drops a packet
Any box
Hardware is not in the licence

What service providers ask for, and where it is in the model

Monthly, in arrears

The MSP tier bills for the firewalls that were running at the end of the month that just ended. Onboard a client in March, pay for March in April. Offboard one, and it leaves the count the same day.

Multi-tenant from the first firewall

Unlimited organisations and unlimited firewalls on the MSP tier. Delegation by role across organisation, branch and firewall - a technician sees the client they are assigned, a client can see their own estate read-only.

No hardware in the licence

The licence does not know which box it runs on. The OPNsense or pfSense CE appliance the client already owns, a validated x86 configuration, or a branded build from your OEM partner - the count is the same.

Hosted or self-hosted, same licence

Run the console as a container on your server, or use console.zedmos.com operated from Frankfurt. Move between the two without re-licensing anything.

Your brand

White-label on the console and on the firewall interface is part of the MSP tier, not a separate SKU.

A lab you can break

Not-for-resale licences for a partner's lab and demo estate, at no charge, on request. Granted because a partner who can show the product sells it - not gated behind a tier or a revenue threshold.

Licensing & partner pricing: sales@zedmos.com

Request a quote