Deployments
Sized for the network you run today.
The same platform, planned differently. Access model, contention shape and address strategy change with the network — the gateway does not. Pick the profile closest to your operation.
What changes between profiles
- Access model
- PPPoE / IPoE / QinQ
- Contention shape
- PON · sector · backhaul
- Address strategy
- public / CGNAT
- Redundancy
- single / paired
- Provisioning
- CLI / API / OSS
What does not change
- The same binary and the same release
- The same configuration model and CLI
- The same capability set, all nine areas
01 Deployment profiles
Four network shapes, one gateway
Each profile has its own page covering what matters for that network and how the deployment is put together.
Fiber ISPs
FTTH and PON aggregation with per-ONT VLANs and shaping that models each PON port’s real contention.
- Access model
- PPPoE or IPoE, single-tag or QinQ per ONT
- Bandwidth
- Per-subscriber shaping nested under PON-port aggregates
Wireless ISPs
Fixed wireless access where DHCP-based subscribers and MAC identity avoid session overhead on the radio.
- Access model
- IPoE with MAC or circuit identity; PPPoE also available
- Bandwidth
- Per-subscriber shaping under sector or backhaul aggregates
Regional ISPs
One gateway pair covering the whole footprint, with regional pools and a single place to answer support calls.
- Access model
- PPPoE and IPoE together on one gateway
- Operations
- Staged configuration with commit, rollback and audit trail
Telecom operators
Wholesale QinQ access domains, redundant gateway pairs, and provisioning driven from existing OSS workflows.
- Access model
- QinQ wholesale domains, PPPoE and IPoE
- Provisioning
- API-first, with CLI and staged configuration behind the same contract
Size a gateway for your network
Bring your subscriber counts, access model and address plan. We size against your hardware, not a product tier.