Self-hosted phone lines that just work.

You should be comfortable renting a small Linux server and pasting a few commands — if you've ever set up a Minecraft server, Home Assistant, or a WordPress box, you're overqualified. The backend installs with Docker, the admin console does the carrier configuration, and the docs assume nothing. If that paragraph sounded like work you don't want, an app like OpenPhone is genuinely a better fit — this product is for people who want to own the stack.

US carriers require every business-ish sender of text messages to register who they are (it's an industry anti-spam regime called 10DLC). With a business EIN you register once and all your numbers ride under it with full throughput. No EIN? There's a sole-proprietor lane (capped at one texting number), an EIN is free from the IRS in ~10 minutes if you want more, or skip registration entirely with a voice-only line. The setup wizard walks whichever path you pick. Approval is carrier-side and typically takes a few days — start it early.

Yes — including a mobile number you've had for years. The golden rule: never cancel the old line first; the port itself moves the number and closes the line behind it. Our porting guide covers the whole sequence, including keeping a fallback line live during the cutover and moving any text-message 2FA off the number first.

Your numbers stay in your carrier account, your data stays on your server — both were never ours to take. What stops is what the subscription pays for: the mobile app's push delivery (so it stops ringing for new calls), app updates, and support. There's a grace period before anything turns off, and you can export everything at any time.

Not for you. We can't promise that our prices won't go up… but we guarantee our prices will never go up for you. The rate card in effect the day you subscribe is locked to your account for as long as you stay subscribed — your monthly base and the same per-user rate for any teammates you add down the road. If we raise prices later, that's a problem for new customers, never for you.

It covers the essentials a small business actually uses: an auto-attendant ("press 1 for sales"), business-hours routing, ring groups (the main number rings several people; first answer wins), a shared texting inbox for the company number — plus every person's own private line(s) with calling, texting, voicemail, and recording. What it deliberately is not is call-center software: no agent queues, wrap-up timers, wallboards, deskphone fleet management, or built-in video — by design, not by roadmap. If you're running a support floor, buy that. If you're running a business that needs to answer the phone, you're covered.

Those are the other ways to self-host your phones, and they're good at what they are: office switchboards. You administer trunks, extensions, and inbound rules, and in exchange you get deep call-center features and deskphone support. RingReplacer deliberately isn't that — each person gets their own number(s) with native calling and first-class texting, and the front-desk basics (auto-attendant, business hours, ring groups) are built in without any PBX administration — set up by a wizard in an afternoon. If you need deskphone fleets or call-center queues with agent reporting, use a PBX — 3CX does that well, and even has a free entry tier for very small setups. If you need people reachable on numbers you own, with SMS/MMS that isn't a trunk afterthought and an iPhone experience that feels like the built-in dialer, that's us. (FreePBX/Asterisk: free and powerful, but you're building the mobile, push, and texting experience yourself.)

Emergency calling on any VoIP line requires registering your street address with the carrier (E911, ~$1/mo per number — the wizard reminds you). The app routes 911 dials to your phone's native dialer whenever a cellular line is present, because that's safer than any VoIP path. Don't rely on a VoIP line as your only way to reach 911.

Planned, and gated purely by demand — the backend already doesn't care what the phone runs. Join the waitlist and you're literally voting for it; enough votes and it gets built.

They're stored only in your database, on your server. We operate one small piece of infrastructure — the push relay that wakes your phone — and it's built to know as little as possible: enough to deliver a notification, never a message archive. Calls and texts themselves flow between your server, your carrier, and your phone.