Opportunities › SMS API gateway for developers › Proposed app
Pocketline
Turn spare Android phones into a managed SMS API with webhooks and a delivery log
- Score
- 50
- confidence 57
- Evidence
- 5
- items on the page
- Rivals
- 1
- named in sources
- First version
- 30 d
- estimate
- Type
- Desktop app
- PWA: runs in the browser, installs on Mac and Windows
- Market since
- 2008
- Mature market · AI estimate
ScreensConcept
Desktop app: Engineers manage device pools, configure send limits, trace message flows, and view usage dashboards—technical setup and monitoring work. Sample screens on a computer, in the proposed brand. Their numbers are sample data.
Devices
1 needs attention3 online
About this appAI proposal
Pocketline lets developers send and receive SMS through a plain REST API, using Android phones they already own as the gateway. Your app calls one endpoint; a phone with a SIM sends the message. Replies come back to your server as webhooks.
It is built for engineering teams who want to avoid per-message fees and vendor lock-in. Run the open gateway yourself for free, or use the hosted control plane that handles queues, retries, device health and logs so you do not have to.
What sets it apart: several phones act as one pool, with routing, failover and a clear log of every message. You see which device sent what, and why a message failed, in a PWA you can open on any screen.
- Tagline
- Your phones, your SMS API. No per-message fees.
- Voice
- PlainPracticalDirect
- Why this name
- A pocket is where the phone lives, and a line is a SIM line and a line of code. Two plain words that say what it does.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
Simple send and receive API
One REST call to send. Incoming messages arrive as signed JSON webhooks with sender, body and device ID.
No member yet
Device pool with failover
Link several Android phones. If one goes offline or hits its SIM limit, the next one takes the message.
No member yet
Delivery log and retries
Every message shows its status, device and error. Failed sends retry on a schedule you set.
No member yet
Self-host or hosted
Run the gateway on your own server for free, or let the hosted plan handle uptime and updates.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#0F4C4ADeep Teal · primary#F6F3ECPaper · surface#1B2220Ink · text#E8742ASignal Orange · accent#7FA99BSage · data#D9D3C4Stone · border
Typography
Aa
Pocketline
PricingAI proposal
Twilio's pricing page, per the material, lists 4 paid plans from $0.01 to $0.07 by usage. Pocketline tiers are flat starting points to test against that, not based on any competitor flat fee.
Self-hosted
Free
- Run the gateway on your own server
- Unlimited messages on your own SIMs
- REST API and webhooks
- Community support
Hosted
$15 a month
- Managed server, queue and retries
- Up to 5 devices
- Message log for 30 days
- Device health email alerts
Team
$49 a month
- Up to 25 devices
- Routing rules and failover
- Multiple API keys and scopes
What it could be worthEstimate
What a software business making this much sells for today, from real deals. Pick a monthly revenue.
If it makes
Worth about
$194,000
Sale range $132,000 to $263,000
$120,000 a year in revenue
From 87 software businesses listed and sold on Empire Flippers in the last year, revenue vetted by the broker: they sell for about 19× their monthly revenue, most between 13× and 26×.
Measured on profit, the middle deal is 32× monthly net profit: about 2.7 years of profit.
An estimate, not an offer or financial advice. A real price depends on profit, growth, churn, how much of the work is the owner's, and the buyer.
How it would growAI proposal
How the product would reach new customers through its own use, and how the first ones would be found. A plan to test, not a result.
- Built-in loop
- No loop in the product. Users run it behind their own apps, so end recipients see only text messages with no Pocketline name. It spreads through developer content, open-source communities and word of mouth.
- Do they become customers?
- Recipients of texts cannot become customers. Test whether developers who find the free self-hosted version convert to the hosted plan, and what share would pay to skip running servers.
- First customers
- Small engineering teams of 2 to 10 developers at startups, sending one-time codes or alerts at low volume, who want to avoid per-message fees.
- Where to reach them
- GitHub and open-source communities: Publish the self-hosted gateway with clear docs and a Twilio migration guide.
- Developer forums: Answer questions on Hacker News, Reddit and Stack Overflow about cheap SMS for side projects and internal alerts.
- Technical blog posts: Write guides on sending SMS from a spare phone, with cost comparisons using the reader's own numbers.
- First milestone
- Ten teams run the self-hosted version and five of them pay for the hosted plan within 60 days of launch.
Why people already pay for this
- VerifiedGitHub repository gained 3179 stars in 1674 days
- Public claimDevelopers need an SMS API alternative that can be self-hosted and uses Android devices as gateways
- Public claimTwilio and similar services are the existing solution, establishing a commercial market for SMS APIs
- Public claimSelf-hosting and cost avoidance are key differentiation points
- Verified
Tech stack
Every proposal builds on the same PWA base, installable from the browser on any phone or computer. Dashed boxes are what this app adds.
- AppNext.js and TypeScript
- PWAManifest and service worker
- UITailwind CSS
- Data and authSupabase Postgres
- PaymentsStripe
- EmailResend
- HostingVercel
- This app · Android gateway appSmall native Android app that relays SMSA PWA cannot read or send SMS on a phone, so a companion app on each device is required.
- This app · Push to devicesFirebase Cloud Messaging or similar pushWakes the phone to send a queued message without keeping a connection open.
RisksAI inference
- RegulatorySending application traffic from consumer SIMs may breach carrier terms or local messaging rules on consent and registration, and numbers may get blocked.
- PlatformAndroid and Google Play limit apps that read or send SMS; the gateway app may need sideloading, or may be rejected from the store.
- TechnicalPhones go offline, sleep or throttle background work, so delivery is less reliable than a carrier-grade provider.
- CommercialAn open-source self-hosted option is free, so some users may never pay for the hosted plan. The material shows interest, not payment for it.
- Intellectual propertyAn existing open-source project covers a similar idea. Code reuse must follow its license, and the product needs its own design and name.
Everything marked AI proposal or AI inference was written by a model from the evidence on the opportunity page. The proposed name must be checked against trademark registers before it is used.