Open one live message
Ask us to open any message: pipeline steps with timings, the route it took and the PDUs on both sides, decoded next to the hex.
Why Auvia
Why Auvia Gateway: reasons you can check
Choosing an SMS platform should rest on evidence, not on sales copy. These are the reasons operators and aggregators pick Auvia, and how you can verify each one before you sign.
One platform, SMPP to invoiceCharged exactly onceWhite-labelCloud or on-premise
For resellers and aggregators
Built for selling traffic, not just sending it
Many SMS tools are only a client that sends to one provider. Auvia gives your own customers an SMPP server and an HTTP API, connects you to many suppliers, and keeps the price, cost and margin of every segment, so a wholesale or reseller business runs on one system.
- SMPP 3.4 server with TLS, and an HTTP API, for your customers
- SMPP 3.4/5.0 and HTTP suppliers, SS7 through a connected gateway
- Least-cost, weighted, split and quality pools
How a route is chosen
Illustrative rules, pool and prices.Changes reach live traffic within seconds.
Accounts that close
No lost messages, no double charges
A message is acknowledged only after it is stored, priced when it is accepted and charged once, even when parts are retransmitted. The same record drives the receipt, the statistics and the invoice, so the month closes on the day's numbers.
- submit_sm_resp only after the message is stored
- Retransmitted parts neither sent nor billed twice
- Revenue, supplier cost, HLR cost and margin per message
One message, end to end
RequestReceipt
The acknowledgement is sent only after the message is stored. Retransmitted parts are neither sent nor billed twice.
White-label
Your brand is the one your customers trust
The customer portal and the operator panel carry your name and logo on your domain. Customers send campaigns, read reports, check their balance and manage their own API keys, while routing and prices stay with you.
- Your name, logo and domain
- Campaigns, chats, reports, invoices and API keys
- Customer data isolated per account by the server
Verify it
If you need to verify this, good
Regulated operators and careful buyers should check every claim. This is how you can.
Measure it yourself
Throughput and latency are measured on your routes and hardware during a technical evaluation, not quoted from a brochure.
Read the limits
Parts per message, sends per message, export sizes and retention are published as the code enforces them.
Keep the data at home
On-premise installations keep traffic and personal data on your infrastructure, for data residency and security reviews.
What every installation gets
Engineering choices behind the platform
No restart for routine work
Routes, prices and trunk settings reach live traffic in seconds; trunk changes apply to open SMPP sessions.
Durable by design
Messages are stored before they are acknowledged, and a failed store returns an error instead of losing the message.
Shared state across processes
One SMPP listener owner with shared live session state, and scheduled jobs coordinated across nodes.
Monitoring and alerts
Bind uptime, queues and live traffic, with alerts by email, Telegram, Slack and web push, and an audit log of every user action.
Compare
Auvia or a platform you assemble yourself
| Assembled from separate tools | Auvia Gateway | |
|---|---|---|
| SMPP for customers and suppliers | Separate server and client, configured apart | One platform, one record per message |
| Routing and least cost | Scripts or spreadsheets | Rules, pools and a Routing Analyser |
| Billing | Reconciled at month end | Per segment at acceptance, charged once |
| Support and disputes | Logs spread across systems | Pipeline timings and PDUs per message |
| Customer self-service | Built in-house | White-label portal included |
| Where it runs | Wherever each tool runs | Dedicated cloud installation or on-premise |
FAQ
Questions before choosing
What makes Auvia different from other SMS platforms?
It is one platform for selling traffic: an SMPP server and HTTP API for your customers, SMPP and HTTP connections to suppliers, routing, per-segment billing, invoices and a white-label portal, all working on the same record of each message.
What throughput can I expect?
We do not publish a TPS figure, because it depends on your hardware, suppliers and configuration. Throughput and latency are measured on your own routes during a technical evaluation.
Can it run on our own infrastructure?
Yes. Every installation is dedicated to one customer. Operators can run it on their own servers, domain and database, delivered as a compiled container image.
Can our customers see our brand instead of yours?
Yes. The operator panel and the customer portal carry your name and logo, on your domain.
How do we check what you say?
Ask us to open a live message in the demo, read its PDUs and pipeline timings, and then measure the platform on your traffic. The limits on this site are the ones the code enforces.
Does the AI console send our data to an AI provider?
Only masked data. Before anything leaves the platform, phone numbers, senders, texts, emails, customer and supplier names, system IDs and IP addresses are replaced by placeholders. Masking can be turned off only for a local model on your private network.
Keep exploring
