About WISPGate

The roots of WISPGate go back long before the WISPGate name itself existed.

For more than 20 years, the founders and core team behind WISPGate were deeply involved in the ISP and telecom industry. Their experience ranged from wireless ISP deployments and MikroTik consulting to FTTx operations, AAA systems, hotspot deployments, LTE environments, and operational consultancy for ISPs across multiple regions.

During those years, one major pattern became obvious:

Most ISPs were operationally fragmented.

Operators were forced to combine disconnected systems for billing, customer management, hotspot control, network provisioning, support tickets, inventory tracking, monitoring, and communication. The result was operational chaos, duplicated data, inconsistent workflows, and massive dependency on spreadsheets, manual processes, and tribal knowledge.

At the same time, the team had already started exploring software development specifically for the ISP market.

One of the earliest projects was HotGate — a cloud-based hotspot controller and WiFi management platform designed to centralize hotspot operations and simplify public WiFi deployments. HotGate became an important experimental foundation because it introduced the team to large-scale authentication flows, centralized device management, customer lifecycle behavior, usage control, and cloud-oriented operational architecture.

Those experiments laid the groundwork for what would eventually evolve into WISPGate.

In 2019, while providing consultancy services for one of their ISP customers, the team started building what was initially intended to be a relatively small experimental RADIUS management system.

The goal was not to create a massive commercial product.
The goal was simply to solve operational pain points that existing systems were not solving properly.

The original focus was heavily operational:

• Subscriber authentication
• Service enforcement
• Package management
• Operational automation
• Better integration with MikroTik environments
• Cleaner operational visibility
• Reduced dependency on fragmented tools

Very quickly, the project started expanding beyond authentication.

The team realized that the real problem ISPs faced was not just authentication or billing individually — the real problem was operational fragmentation. That realization fundamentally changed the direction of the project.

As development continued throughout 2019, the project evolved from an experimental RADIUS platform into a broader operational framework for ISPs.

The team combined:

• 20 years of ISP operational experience
• Real-world field deployment knowledge
• Consultancy insights from multiple ISP environments
• Five years of accumulated software development experience
• Lessons learned from HotGate and earlier operational systems

The result became WISPGate.

Rather than behaving like a traditional “billing system,” WISPGate was designed from the beginning to think operationally. The philosophy was simple:

The billing system should not live separately from the network.
The support system should not live separately from the subscriber lifecycle.
The operational data should not live inside spreadsheets.
And the ISP should not need 15 disconnected systems to run a telecom operation.

This philosophy became the foundation of WISPGate.

In March 2020, WISPGate officially went into live production for its first major ISP customer.

At the time, the world was entering a global pandemic, and ISPs were facing unprecedented traffic demands, operational challenges, and scaling requirements.

During this critical period, WISPGate proved its operational value.

Instead of requiring massive engineering teams to manage subscriber operations, WISPGate automated:

Because WISPGate was built by network engineers, it behaved the way an ISP needed it to behave.

The success of this initial deployment validated the concept: An ISP Operating System was far more valuable than just another billing platform.

Between 2020 and 2023, WISPGate underwent aggressive development.

The platform shifted from a pure RADIUS and billing engine into a massive operational ecosystem.

Major architectural expansions included:

• Advanced CRM architecture: Moving beyond simple subscriber management into lifecycle tracking.
• Network Inventory (OSS): Connecting physical devices directly to subscriber profiles.
• Helpdesk & Ticketing: Building a telecom-specific support environment.
• API & Integration Layer: Connecting with external payment gateways, SMS providers, and accounting platforms.
• Multi-Tenant Capabilities: Allowing large operations to manage multiple brands from a single core.
• Advanced Network Visibility: Creating direct integrations with MikroTik, Ubiquiti, and standard network environments.

During this period, WISPGate also expanded its deployment architecture. Recognizing that ISPs have varying security and infrastructure requirements, the platform was developed to support:

• Cloud Deployments (SaaS)
• On-Premise Deployments
• Dedicated Private Cloud Environments

This flexibility allowed WISPGate to scale from small wireless operators to enterprise-level telecom environments.

Every feature inside WISPGate is driven by a strict operational philosophy.

This philosophy dictates how the platform is built, how it scales, and how it behaves in production environments.

• Consolidation Over Fragmentation: The system must eliminate the need for disconnected applications.
• Automation Over Manual Labor: If an action can be automated, the system should do it.
• Network-Centric Design: Software must understand network hardware. If the software cannot communicate with the router, it is useless to an ISP.
• Operational Visibility: The operator should never have to guess what happened. Every financial transaction, RADIUS session, configuration change, and customer interaction must be traceable.
• Flexibility Without Complexity: The platform must be powerful enough for enterprise operators but accessible enough for small WISPs.

The core mission of WISPGate is to eliminate operational chaos for Internet Service Providers.

We exist to help operators transition from surviving daily operations to actively growing their networks.

We achieve this by providing a unified, automated, and deeply integrated platform that acts as the central brain of the ISP.

The vision of WISPGate is to become the global standard for ISP operations.

We envision a future where telecom operators do not waste resources managing broken software integrations, but instead rely on a single, intelligent operating system that automates the network, manages the business, and protects the customer experience.

Today, WISPGate is a mature, high-performance operational ecosystem. It acts as the central nervous system for ISPs, managing:

• Hundreds of thousands of subscriber sessions
• Complex financial transactions and recurring billing cycles
• Enterprise-level ticketing and support workflows
• Massive inventory databases and hardware tracking
• Automated network provisioning and RADIUS enforcement
• Extensive API integrations with global payment and communication providers

The platform is no longer an experiment. It is a production-grade infrastructure platform relied upon by operators who require stability, speed, and deep operational control.

WISPGate is continuously evolving.

Our engineering focus remains entirely on solving telecom operational challenges.

Future development is heavily focused on:

• AI-assisted network diagnostics and support automation
• Deeper native integrations with FTTx and GPON infrastructure
• Enhanced machine-learning-driven fraud prevention and billing protection
• Broader expansion into carrier-grade network orchestration

WISPGate is not just a software product. It is an evolving operational intelligence platform designed by operators, for operators.

We built WISPGate because we needed it.

We grew WISPGate because the industry needed it.

And we continue to develop WISPGate because the future of telecom requires intelligent, unified, and automated operational platforms.

Welcome to WISPGate.
The Operating System for ISPs.