• 228 destinations
  • No KYC, ever
  • Bitcoin, Monero, USDT and 4 more

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.89%uptime of our weakest component since launch
5incidents since launch, all public, 1 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 we launched, 62 days ago.

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

  1. Two free tools: an SMS character counter and an E.164 converterCount characters, encoding and segments before a campaign leaves, and turn a column of local phone numbers into E.164 in one paste. Both run in the browser, free, without an account.Read
  2. How SMS routes are chosen, monitored and swappedOne route per destination, measured every day: what a route is, the signals that trigger a swap, how sender rules change and what you see when it happens.Read
  3. Outage: Delivery failures on Latin America routesResolved in 103 minutes. Full timeline on the status page.Read
  4. SMSMeteor goes liveRate card, documentation and status page public from the first day.
  5. Quiet hours and transactional SMS: when the bypass appliesQuiet hours keep marketing out of the night. Codes and alerts are different: how the transactional bypass works, who may use it and what still applies.Read
  6. How to read an SMS delivery report, status by statusRejected, failed, expired, delivered: the order to read an SMS delivery report in, what each status and failure reason means, and what to fix first.Read
  7. Batch sending: how partial rejections workOne bad number should not sink a batch of a thousand. How the batch endpoint validates each message, what the response contains and how to handle rejections.Read
  8. Webhook failures and replays: a practical guideWhy webhook deliveries fail, how retries work over 24 hours, and how to replay undelivered events one by one or in bulk without processing them twice.Read
  9. 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
  10. Why we publish the whole rate cardMost gateways quote on request. We print every rate, and a published alternative next to it. The reasoning, what it costs us and how to compare SMS prices.Read
  11. The curly apostrophe that doubles your SMS costOne character outside the GSM-7 alphabet switches a whole message to Unicode and can triple its segment count. Which characters do it, and how to avoid them.Read
  12. Sender ID registration: how we prepare the file with youWhere brand names must be registered before they show, what the file contains, how long approval takes and how your messages keep flowing meanwhile.Read
  13. Test keys: integrate an SMS API without spending a centAn sk_test_ key validates, prices and answers like the live API, fires signed webhooks and sends nothing. What it covers, what it cannot tell you and how to go live.Read
  14. 228 destinations, one price each: how the rate card worksEvery destination has one published per-segment rate, the same for one message or ten million. How rates are set, what is included and how to estimate a campaign.Read
  15. What "no KYC" means here, and what it does notWe do not ask who you are. We are strict about what you send. What no-KYC means for your account and your data, what is enforced instead, and why.Read

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.