TextPipe

OTP routing / Android

Codes shouldn't live on one phone.

Every one-time code you depend on arrives by SMS, on one SIM, in one drawer. TextPipe is the layer that moves them: capture on the device, authenticate at the edge, deliver to a destination you control.

Download the APK How it routes

Capture. Authenticate. Deliver.

Three stages, one path. Your phone does the catching; everything that decides where a code goes lives on our side, so a lost or replaced phone changes nothing.

01 · Capture

On the SIM.

The Android app reads incoming text SMS and tags each one with its sender and the SIM that received it. Dual-SIM phones stay distinguishable end to end.

  • ReadsIncoming text SMS
  • TagsSender, receiving SIM
  • IgnoresMMS, attachments
02 · Authenticate

Nothing secret on the phone.

Your phone never stores a bot token or a destination address — only a credential that identifies it. Everything sensitive stays server-side, encrypted in transit and at rest. A request without a valid credential gets nothing back.

  • On the phoneA credential, nothing else
  • EncryptedIn transit and at rest
  • Lose the phoneRevoke it, keep your routes
03 · Deliver

Your routes follow you.

Where your codes go belongs to your account, not to a handset. Get a new phone, sign in, and everything still points where you left it. Nothing to set up twice.

  • New phoneSign in, routes are there
  • Two SIMsSend each one somewhere different
  • Sent twiceStill arrives once

Route each SIM anywhere.

Work SIM to a work chat, personal SIM to your inbox. Rules live in your account, so you change where codes land without touching the phone.

SIM 1 and SIM 2 feed the TextPipe router, which forwards each to its own destination. SIM 1 SIM 2 ROUTER Telegram Email
In development

Telegram

Delivery to a Telegram chat you link from the app. The delivery path is built; binding it to account-owned routing is the work in progress, so it is not usable yet.

In development

Email

Forwarding to a verified address, with per-account quota. Implemented behind the account model; provider activation is not complete.

Nothing here is live for end-to-end SMS delivery yet. The app installs, signs in, and links destinations today; message delivery through a paid account is still being wired. This page will say otherwise the moment it is true.

Pricing

One dollar. Two phones.

Billing runs through Stripe. Subscribe in the app, manage or cancel in the Stripe customer portal. TextPipe never sees card details.

Hosted

$1 per month

  • Account-owned destinations that survive a handset swap
  • Two active phones per account; the same phone reuses its slot
  • Per-SIM routing on dual-SIM hardware, counted as one phone
  • Subscribe, manage, and cancel through Stripe

Need more than two phones? Ask for extra slots

Billing is functional. Delivery to a destination on a paid account is not finished, so subscribing today buys an account, not a working pipe.

Downloads

You can check what you're installing.

Sideloading means trusting a file. So every build publishes its fingerprint, and the button below only turns on when the file we're offering matches ours. If anything looks off, you get no download instead of a questionable one.

Builds are never replaced after release, so the version you checked stays the version you get. The numbers are there if you want to verify them yourself.

Latest release manifest NOT PUBLISHED

No public APK yet

Version
Not published
Source revision
Not published
APK size
Not published
APK SHA-256
Not published
Signing certificate SHA-256
Not published

Support: founder-operated at textpipe@liongkj.com. No published response-time commitment.

Scope: incoming text SMS on Android. Delivery depends on your carrier, your network, and the destination provider — no routing layer can guarantee every message arrives.