SMS Forwarder
Your phone's messages, wherever you actually are.
SMS Forwarder relays the messages a phone receives to wherever you actually work: email, a webhook, Telegram, Slack, Discord, Teams or a push channel. You can reply from there and the reply leaves the phone as an ordinary SMS. It has no backend of its own — everything runs on the device, and nothing is reported anywhere.
Category
Mobile utility
Platform
Android
Stage
In development
Architecture
On-device, no backend
The problem
A number and the person who needs its messages are often not in the same place. A second SIM stays in a drawer but still receives login codes. A number registered in one country keeps getting bank messages while you are in another. A team shares a number, and one person's phone is the only place its alerts land.
The category is also, frankly, full of apps that solve this by sending your text messages through somebody else's server. For a class of message that consists largely of one-time codes, that is the wrong trade.
How it works
The app watches for incoming SMS and MMS and forwards what matches your rules to the destinations you have configured. Optionally — and only if you turn it on — it can do the same for notifications from specific apps you select.
Destinations are yours, not ours: another phone number, your own SMTP server, a webhook, a Telegram bot, Slack, Discord, a Teams workflow, or an ntfy push topic. The app has no server, so message content goes from the device to those destinations and nowhere else.
Replies work in the other direction. Answer a forwarded message in the channel where you received it, and the app sends that reply as an SMS from the phone, back to whoever sent the original.
Built to be trustworthy
There is no analytics SDK, no advertising SDK, no crash reporting and no telemetry. The app does not read your contacts. Nothing about your usage reaches LucidMaze, because there is no server for it to reach.
Credentials — SMTP passwords, bot tokens, webhook auth headers — are held in Android's encrypted storage, and a configuration export deliberately leaves them out so a backup file is not a secret. Plain-HTTP webhooks are refused unless you explicitly permit one. Delivery history stays on the device and is deleted after 30 days.
Two-way replies are off unless you enable them, and constrained when you do: only sender IDs you allow can trigger an SMS, replies are rate-limited, a reply must refer to a specific forwarded message, and you can require a confirmation word or PIN. When notification reading is active, the app shows a permanent notification saying so, with a button that switches it off immediately — and it will not read notifications at all if that indicator cannot be shown.
Capabilities
What it does
Many destinations
SMS, email over your own SMTP server, webhooks, Telegram, Slack, Discord, Microsoft Teams and ntfy push.
Two-way replies
Reply in the channel you received the message in; it goes back as an SMS from the phone, within limits you set.
Notification forwarding
Optionally forward notifications from apps you choose, with a visible always-on indicator and a one-tap pause.
History and retries
Every delivery, its status and its errors, kept on the device for 30 days and retryable when something failed.
Health checks
The app tells you when forwarding has quietly broken — a revoked permission, a destination that stopped accepting — instead of failing silently.
Heartbeat
An optional scheduled message with no personal content, so you know the relay is still alive.
Built with
- Android
- Foreground service
- Android Keystore
- No backend
Next venture
offcloud
Turn any server into a secure private cloud.