Architecture – Deployment Models

How WISPGate Deploys Into Your Environment

Flexible deployment models supporting cloud, on-prem, and hybrid environments

Cloud Deployment

Your cloud model clearly positions WISPGate as a centralized control plane sitting above the network layer.

At the top, the WISPGate stack (Customer Portal, Billing Engine, AAA/RADIUS) is deployed in the cloud, acting as a unified orchestration layer. All subscriber traffic flows from the Internet through the Security/Edge Gateway and BNG, then into the operator’s network infrastructure—but critical control decisions (authentication, billing, service logic) are handled centrally in the cloud.

This creates a powerful separation:

network stays local
logic moves to the cloud.

The Result:

Faster deployment(no heavy infra setup)

Centralized updates and feature rollouts

Reduced operational overhead

But more importantly: WISPGate becomes the single source of truth — coordinating authentication, billing, and customer experience across the entire network — without being physically tied to it.

On-Prem Deployment

This model flips the control boundary.

Here, WISPGate is deployed inside the operator's infrastructure, directly connected to the BNG and core network components. Instead of routing control externally, the system operates within the same environment as network elements, enabling tighter coupling between:

Subscriber sessions
Network behavior
Billing and AAA decisions

This is critical for operators who require:

Full data sovereignty

Low-latency control loops

Strict regulatory compliance

In this setup: WISPGate is not just managing the network — it is embedded within it.

The architecture shows that authentication (AAA), billing, and customer services sit side-by-side with network control, allowing real-time enforcement and decision-making without external dependency.

Hybrid Deployment Recommended

This is where things get interesting—and where your architecture actually differentiates.

The hybrid model splits WISPGate into:

Active (on-prem)

Handling real-time operations

Backup / Cloud layer

Acting as redundancy + extended control

Both stacks (cloud and on-prem) are synchronized via database replication, ensuring consistency across environments.

This enables a dual advantage:

Local system handles real-time network interaction

Cloud layer provides resilience, backup, and scalability

So if:

On-Prem Fails

Cloud layer activates and takes over seamlessly — zero service interruption for subscribers.

Cloud Fails

Local system continues operating independently — your network never stops.

That's not just hybrid—that's operational continuity by design

This model also allows gradual migration:

Start on-prem

Extend to the cloud

Eventually operate in fully distributed mode

High Availability (Hybrid ONLY)

Single-Site, Active/Active (Scale-Out HA)

Multiple stateless WISPGate app/worker nodes behind LB — horizontal scaling

DB cluster (multi-node, master + replicas / Galera / cluster manager)

Redis / queue cluster for caching, sessions, tasks

Multiple AAA / RADIUS / PCRF / HSS / OCS nodes all active — load distribution

Diameter / RADIUS / SIP endpoints configured across all nodes

✓ Pros

Real throughput scaling — can handle large subscriber counts and high request rates
Smooth rolling upgrades, no downtime for maintenance
Better performance isolation (billing load, AAA load, UI load separated)

⚠ Cons

Increased complexity — requires mature DevOps / monitoring/orchestration
DB cluster management, split-brain risk, replication consistency challenges
Configuration errors can cause worse failures than a single-node

Best For

Large clients (100k–500k+ subs)
When you expect growth, heavy traffic (especially LTE + real-time billing), multiple services (IPTV, VoIP, Internet)

Choose Your Deployment

Learn how WISPGate’s flexible deployment models can be tailored to your specific network and operational needs.

Book Demo Explore Platform

Technical Architecture

Explore the security models, database structures, and API access layers that complete the WISPGate technical ecosystem.

Security Model Database Structure