Skip to content

Carrier-grade telecom charging and execution Built and operated at scale.

200M+ events/day · <1 ms latency · live telecom environments

Telecom

We design and operate carrier-grade platforms for telecom operators (MNO, MVNO, MVNE). Our systems cover real-time charging, service execution, interconnect, messaging, TAS and service orchestration, enabling smooth transitions to 5G, IoT and cloud-native networks.

FLAGSHIP

Online Charging System (OCS)

3GPP Rel-15/16 compliant charging platform for MNO, MVNO and MVNE operators. Real-time rating, policy control and quota management. Cloud-native, BSS/OSS-ready, with AI-assisted fraud detection and full 5G SA support at scale.

Prepaid & Postpaid Charging (Gy/Ro): Real-time quota management, balance deduction and mid-session policy updates for voice, data and SMS.
5G SA: Nchf Interface: Native HTTP/2-based charging for 5G Standalone deployments, aligned with 3GPP Rel-15/16.
Roaming & Wholesale Billing: Inter-operator settlement, TAP/RAP processing and real-time roaming charging via Diameter.
Policy & Charging Rules (PCRF/PCF): Dynamic QoS, bandwidth throttling and fair-use enforcement integrated with OCS rating.
IoT & M2M Charging: Lightweight session handling for high-volume, low-bandwidth device populations at carrier scale.
AI-Assisted Fraud Detection: Real-time anomaly scoring on charging events. Flags and blocks suspicious sessions before CDR export.
100M+
Subscribers
99.999%
Uptime SLA
<1 ms
Avg latency
Online Charging System deployment architecture
SLEE — Service Logic Execution Environment
FLAGSHIP

Service Logic Execution Environment (SLEE)

JAIN SLEE-compatible runtime for deploying and executing carrier-grade service logic at scale. Sub-millisecond event processing, built-in concurrency management and full session lifecycle control, without platform downtime.

IN Services (CAMEL Ph. 1–4, INAP): Prepaid call control, CLI screening, number translation and routing logic.
VoLTE / IMS Call Control: SIP-based session handling and policy enforcement for LTE and 5G voice.
Prepaid SMS & USSD: Real-time balance checks, service menus and OTA interactions over SS7 and Diameter.
Roaming Triggers: Home-routing and roaming charging integration via Diameter and MAP interfaces.
Custom Service Logic (SBBs): Deploy new service building blocks into a live production environment with zero downtime.

Partners & Clients

We work with trusted partners and clients in telecom and energy, and build on proven global technologies.

Tier-1 and Tier-2 operators · energy communities · technology partners worldwide

FAQ

Short answers to common questions. For anything else, contact us.

What is your high-availability and disaster recovery architecture?

Our platforms are deployed in active-active multi-node configurations with automatic failover. We support multi-AZ and multi-region deployments depending on the client's infrastructure. All stateful components are backed by replicated storage with RPO < 1 minute and RTO < 3 minutes under standard SLA tiers.

Do you support on-premise deployment, or is it cloud-only?

We support both. Our platforms run on-premise, in private cloud (VMware, OpenStack), and on public cloud (AWS, Azure, GCP) via containerised Kubernetes deployments. For regulated clients — municipalities, cooperatives, and carriers with data sovereignty requirements — on-premise remains a primary deployment model.

How does migration from a legacy OCS or billing system work?

We provide a structured migration methodology: parallel-run period, zero-downtime cutover toolchain, and subscriber/data migration tooling. Typical migration timelines range from 3 to 9 months depending on subscriber volume, integration complexity, and regulatory requirements. We have executed migrations from legacy Comptel, Convergys, and custom in-house OCS platforms.

What does your SLA structure look like?

Standard SLA tiers cover 99.9%, 99.99%, and 99.999% platform availability. Enterprise+ engagements include dedicated SRE support, 15-minute incident response, and monthly SLA reporting. SLA scope covers platform availability, API response time, and CDR delivery completeness. Penalty and remediation terms are defined per contract.

What compliance and standards certifications does the OCS carry?

Our OCS implements 3GPP Rel-15/16 charging interfaces (Gy/Ro for legacy, Nchf for 5G SA), aligned with TM Forum Open API standards. The Energy Platform handles KSeF-compliant invoicing and CSIRE data exchange. We operate under GDPR-compliant data processing frameworks. ISO 27001 certification is in progress; current security controls align with ISO 27001 Annex A requirements.

What does a typical deployment timeline look like?

A greenfield OCS deployment takes 3 to 6 months from contract signature to live traffic, depending on integration scope and operator readiness. Energy Platform deployments for cooperatives typically complete in 6 to 10 weeks. All engagements begin with a scoped architecture review and a joint integration plan before any code is deployed to production.

Contact us