Architecture High-Level System

High-Level System Architecture

Traditional ISP environments are built on disconnected systems—billing, CRM, and network tools all operate independently, stitched together through manual integrations, scripts, and constant reconciliation.

Deployment Models View Features

From Fragmented Systems to Unified Control

This approach creates:

  • Data inconsistency across systems
  • Slow provisioning and activation
  • Heavy operational overhead
  • Continuous dependency on custom integrations
WISPGate eliminates this fragmentation by introducing a unified operational architecture where all core functions operate within a single system.
Traditional OSS-BSS vs WISPGate

Unified Platform Architecture

At the core of WISPGate is the Subscriber Lifecycle Engine—a centralized layer that manages the entire journey:

Lead Customer Activation Billing Support

Instead of separate systems, WISPGate integrates:

  • CRM Platform → customer management and operations
  • Billing Engine → rating, invoicing, payments
  • AAA / RADIUS → authentication and session control
  • OSS & Inventory → network topology and assets
  • Automation Engine → workflows and orchestration
  • Customer Portal → self-service interface
  • Mobile / LTE Core → telecom-grade connectivity
  • Integrations API → external ecosystem connectivity

Everything connects into one lifecycle, not across multiple tools.

WISPGate Full Platform Architecture

Platform Ecosystem Architecture

Beyond internal modules, WISPGate extends into a full operational ecosystem—connecting business, network, and customer experience into a single flow.

Network Control & Provisioning Layer

This is where WISPGate becomes different. Instead of treating the network as an external system, WISPGate directly integrates with:

  • NAS / BNG
  • Access Points / Towers
  • OLT / Fiber infrastructure
  • Routers and core network devices

This enables:

  • Real-time service activation
  • Automated provisioning
  • Usage-aware billing enforcement
  • Immediate network-level control

Around this core:

  • Support & Ticketing
    feeds operational workflows
  • Marketing & Sales
    connects lead generation to activation
  • Customer Portal
    enables user-driven actions
  • Operations / NOC / Finance / HR
    operate from the same data layer
WISPGate Platform Ecosystem Architecture

The Real Shift

Traditional OSS/BSS

  • Multiple systems
  • Data sync problems
  • Reactive operations

WISPGate

  • One platform
  • One workflow
  • One source of truth

Key Architectural Principles

1. Lifecycle-Centric Design

Everything revolves around the subscriber lifecycle—not systems.

2. Native Network Integration

Billing and CRM are directly tied to network control via AAA/RADIUS and provisioning.

3. Automation by Default

Workflows are built-in, not added later.

4. Single Source of Truth

All departments operate on the same real-time data.

5. OSS + BSS Convergence

No separation between business systems and network systems.

Bottom Line

WISPGate is not an OSS/BSS stack.

It is a unified operational platform that merges customer management, billing, network control, automation, and service delivery into a single system.

Book Demo Back to Architecture