The problem
Six reasons SMS fails your business
Every team using a single-provider gateway hits the same wall. Here is what breaks — and how we fix it.
№ 01
One provider goes down — business stops
OTPs don't arrive, customers can't log in, the campaign dies.
Automatic failover
Multiple providers run in parallel. If one drops, the system switches in 5 seconds — the customer doesn't notice.
№ 02
Every provider has its own tariff
Each content provider prices differently. Reconciling which is cheapest per carrier is impossible by hand.
Cost-optimal routing
SmartRouter picks the cheapest provider per number automatically. 5 strategies: cheapest, priority, round-robin, carrier-based, failover.
№ 03
OTP brute-force and bot spam
Fraudsters spam OTP requests, bots send mass spam.
Fraud Detection Engine
6 rules: rate limit, duplicate detection, pattern match, blacklist, geo-anomaly, Redis-backed brute-force shield.
№ 04
Did the SMS arrive? Nobody knows
Traditional gateways are "fire and forget". No status.
Real-time SSE tracking
QUEUED → SENT → DELIVERED live in your dashboard. Failures auto-retry 3 times, then DLQ.
№ 05
Teams blow their budgets
Who sent what, when, how much? Auditing is a nightmare.
Per-team budgets + audit log
Each department has its own budget. Pessimistic locking. Full audit trail.
№ 06
Consent and compliance
Promo SMS requires consent. Opt-out is mandatory. Auditors will ask.
Consent Management
Every promo SMS checks DND and opt-out lists first. Data retention runs automatically.
SmartRouter
One API — every provider
SmartRouter picks the best path for each SMS in real time. Five strategies, one line of code.
Carriers
UCell
Beeline
Mobiuz
UMS
Humans
Providers
PlayMobile
Eskiz
BroadNet
Strategy
PlayMobile
✓
17-step journey
Every SMS goes through 17 quality gates
From API call to "Delivered" — a complete audit trail, automatic retries, and delivery receipts.
01
API Key validation (SHA-256 + IP whitelist)
02
Rate-limit check
03
Input validation (phone, text)
04
Fraud Detection (6 rules)
05
Consent check (DND + opt-out)
06
Budget check (pessimistic lock)
07
Carrier detection (phone prefix)
08
SmartRouter decision
09
Provider selection
10
Idempotency key generation
11
Queue (RabbitMQ)
12
Provider API call
13
Delivery receipt (DLR)
14
Status update — SENT/FAILED/DELIVERED
15
Real-time SSE → client
16
Retry on failure (max 3, DLQ)
17
Audit log write
0ms0ms
Solid foundation
Built to bank-grade standards
We picked the same technologies trusted by the world's largest banks and tech companies. Your SMS rides on that foundation.
Language
Kotlin 2.1
Java-compatible, safer
Framework
Spring Boot 3.4
Industry standard
JVM
JDK 21 + Virtual Threads
100K+ concurrent SMS
Database
PostgreSQL 16
ACID, reliable
Cache
Redis 7
OTP, idempotency, rate
Queue
RabbitMQ 3
Async, retry, DLQ
Frontend
React 19 + TS
Modern dashboard
Monitoring
Prometheus + Grafana
Real-time metrics
Use cases
What our clients send
From OTP to marketing campaigns — one platform handles every SMS scenario.
Finance
Banks & payments
OTP, transaction confirmation, fraud alerts. 99.99% uptime SLA.
E-commerce
Online retail
Order status, delivery updates, abandoned-cart campaigns.
Government
Public services
Citizen notifications, queue systems, document-ready alerts.
Logistics
Last-mile
Driver coordination, customer contact, ETA notifications.
Education
Schools & universities
Attendance, grades, events, parent communication.
Healthcare
Clinics
Appointment reminders, prescription-ready alerts.
Onsite installation
Your servers. Your data.
For banks and government bodies. Nothing leaves your perimeter. Full control stays with you.
1
Audit & architecture
Our engineering team studies your infrastructure. 3–5 working days.
2
Deploy to your servers
On-premise or private cloud. Docker, Kubernetes, bare-metal.
3
Provider integration
Your existing content-provider contracts connect. We add new ones too.
4
Migration & testing
Data migration from legacy. Parallel test mode.
5
Training & docs
Two-day training for your team. Complete technical documentation.
6
Ongoing support
24/7 monitoring and engineering support. SLA contract.
Average install time
2–4 weeks
Depending on complexity
Security
ISO 27001
Best practices
Why us
One system — every provider
✓
All content providers
All major content providers in Uzbekistan — unified behind one API.
✓
Bank-grade security
Runs on your servers. Data never leaves your perimeter.
✓
Fast integration
Live in 1-2 weeks. Full documentation and team training included.
✓
We don't sell SMS
Your direct contracts with the providers stay yours. We just build the pipe.
✓
No vendor lock-in
Add or drop any provider at any time.
✓
24/7 local support
Team in Tashkent. Uzbek, Russian, English.