Text messaging for developer tools apps.
Deploy alerts, quota warnings, payment failures — the messages that keep a production platform running.
Free to author & testNo credit cardUS & Canada
Acme: prod deploy #4821 failed. Roll back or fix: yourapp.com/deploys/4821
Our free message templates are live.
Sending arrives Summer 2026.
A text can change the outcome.
A production deploy fails at 2am. The on-call engineer gets a text before the first customer opens a support ticket.
Developer tools & API platform messages. And all of the others.
All nine message categories are included — one registration.
Runs the gated-access funnel from joined, to access granted, to lapsed.
Messages your on-call engineer the moment a production deploy or build fails.
Keeps a developer-customer informed on an open ticket without making them poll a portal.
Warns before the cap is hit, then alerts when requests start failing.
Notifies affected accounts when the platform is down, and again when it clears.
Catches a declined card before it suspends the account and takes down production workloads.
Nudges a trial toward conversion, then confirms when a plan is chosen.
Alerts on new device access and gates destructive actions behind a confirmation code.
Proves phone ownership at account creation.
Q&A: Account event messages
Can I send deploy alerts from a CI/CD pipeline directly, or does it need to go through my app's backend?
Either works — RelayKit is an API call, not a platform integration. You can call the RelayKit API from a GitHub Actions step, a build hook, or any webhook your pipeline fires. The message goes out the same way regardless of where the call originates. Most teams start with a direct pipeline call and move it behind their backend when they want delivery tracking or per-user routing.
What's the difference between a system alert and an on-call page for deploy failures?
Urgency and what you expect the recipient to do. An on-call page fires when something is down and needs human attention now — it's the shortest message in the library and links straight to the incident. A system alert is for informational threshold events: quota at 80%, latency above baseline, a job that finished. Both use the same channel; the difference is the action you're asking for.
Do verification texts for API key rotation need a STOP line?
No — step-up confirmation codes are 2FA traffic and carry the same carve-out as signup codes. The 2FA TCR exemption covers any code sent to verify a specific action, not just signup. Key rotation, ownership transfer, payment method changes — all qualify. No STOP language in the body.
What's the right message for an API key rotation or ownership transfer?
A confirmation code sent to the account owner before the action completes. High-stakes actions — key rotation, billing-owner transfer, team permission changes — should require a step-up code. It's a one-time code sent to the verified number on the account, confirming the action before it goes through. Never put the key itself in the message body; link to the dashboard instead.
You build the feature. We handle the bureaucracy.
Every text message carries a stack of carrier rules. We've read all of it, so you don't have to.
Registration handled
Getting approved on your own can take weeks.
Most registrations clear in about three days. We handle the filing, so you can keep building your app.
Messages compliant
Send the wrong kind of message and carriers block it — silently.
Every message is checked against carrier rules before it sends, not just passed through.
Opt-ins & opt-outs covered
Miss a single STOP and the fines add up fast.
We stop instantly. Consent is tracked and enforced at delivery, not wired up by you.
Give your AI tool a build spec, not a pile of docs.
RelayKit generates implementation instructions for your AI tool. Messages, variables, event triggers, testing steps, and integration guidance arrive for smooth integration.
Slots into ShipFast, Supastarter, MakerKit, and Vercel + Supabase.
import { RelayKit } from 'relaykit'; const relaykit = new RelayKit(); await relaykit.appointments.sendConfirmation(customer.phone, { date: 'Fri, Jun 6', time: '2:00 PM', });
That's the send.
Preview list
Your safe audience for sending test messages, before and after launch.
- JoelVerified(555) 867-8842
- SarahVerified(555) 412-5519
- MikeInvited(555) 290-3301
Run test messages through real phones.
Add yourself, your team, your beta testers. Each person verifies once. After that, your app's messages work for them exactly the way they'll work for customers.
Trigger your real flows — a booking, a code, a reminder — and see the whole loop land: sent, delivered, your database updated.
What it takes to go live.
No telecom expertise required. We handle the carrier side.
Choose your messages
Pick the messages your app needs from templates that already know the rules.
Browse the messages →Build and test
Hand the spec to your AI tool, then test the full flow on real phones before launch.
Go live
RelayKit handles registration and delivery. A few days to approval.
Simple pricing.
Build for free
Set up your messages. Add the code to your app. Test with real phones. No credit card.
Go live for $49 + $19/mo
We file your registration with carriers. Approval takes a few days. 500 messages included per month, then $8 per additional 500. Full refund if you're not approved.
What $19/mo includes.
Marketing messages add $10/mo. Volume pricing above 5,000 messages. US and Canada at launch. We don't handle HIPAA, healthcare-regulated workflows, or enterprise procurement.
When a message can't wait, send a text.
Messages from an app only work when someone sees them. Here's how text and email compare.
Industry SMS-vs-email benchmarks, 2025–26 — open and response from SMS-marketing aggregates; email inbox placement from Validity's 2025 deliverability report. SMS open is inferred from delivery, not pixel-tracked; reported email open rates are distorted by tracking-pixel prefetch and blocking.
The rules show up after you start building.
US carriers require these from every business that sends texts. Getting approved can take weeks if not done right.
Registration
Before anything sends, your business gets registered in a central registry that every US carrier checks — legal name, tax ID, website, and what you plan to send. Details have to match your IRS records exactly, or the application bounces.
RelayKit collects this during setup and files the registration for you.
Carrier review
Reviewers check your registration and your messages against carrier rules before you're allowed to send. Other providers typically take two to three weeks — and every rejection restarts the clock, with no guarantee the next round clears.
RelayKit submissions are prepared to pass the first time; approval typically takes a few days.
Consent requirements
You have to collect and keep proof that every recipient agreed to get texts from you — how they opted in, when, and which kinds of messages they agreed to. Someone who signed up for appointment reminders hasn't agreed to marketing.
RelayKit provides the opt-in language and keeps the consent records automatically.
Build a compliance website
Reviewers visit your website looking for a privacy policy with specific mobile-data language, posted terms, and a visible description of your texting program. A missing or half-finished site is the single most common reason registrations get rejected.
RelayKit generates and hosts a compliance site for you — privacy policy, terms, and opt-in page included.
STOP and HELP handling
A reply of STOP has to halt messages to that person immediately, and HELP has to get a real answer — automatically, every time. Getting it wrong is a fast way to get a number shut down.
RelayKit handles both at the delivery layer; when someone replies STOP, we stop.
Message restrictions
Carriers limit what businesses can say over text: entire content categories are banned, links get scrutinized, and messages outside your registered use case can get your number flagged. The rules live across multiple carrier policies, and they change.
RelayKit's templates already follow them, and custom messages are checked before they send — not just passed through.
The messages are ready now.
Sending arrives Summer 2026.
You can start with the messages today. When sending launches, your AI tool wires up the integration, you test on real phones, and registration and opt-outs stay handled behind the scenes.