NdoleStudio

NdoleStudio/httpsms

Go AGPL-3.0 Mobile

Send and receive SMS messages using your Android phone programmatically via a simple HTTP API

3.3k stars
541 forks
active
GitHub +552 / week

3.3k

Stars

541

Forks

3

Open issues

10

Contributors

v0.0.17 18 Apr 2026

AI Analysis

httpSMS enables users to programmatically send and receive SMS messages through their Android phone via a simple HTTP API, eliminating the need for commercial SMS gateway services in countries with limited virtual phone number availability. It serves developers and businesses in regions (particularly Africa) where traditional SMS APIs are unavailable or prohibitively expensive, and is not designed for general-purpose web development or mainstream messaging applications.

Mobile Application Discovery value: 6/10
Documentation 8/10
Activity 10/10
Community 8/10
Code quality 7/10

Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.

Overall score 8/10

AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.

sms-gateway http-api android-integration self-hosted webhook
Actively maintained Well documented Niche/specialized use case Production ready
Deep Analysis · Based on README and public signals
2w ago

Android phone as SMS gateway via HTTP API, targeting regions without virtual phone number support

httpSMS converts an Android phone into an SMS gateway accessible through a simple HTTP API and web dashboard. Designed for users in countries where virtual SMS numbers are unavailable, it combines a Go backend (Fiber + CockroachDB), Kotlin Android app, and Nuxt web UI. The service manages both outbound SMS sending and inbound message webhooks. Adoption appears concentrated in emerging markets and developer communities needing local phone-based SMS access rather than traditional SMS provider APIs.

Origin

Created May 2022 by a developer from Cameroon frustrated by lack of viable SMS solutions in regions without virtual number support. Has accumulated 2,533 GitHub stars and grown to a multi-component system (backend, Android app, web UI) with active maintenance across all layers.

Growth

Strong recent acceleration: 526 stars gained in 7 days (as of June 2026) suggests a recent spike in visibility or community interest. Steady maintenance with last push 3 days before analysis date indicates active development. Growth pattern suggests word-of-mouth adoption in niche communities plus periodic discovery bursts rather than explosive mainstream adoption.

In production

Adoption not verified at scale. README shows self-hosted deployment documentation (Docker setup with Firebase, SMTP, Cloudflare Turnstile), implying users can run private instances. Public service at httpsms.com exists with web dashboard and API endpoints. Community Discord server active. However, no published case studies, user counts, transaction volumes, or enterprise deployments mentioned. Adoption likely confined to individual developers and small teams rather than verified enterprise or massive consumer base.

Code analysis
Architecture

Appears to use microservice-like separation: Go API (Fiber framework) on Google Cloud Run with CockroachDB backend, Firebase for web hosting and mobile push notifications, Nuxt/Vuetify for frontend, Kotlin for Android app. README indicates end-to-end encryption (AES-256) and webhook support for inbound messages. Likely built for distributed deployment rather than single-server architecture.

Tests

README mentions CI/CD pipelines (GitHub Actions for Web and API), integration testing documentation, and Scrutinizer Code Quality badges, but specific coverage percentages not documented. Presence of automated testing workflows suggests reasonable test discipline, but depth not verifiable from README alone.

Maintenance

Last push June 25, 2026 (3 days before analysis), last repository created May 2022 (4 years active). Active Discord community and GitHub issues tracked. Multiple CI/CD pipelines passing. Maintenance pattern appears steady and recent, not dormant. No evidence of major version abandonment or stale branches.

Honest verdict

ADOPT IF: you operate in a region where virtual SMS numbers are unavailable or restricted, need to programmatically control a real Android phone for SMS, are comfortable self-hosting complex infrastructure (Firebase, CockroachDB, Cloudflare), and value end-to-end encryption over convenience. AVOID IF: you need a simple, zero-infrastructure solution, require guaranteed high uptime SLAs, want established enterprise support, or can use traditional SMS provider APIs (Twilio, AWS SNS, etc.). MONITOR IF: you are evaluating Android-phone-based SMS gateways and want to track whether httpSMS's recent growth surge sustains, whether managed hosting reliability improves, or whether adoption outside developer communities expands.

