auviaGateway
A2P SMS gateway platform

The SMS gateway platform for operators and aggregators

Simple to launch, ready for carrier traffic. One platform from submit_sm to invoice, in the cloud or on your servers.

Dashboard › Analytics
Analytics dashboard
Operations
Debugging › Message Debugger
Message Debugger for one message
Support
Customer Portal › Overview
White-label customer portal
Your customers
Platform architecture
MT submitDelivery receiptMO inboundNumber lookup
Auvia Gateway architectureCustomers connect over SMPP, HTTP or the portal. Inside the gateway each message is validated, filtered, looked up, routed, rated, stored and acknowledged, queued and retried. Suppliers are reached over SMPP, HTTP or SS7 through a gateway. A configuration store, a live-state layer and a message archive form the data layer. CUSTOMERSSUPPLIERSDATA LAYER HLR / MNP providersDNS ENUM/NAPTR · HTTP AUVIA GATEWAYSMPP listener · API · workers Validatenumber · sender1Firewallsubmit + content2HLR / MNPreal operator3Routerules · LCR4 Ratereserve · once5Store · ACKthen submit_resp6Queuepriority · pacing7Retryreroute · retry8 ObserveMessage Debugger · PDU trace · Analytics · Alerts · Audit log Financeper-segment rating · balances · invoices · CDR export · REST API AssistAI console with masking · Routing Analyser · route tests SMPP customersSMPP 3.4 · TLSTX · RX · TRX bindsHTTP APIPOST /v1/smssigned webhooksCustomer portalcampaigns · chatswhite-label SMPP suppliersSMPP 3.4 / 5.0 · TLSper-trunk pacingHTTP suppliersJSON over HTTPSerror-code mappingSS7 networkvia SMPP-to-SS7gateway + profiles Configurationaccounts · pricesLive statequeues · countersMessage archiveCDR · analytics
Components of every installation, cloud or on-premise. Numbered steps follow one MT message.SS7 is delivered through a connected SMPP-to-SS7 gateway.
GDPR compliantISO 9001ISO/IEC 27001
  • Dedicatedone installation per customer, with its own database
  • Cloud or on-premiseyour servers, domain and brand if you need them
  • CertifiedISO 9001 and ISO/IEC 27001, GDPR compliant
Visit the Trust Center →
Working with us

How an evaluation works

From the first call to traffic on your routes, measured on your infrastructure.

  1. Discovery callYour traffic, protocols, suppliers and billing model.
  2. Console demoThe capabilities you care about, on the real operator panel.
  3. Technical evaluationThroughput and latency measured on your routes and hardware.
  4. InstallationCloud or on-premise, with your domain and your brand.
Start an evaluation →
Solutions

Choose the right setup for your business

The same platform, set up for the way you sell traffic.

Engineer monitoring traffic on three screens
For operators

Monetise A2P on your own infrastructure.

Install on your servers, deliver over SMPP or through your SS7 gateway, check numbers before paying a supplier and give enterprise customers a portal with your brand.

  • On-premise, compiled container image
  • SS7 profiles sent to your SMPP-to-SS7 gateway
  • HLR/MNP lookup and two-stage SMS firewall
Learn more →
Operations team working at their desks
For aggregators

Margin on every route, the same day.

Least-cost pools across suppliers, price lists imported from email, per-segment rating and statistics grouped the way you trade.

  • LCR, weight, split or quality per pool
  • Scheduled price changes with margin checks
  • Sell, buy, HLR cost and margin per client
Learn more →
Account team meeting about a customer portal
For service providers

Customers who serve themselves.

A white-label portal for campaigns, conversations, reports, invoices and API keys, while routing and prices stay with you.

  • Campaigns with lists, exclusions and scheduling
  • Chats by number for up to 180 days
  • Balance, invoices and payments for each customer
Learn more →
POST /v1/sms
For developers

An API next to SMPP, with the same rules.

Send over HTTPS with idempotency, receive signed receipts and inbound messages, and read balances, CDRs and invoices from a REST API.

  • POST /v1/sms, up to 1,000 messages
  • HMAC-SHA256 signed webhooks
  • Scoped keys with IP allowlists
Learn more →
Why Auvia

Why operators and aggregators choose Auvia

Choices that matter when every message is revenue.

Acknowledged after storage

submit_sm_resp is sent only once the message is safe in the store.

Charged exactly once

Price reserved at acceptance; retransmitted parts are not billed twice.

Live configuration

Routes, prices and trunks reach live traffic in seconds, no restart.

Traceable to the PDU

Pipeline timings and decoded PDUs for every single message.

Least-cost pools

Cheapest member per destination, or weight, split and quality.

White-label

Your name and logo on the operator panel and customer portal.

Cloud or on-premise

A dedicated installation, or your servers, domain and database.

Audited

Every user action and sign-in recorded for 90 days.

Resources

Guides and references

Practical material for teams that buy, run and integrate SMS traffic.

Reference

SMPP error codes

Every command_status value, with what the gateway returns.

FAQ

What evaluators ask first

Does it support both SMPP and SS7?
SMPP 3.4 and 5.0 natively, towards customers and suppliers. SS7 runs through a connected SMPP-to-SS7 gateway: Auvia manages the SS7 profiles and reads back the results, while the gateway handles the MAP/SIGTRAN side.
Which deployment options are available?
A dedicated cloud installation, or on-premise for large operators on your own servers, domain and database. Each installation serves one customer and carries your name and logo.
Does it do least-cost routing?
Yes, inside a pool. Put the suppliers for a destination into one pool in least-cost mode and each message goes to the member with the lowest buy price for that destination, with priority and weight as tie-breaks.
How are long messages accounted for?
Per segment. Each part is priced, and a message counts as delivered only when all its parts are. Retransmitted SMPP parts are neither sent nor billed twice. SMPP accepts up to 20 parts, the HTTP API up to 10.
Is there an HTTP API as well as SMPP?
Yes. POST /v1/sms sends up to 1,000 messages per request with optional idempotency, and delivery receipts and inbound messages are pushed to your HTTPS endpoint as signed webhooks.
What throughput can the platform handle?
Throughput depends on your infrastructure, connections and configuration, so we do not publish a guaranteed figure. During a technical evaluation we measure throughput and latency on your routes and hardware.
Talk to us

Let’s talk about your traffic.

Tell us your business type, the protocols towards customers and suppliers, cloud or on-premise, and the capabilities you care about. Our team comes back with a demo on the console or a technical evaluation on your scenario.