Skip to content
Jasmin migration

Outgrown Jasmin? Switch without rewriting a thing.

SMPP Forge speaks the same HTTP API and command-line operations as Jasmin and uses the same configuration model — then adds the billing, compliance, console and vendor support a growing business needs.

Jasmin todaySMPP Forge
  • HTTP send, balance and rate APIUnchanged
  • Command-line operationsUnchanged
  • Users, groups, routes and filtersImported
  • SMPP customer connectionsRe-point only
  • Billing, console and complianceAdded

What stays the same

Everything your customers and team rely on today

Compatibility is a product feature, not a migration script. Nothing your customers built needs to change.

Your customers’ integrations

The Jasmin HTTP endpoints for sending, balance and rate queries keep working, unchanged.

Your team’s runbooks

Familiar command-line operations for users, groups, connectors, routes, filters and interceptors.

Your configuration model

Users and groups, outbound and inbound routes, filters and interceptors map one to one.

Your connections

Standard SMPP everywhere: customers re-point their connections and carriers see an ordinary client.

What you gain

Everything Jasmin leaves you to build yourself

Jasmin is a capable open-source engine. Running a messaging business on it means building the console, billing, compliance and support around it. SMPP Forge ships them ready to use.

  • A web console with 30+ screens, for your team and your customers
  • Customer billing: rate cards, prepaid and postpaid accounts, invoices
  • Refund rules for rejected, undelivered and expired messages
  • A sender-ID registry and regional compliance engine
  • Number-portability routing with a local ported-number database
  • Store-and-forward delivery that never sends a message twice
  • Two-factor sign-in and a complete audit trail
  • SMPP 3.3 and 5.0 alongside 3.4, and a modern REST API
  • Durable bulk campaigns of up to 100,000 messages
  • Vendor support with response-time commitments

The plan

A typical cut-over takes about five weeks

Run both gateways side by side and move traffic route by route. There is nothing to roll back, because nothing is switched off until you are ready.

  1. 1Week 1

    Evaluate

    Install, import users and routes, and test everything against the built-in carrier simulator.

  2. 2Weeks 2–4

    Run in parallel

    Shift a share of live traffic and compare delivery, speed and billing side by side.

  3. 3Week 5

    Cut over

    Move the remaining connections and routes, with monitoring in place.

  4. 4Ongoing

    Optimize

    Tune least-cost and failover routing against real delivery data.

Other gateways

Coming from Kannel or something else?

Customers connect over standard SMPP or HTTP, and carriers see an ordinary SMPP client — so most migrations come down to moving accounts, routes and prices. Our engineers map your current setup and plan the move with you.

Talk to a migration engineer

FAQ

Migration questions

Something else on your mind? Email sales@smppforge.com — a person, not a bot, will answer.

Do our customers need to change their integrations?

No. The Jasmin HTTP endpoints for sending, balance and rate queries keep working, and SMPP customers simply point their connection at the new gateway.

Can we run Jasmin and SMPP Forge side by side?

Yes — that is the recommended path. Move a share of traffic, compare delivery, latency and billing, then cut over route by route with nothing to roll back.

What about our operations scripts?

Your team keeps the familiar command-line operations for users, groups, connectors, routes, filters and interceptors, so runbooks carry over.

How long does a migration take?

A typical cut-over takes about five weeks: one week of evaluation, two to four weeks of parallel running, and a monitored final cut-over.

Plan your move from Jasmin

Tell us about your Jasmin setup — users, connectors and traffic — and we will come back within one business day with a migration plan.