• 228 destinations
  • No KYC, ever
  • Bitcoin, Monero, USDT and 4 more
Sign in Start sending

About

A messaging gateway
should not need your passport.

SMSMeteor exists because sending a text message to a customer had become an onboarding process. We removed the process and kept the messages: 228 destinations, one printed price each, paid in the money you already hold, delivered by routes we measure every morning.

01The problem we started from

Three forms, two calls and a quote to send a receipt.

In 2025 a small team of ours needed to send order confirmations to customers in eleven countries. The first gateway wanted a passport scan, a company registration and a call with sales. The second wanted the same plus a monthly commitment. The third published no prices at all. Every one of them was selling compliance theatre around a product that is, technically, a few bytes handed to a carrier.

We also noticed who was excluded by that theatre: sole traders, teams in countries where company paperwork takes months, projects that simply do not want a marketing database to hold their founders' identity documents. None of them were sending anything the carriers would object to. They were being filtered by the sales process, not by the network.

So we built the gateway we wanted to use. An email address opens the account. The rate card is a public page. The balance is funded in Bitcoin, Monero or USDT. The panel and the API are the same product. And the acceptable use policy does the job the passport scan pretended to do: it decides what may be sent, not who may send.

02How a message travels

Five hops. One of them is ours.

  1. 1Your panel or API callNumber normalised to E.164, destination and rule resolved, price computed from the public card.
  2. 2Our routingOne route per destination, chosen on yesterday's delivery rate and sender fidelity. Idempotency and balance checked here.
  3. 3The carrierThe operator that owns the number. This is where sender IDs are honoured, replaced or filtered.
  4. 4The handsetReceipt returned where the operator supports it; otherwise carrier acknowledgement is the final state.
  5. 5Back to youStatus in the report, event on your webhook, price in both. Nothing kept beyond 90 days.
228destinations, one rate each
$0.0042lowest rate per SMS today
53%average saving vs the two crypto gateways we track
99.85%90-day uptime of our weakest component
21incidents in six months, all public, 2 of them outages

03What we hold ourselves to

Six rules, written down so you can quote them back.

  1. One price, printed. The rate you see is the rate everyone pays. No tiers, no quotes, no enterprise grid. If we cannot print it, we do not sell it.
  2. No identity, ever. We do not ask for documents and we do not buy identity data about you. The acceptable use policy governs content, not people.
  3. One route, measured. A destination has one route, chosen for delivery rate, reviewed daily. We do not sell a cheaper route that loses your messages.
  4. Incidents in public. Every degradation is posted on the status page while it happens, with the timeline kept afterwards. The history is not curated.
  5. Rejected is free. Anything we refuse to send costs nothing. Invalid numbers, unsupported prefixes, blocked content.
  6. We refuse traffic. Phishing, impersonation of banks and public services, harvested lists. The route closes, the account follows. This is the price of the second rule.

04Timeline

Since the status page went live, 190 days ago.

Product changes from the blog and outages from the status page, in one list. The outages are here on purpose.

  1. Quiet hours can now be bypassed for transactional trafficA new value for window.quiet_hours lets codes, alerts and receipts leave at any hour while marketing keeps waiting for the local window.Read
  2. Reading a delivery report in two minutesFour numbers tell you whether a campaign went well, and one table tells you what to fix. A walkthrough of the report, top to bottom.Read
  3. Route notes, August 2026What moved on the network last month: two route swaps in West Africa, a sender rule change in South-East Asia, and new per-operator notes.Read
  4. Outage: Elevated error rate on the APIResolved in 94 minutes. Full timeline on the status page.Read
  5. Batch responses now list rejections individuallyOne bad number no longer fails a batch of a thousand. Rejected items are returned with their error while the rest is queued.Read
  6. Webhook replays, one by one or in bulkUndelivered events are now listed per endpoint for 30 days with the response we received, and can be replayed once your endpoint is fixed.Read
  7. How deposits are credited, coin by coinConfirmation counts, typical waits and what pending means for each of the seven coins, including why Monero takes a little longer than Tron.Read
  8. Why we publish the whole rate cardMost gateways quote on request. We print every rate, and a published alternative next to it. Here is the reasoning, and what it costs us.Read
  9. The curly apostrophe that doubled a campaign's costOne pasted character switched 40,000 messages from GSM-7 to Unicode. How the composer now warns you, and a checklist for single-segment copy.Read
  10. Sender ID registration: we now prepare the file with youFor the destinations that require registered alphanumeric senders, support now assembles the registration file and follows it through.Read
  11. Test keys: integrate without spending a centEvery account now has an sk_test_ key. Requests are validated, priced and answered like real ones, webhooks fire, nothing is sent.Read
  12. Now serving 228 destinations, one price eachCoverage reached every country and territory with a mobile network we can route to. What changed in the rate card, and what did not.Read
  13. What "no KYC" means here, and what it does notWe do not ask who you are. We are strict about what you send. The two are connected, and this is how.Read
  14. Outage: Deposit address generation slowResolved in 71 minutes. Full timeline on the status page.Read
  15. Status page goes liveNine components, public history from day one.

05Who and where

A small team, deliberately.

We are a small operations and engineering team spread across Europe, working in UTC. We do not publish names, for the same reason we do not ask for yours; we publish behaviour instead: the status page, the rate card, the changelog and this page.

Support is staffed seven days a week through the conversations in your panel. Legal terms, privacy and acceptable use are on the legal pages. If you are a carrier or a regulator with a question about traffic, the abuse topic of a support conversation reaches a person the same day.