Every feature, in depth.
The landing page is the trailer. This is the spec sheet — what the engine actually does between accepting a message and proving it was delivered.
18 stages between "send" and "queued".
Every submission runs the full policy pipeline — first rejection wins, and only a durable enqueue returns success. Nothing skips the line.
Four strategies, per destination.
Routes match on account and destination, then apply the strategy you choose — informed by live vendor health, weights and rates.
Direct
Pin traffic to a single vendor for predictable delivery paths and simple reconciliation.
Failover
Ordered vendor lists — traffic shifts automatically the moment a vendor degrades or rejects.
Load Balance
Smooth weighted round-robin spreads volume across vendors exactly in the ratios you configure.
Least Cost
Rates from versioned rate cards drive per-destination least-cost decisions, automatically.
Two protocols, both directions, first-class.
Most gateways treat one edge as an afterthought. Yakugate implements HTTP and SMPP symmetrically — clients submit over either, vendors receive over either, and MO + DLR flow back through the same machinery.
HTTP API v4
One clean JSON contract — multi-recipient fan-out, scheduling (sendAt), validity periods, priorities, idempotency keys and per-recipient results.
SMPP 3.4 server
Real PDU codec, server-initiated enquire_link keepalives, per-account idle timeouts, scheduled delivery, TON/NPI validation and windowed throughput.
Per-account API dialects
Migrating customers keep their existing field names, response shapes (JSON, XML, plain text) and even their old submit URLs — zero client-side changes.
Client DLR push
Delivery receipts pushed over the client's SMPP bind or webhooked to their dlr_url — whichever way they connect.
Onboard a carrier over lunch.
Upstream connections are configuration, not code. A JSON adapter profile describes any REST, XML or SOAP vendor API — and SMPP vendors get sessions, windows and throttle handling out of the box.
Templated adapters
Request templates plus regex extraction map any vendor response format into canonical delivery states.
Session-auth chains
Multi-step login flows (session → token) with shared, instance-safe session storage, reactive re-auth on 401 and clean logout on deactivation.
Hot reload
Vendor config changes apply within seconds — no restarts, no dropped traffic.
Battle-tested SMPP
Never retransmit on timeout, hex-vs-decimal message IDs, backoff on throttle — a decade of pitfalls already encoded.
Accepted means durable. Delivered means proven.
A message is acknowledged only once it is durably enqueued. From there, every state transition is tracked until a delivery receipt closes the loop — or retry, expiry and failure handling settle it honestly.
Multipart integrity
Concatenated messages are assembled before policy so content rules see whole messages; part-level delivery truth over SMPP, single-call over HTTP.
Retry & expiry
Configurable backoff for transient vendor failures; validity periods enforced with clean expired states.
Retention & archive
Hot records partitioned per tenant-month, exported to cold storage on schedule — compliance without table bloat.
DLR correlation
Receipts parsed defensively (key/value, never positional) and matched through a global index — even across restarts.
Rate it, charge it, prove it.
Every accepted message — outbound and inbound — is rated from versioned buy/sell rate cards and settled against an append-only ledger. Historical charges always resolve to the exact rate row that priced them.
Versioned rate cards
Rate changes are inserts, never updates — audit pointers stay valid forever.
Idempotent charging
Charge-before-rate with message-ID references: crash retries can never double-bill.
Prepaid enforcement
Company-level balances checked in the hot path; suspend a company, suspend every account under it.
Abuse monitoring
Sliding-window scoring for AIT, spend spikes, spam patterns and template abuse — automatic warn, throttle, suspend, all audited.
13,435 segments a second. One deployment.
The measured peak — full 18-stage pipeline to durable enqueue — is 13,435 segments per second on a single deployment, with p95 accept latency as low as 3.7 ms. Need more? Scale vertically: bigger hardware, same simple topology.
One binary, 15 roles
Every process is the same Go binary run by role — deploy exactly the shape you need.
Vertical scaling
Throughput grows with cores and IO — no cluster choreography, no coordination tax.
Pluggable stores
Queue, config, hot and cold stores each choose MySQL, MSSQL, MongoDB or Redis independently.
Benchmark harness included
Reproduce the numbers on your own hardware before you commit.
Security gets its own page.
Authentication, brute-force defense, anti-enumeration and data protection are core engine features — read how they work.
Explore Security