XenonSMS is a production SMPP softswitch for A2P and P2P traffic. Multi-lane vendor binds with automatic lane failover, real-time rating and credit control, and normalized delivery receipts pushed back to every client — running as one connected pipeline, not a chain of scripts bolted together.
Every message that enters XenonSMS passes through the same traceable path — from the moment a client bind opens to the moment a rated CDR is written.
A softswitch earns trust in the moments things go wrong — a vendor lane drops, a client connection goes idle, a route table has a gap. XenonSMS is built to surface those moments, not hide them.
A Django and Celery core built specifically for high-throughput SMPP operations — not a general messaging framework bent into shape.
Define and prioritize routes by prefix, MCC/MNC, or vendor, with test route groups isolated from production traffic before a change goes live.
Import and version ratesheets, with real-time balance checks against a live credit limit on every submit — not a nightly batch job.
Watch throughput, vendor lane health, and per-client submit-failure reasons as they happen, broken down by cause — routing, credit, or vendor.
One consistent delivery status model regardless of how each downstream vendor reports it, pushed back to the client's SMPP session and tracked to ACK.
Queryable records built for dispute resolution — every message traceable from submission to settlement.
Idle and stuck client connections are detected and recycled automatically, so one dead session can't quietly block delivery for everyone behind it.
Every client connection is authenticated, scoped, and rate-limited individually — access control that's enforced on every bind and every submit, not a policy document.
Every client binds with its own system_id and password — no shared credentials, no ambient trust between accounts.
Restrict which source IPs are allowed to bind against a given account, enforced at connection time, not after the fact.
Client and vendor balances are checked against a live limit on every submit — a message can't be accepted past a credit ceiling and reconciled later.
TPS caps, session windows, and global concurrency limits apply per connection and per client, so one account can't starve the platform for everyone else.
Every message is traceable end to end — submit, routing decision, vendor attempt, delivery receipt, and billed CDR — queryable for dispute resolution.
Test route groups run on separate routing paths from production traffic, so a route change can be verified before it ever touches live clients.
The things that come up in the first onboarding call — answered up front.
Transmitter, receiver, and transceiver binds over SMPP 3.4. Most clients connect as transceiver so submit and delivery-receipt traffic share one session.
Vendor connections run as multiple parallel SMPP lanes. A route only flips to offline once every lane for that vendor has genuinely dropped — a single lane blip doesn't take down the route or interrupt the rest of your traffic.
Real-time. Client and vendor balances are checked and deducted at submit time, against a live credit limit — cost and margin are known before a message leaves the queue, not reconciled after the fact.
Vendor DLRs arrive in whatever format each carrier uses; XenonSMS normalizes them to one consistent status model, matches each receipt back to its originating message, and pushes it to your SMPP session — tracked through to your acknowledgment.
Idle and stuck client sessions are detected and automatically recycled. A dead connection on your end doesn't sit there indefinitely blocking delivery receipts meant for you, and it doesn't affect other clients' sessions.
Yes — test route groups are configured on a routing path fully separate from production, so a route or rate change can be verified with real traffic before it's switched on for live clients.
Each client binds with its own SMPP credentials, and access can be further scoped to specific source IPs. There's no shared account or credential reused across clients.
Reach out to plan your integration — SMPP binds, route setup, and rate onboarding, on your timeline.
We'll get back to you at the email you provide, usually within one business day.