Independent dimensions

Mainstream potential

3/10

Technical importance

5/10

Adoption evidence

3/10

Risks
  • Dependency on third-party services (Firebase, CockroachDB, Google Cloud Run, Cloudflare) creates operational complexity and potential single points of failure; no clear self-hosted alternative documented for all components.
  • Adoption appears limited to developer/technical communities; evidence of production use at meaningful scale (transactions, users, uptime requirements) not publicly documented.
  • Android app stability and push notification delivery reliability not discussed in README; these are critical for production SMS workflows but implementation details opaque.
  • AGPL-3.0 license may deter commercial deployments or integrations with proprietary software; copyleft restrictions limit enterprise adoption.
  • Project relies on single maintainer (implied by 'I wanted' language in README); no visible team structure or sustainability plan documented, raising long-term maintenance risk.
Prediction

httpSMS likely remains a specialized tool for regional SMS access rather than mainstream SMS gateway. Recent star velocity may reflect awareness growth in emerging markets or developer communities, but sustained adoption depends on reliability of managed service, competitive positioning versus improving regional SMS provider availability, and whether maintainer can scale operational load. Most probable outcome: niche but stable tool with slow, steady adoption among developers in SMS-restricted regions, occasional dormancy risk if maintainer priorities shift.

0 found this helpful

Newsletter

Get analyses like this every Monday

Free weekly digest of the most interesting open-source discoveries.

Languages

Go
67.9%
Vue
19.6%
Kotlin
7.7%
TypeScript
4.6%
JavaScript
0.1%
Dockerfile
0.1%
Shell
0.1%

Information

Language
Go
License
AGPL-3.0
Last updated
17h ago
Created
50mo ago
Analyzed with
anthropic/claude-haiku-4-5

Stars over time

Loading…

Contributors over time

Top 100 contributors only — repos with more will plateau at 100.

Loading…

Similar repos

capcom6

capcom6/android-sms-gateway

SMS Gateway for Android turns a smartphone into an SMS gateway API server,...

5.1k Kotlin Mobile
vernu

vernu/textbee

textbee is an open-source SMS gateway that converts any Android phone into a...

2.9k TypeScript IoT
dromara

dromara/SMS4J

SMS4J is a Java aggregation framework that simplifies integrating multiple SMS...

1.3k Java Dev Tools
telegram-sms

telegram-sms/telegram-sms

Telegram SMS is an Android application that forwards SMS messages and...

1.9k Kotlin Mobile
overtrue

overtrue/easy-sms

Easy SMS is a PHP library that provides a unified interface for sending SMS...

3.3k PHP Dev Tools
vs. alternatives
android-sms-gateway (4,874 stars, Kotlin)

Similar scope but higher star count. Both are Android phone-to-API gateways. android-sms-gateway lacks documented web UI or hosted service; appears to be library/app only. httpSMS adds managed hosting, web dashboard, and end-to-end encryption. Trade-off: android-sms-gateway may be more lightweight, httpSMS more feature-complete but more complex to self-host.

textbee (2,624 stars, TypeScript)

Close in star count. Similar premise (Android phone as SMS gateway). textbee emphasizes simplicity and lightweight setup. httpSMS offers more features (webhooks, rate limiting, message expiration, encryption) but higher operational overhead (requires Firebase, Cloudflare, etc.). textbee likely faster to deploy, httpSMS more enterprise-feature-rich.

telegram-sms (1,931 stars, Kotlin)

Related but distinct niche: bridges Telegram and SMS rather than exposing HTTP API. Solves different use case (Telegram-to-SMS routing vs. programmatic SMS gateway). Less direct competition, serves adjacent workflow.

easy-sms (3,330 stars, PHP)

Multi-provider SMS abstraction library, not a phone-based gateway. Targets developers integrating traditional SMS APIs (Twilio, Aliyun, etc.). httpSMS solves different problem: local phone control when virtual numbers unavailable. Complementary rather than competing.

SMS4J (1,264 stars, Java)

SMS provider abstraction library. Similar positioning to easy-sms. Does not solve httpSMS's core problem (lack of virtual number access in certain regions). Lower adoption than httpSMS but serves different use case.