Skip to main content
FireFlo sits between applications that want to send SMS and the carriers that actually deliver it. It speaks HTTP to your applications and SMPP to your vendors, in both directions, and it keeps the routing, the pricing and the record of every message on your own infrastructure. It is three things that ship together:

The gateway

A Java/Quarkus service. Accepts SMPP binds and HTTP submissions, routes, rates and records every message, and dials out to your vendors.

The control panel

Your operators’ screens. Vendors, listeners, routing, customers, tariffs, statements and live health — configuration and diagnosis in one place.

The customer portal

Your customers’ own half of that application: their messages, their statement, their sender-ID registrations, credential rotation and an API playground.
Current release: .

​
Which part of this site do you want

Platform

You run FireFlo. Installing it, connecting vendors, writing routing rules, onboarding customers, pricing their traffic, and knowing when something is wrong.

Developers

You send messages through someone’s FireFlo. Getting a message out over HTTP or SMPP, handling delivery receipts, and reading what you have been charged.

Reference

You are looking something up. Every request field, configuration key, worker setting, CLI verb and status code, with its default and what happens when it is wrong.

​
If you have ten minutes

1

Read the vocabulary

Concepts fixes the handful of words the rest of the site leans on — vendor, server, product, account, scope. Two of them mean the opposite of what a Kannel or Jasmin background suggests.
2

Start it

Quickstart runs a gateway in Docker with one command, and Install puts it on a server properly.
3

Send something

Send one message is a single curl. Everything after that is routing it somewhere real.
FireFlo is commercial software, licensed per deployment. It is created and maintained by Remotiq — talk to us about licensing, or write to support@fireflo.au if you already run it.