Capgo Crossed $25K MRR. The Open-Source Plugin Was the Acquisition Engine.
Capgo crossed $25,000 MRR by making live updates an open-source CLI plugin that slots into existing GitHub Actions pipelines, using 78 community plugins and sunset migration SEO as its organic acquisition engine.
The short version
Capgo, an open-source live update and native build platform for Capacitor mobile apps built by solo founder Martin Donadieu (@martindonadieu), publicly confirmed crossing $25,000 MRR on September 9, 2026. 1 Donadieu verified the milestone while reflecting on leaving venture-backed startups to bootstrap Capgo solo, tracking progress between $20,000 and $30,000 MRR. 2
Loading content card…
The operating mechanism behind Capgo is unusually clean for developer tooling. Software engineers avoid vendor lock-in. Donadieu bypassed resistance by open-sourcing the client runtime under MPL-2.0 and the backend under AGPL-3.0. 3 Instead of replacing GitHub Actions or GitLab CI, Capgo runs as a two-line CLI plugin for instant over-the-air updates and cloud builds.
Growth came without paid ads or outbound sales reps. Donadieu scaled Capgo by maintaining 78 open-source Capacitor plugins, capturing search traffic as competitors Microsoft App Center and Ionic Appflow wound down, and keeping a transparent $12 monthly entry tier unchanged since launch. 34
That packaging proves a solo developer can build recurring developer infrastructure. The four-year timeline, plugin maintenance, and founder background remain structural advantages a weekend clone cannot match.
Snapshot
| Metric | Public evidence | How to read the number |
|---|---|---|
| MRR | $25,000+ disclosed September 9, 2026; live profile tracks $20k to $30k MRR; IdeaWave logs $29.5k/mo | Verified milestone across founder posts and podcast release. Margins, churn, and plan mix remain private. 125 |
| Team size | Solo founder (Martin Donadieu); zero full-time staff | Satisfies the channel filter of three or fewer team members. Donadieu left Naas in July 2021 to build independently. 6 |
| Product age | Prototype created in December 2021; commercial cloud launched early 2022; active over 4.5 years | Excludes one-week viral spikes and clears the minimum six-month age requirement. 6 |
| Traction & Scale | Customer apps include Nana (2.5M downloads), Snowqueen (1.8M), Shelf (950k), Suez (3.2M), Janitor (750k); 78 community plugins maintained | Download numbers represent end-user mobile installs across client apps, not direct Capgo paying accounts. Total active subscription count remains undisclosed. 47 |
| Pricing structure | Solo at $12/mo (annual) or $14/mo; Maker at $33/mo or $39/mo; Team at $83/mo or $99/mo; Enterprise at $208+/mo; prepaid credits available | Paid tiers meter along Monthly Active Users (MAU), storage, bandwidth, and build hours. A 14-day free trial is offered without a permanent free plan. 4 |
| Funding | 100% bootstrapped; self-funded since departing Naas | No institutional venture capital rounds raised for Capgo. 16 |
The public disclosure confirms a bootstrapped solo developer business generating at least $300,000 in annual run rate. Net retention, acquisition cost, and voluntary churn remain private.
Origin: a production bug on a $400/month side project
In July 2021, Martin Donadieu stepped down from Naas, an open-source data platform he had co-founded in 2019, to focus on solo software development. 6 During his first six months solo, Donadieu focused on Captime, a sports timing app generating $400 per month. 6
In December 2021, while rewriting Captime, Donadieu introduced a critical production bug. Traditional store review meant days of downtime that threatened to wipe out user trust and subscriptions. 6
Donadieu searched for a tool to push web-layer code directly to Capacitor. Ionic Appflow was priced for enterprises far beyond a $400/month app. 6 When Donadieu asked Ionic for an indie tier, Ionic declined, stating solo developers were not their audience. 6 Microsoft App Center was already withdrawing hybrid framework support. 6
Faced with a broken production app, Donadieu spent a month building his own mechanism: downloading a zip archive of web assets from a remote URL, extracting files locally, and hot-swapping the web view root without restarting the native container. 6
When Donadieu published the code on GitHub, Capacitor developers started starring the repository. Teams noted that self-managing hosting, signing, rollbacks, and rollouts was too fragile for production and asked for a hosted service. 6 Inbound demand turned an emergency fix for a $400/month app into Capgo.
Wedge: "keep your CI" and the open-source escape hatch
Capgo wins against competitors by solving two distinct developer frictions: operational displacement and vendor lock-in.
Most mobile deployment products position themselves as CI/CD replacements. Platforms like Ionic Appflow or Capawesome Cloud require teams to connect repositories, transfer secrets, abandon existing GitHub Actions or GitLab pipelines, and adopt a new build dashboard. 3 That replacement model imposes high switching costs: workflow files must be rewritten and developers must monitor another dashboard.
Capgo approached the architecture with a different thesis: keep your CI. 3 Instead of demanding pipeline migration, Capgo integrates directly into whatever automation developers already run. After standard web tests and asset builds complete in GitHub Actions, the developer adds two CLI commands:
npx @capgo/cli@latest bundle upload
npx @capgo/cli@latest build requestThe first command ships updated web bundles to Capgo's distribution network for immediate over-the-air deployment. The second command dispatches native iOS and Android build requests to Capgo's cloud builders when native dependencies change. 3 The developer never leaves GitHub. Status alerts, pull request preview links, and build logs flow directly back into the pull request discussion.
The second half of Capgo's wedge addresses vendor capture. Developers fear third-party deployment vendors will raise prices or shut down, stranding production mobile apps.
Donadieu eliminated that fear by structuring Capgo around open-source licenses:
- Client updater plugin: Distributed under MPL-2.0, allowing any developer to inspect code, modify native bindings, and bundle the plugin into commercial apps without fees. 3
- Backend cloud server: Distributed under AGPL-3.0, enabling teams to self-host the entire update server, database, and bundle delivery mechanism on their own infrastructure if Capgo ever changes terms. 3
In contrast, alternatives like Capawesome Cloud provide an open-source CLI but keep backend infrastructure closed source, leaving metadata and rollout logic locked in their cloud. 3 By providing a complete self-hosting option, Capgo removes adoption risk. Developers pick Capgo Cloud because paying $12 or $33 per month costs far less than running edge servers and managing continuous delivery pipelines.
Pricing teardown: $12 entry anchor, MAU ladders, and credit overages
Capgo structures its pricing around usage dimensions that expand naturally with customer growth: monthly active users (MAU), network bandwidth, storage, and build machine hours. 4
| Plan | Public price (annual / monthly) | Included limits | Core buyer profile |
|---|---|---|---|
| Solo | $12/mo ($146/yr) or $14/mo | 2,000 MAU, 100 GiB bandwidth, 20 GiB storage, 1 build hour, 2 concurrent builds | Indie developers and early-stage side projects shipping first releases |
| Maker | $33/mo ($396/yr) or $39/mo | 10,000 MAU, 1,000 GiB bandwidth, 50 GiB storage, 2 build hours, 3 concurrent builds | Growing production apps with established user traction and regular release cycles |
| Team | $83/mo ($998/yr) or $99/mo | 100,000 MAU, 10,000 GiB bandwidth, 100 GiB storage, 10 build hours, 4 concurrent builds | Medium software teams requiring higher concurrency, large bandwidth, and org logs |
| Enterprise | $208+/mo ($2,490+/yr) or $249+/mo | 1,000,000+ MAU, 100,000+ GiB bandwidth, 200+ GiB storage, 333+ build hours, 6 concurrent builds | Scaled mobile applications requiring custom SLAs, dedicated Slack channels, and SOC 2 compliance |
The foundational anchor in Capgo's pricing is the $12 per month Solo plan. Donadieu established that price point at launch in 2022 and has maintained it without price hikes. 3 For an indie maker, $12 per month goes on a personal credit card without corporate approval. It provides full access to every core capability: live updates, native builds, push notifications, and runtime observability.
Capgo avoids permanent free plans. Instead, every new account receives a 14-day unlimited free trial across all features. 4 Many developer tools accumulate non-paying hobbyists that consume bandwidth and support. Capgo forces users to evaluate whether automated delivery justifies a monthly subscription within two weeks. Developers wanting a zero-cost solution can self-host the open-source repository.
To handle traffic spikes, Capgo offers prepaid pay-as-you-go credits valid for one year. 4 Credits cover extra MAU ($0.003 to $0.0007), bandwidth ($0.06 to $0.01 per GiB), and build minutes ($0.08 to $0.04). Installed app updates continue functioning even if an account reaches its limit; only new downloads pause until an upgrade or credit top-up.
Acquisition channel: open-source plugin loop and sunset migration SEO
Capgo scaled past $25,000 MRR without running paid ads or employing outbound sales staff. Customer acquisition relies on two systematic organic funnels: the open-source plugin ecosystem and high-intent migration SEO.
Dominant channel 1: the 78-plugin open-source distribution loop
The primary driver of developer discovery is Capgo's presence across the open-source Capacitor ecosystem. When developers build mobile apps with Capacitor, they hit gaps in native device access. Rather than treating open source as marketing collateral, Donadieu systematically authored and maintained 78 Capacitor plugins under the
@capgo scope on npm and GitHub. 7When a developer searches npm for camera previews, audio, or in-app reviews, they find a
@capgo package. Documentation and README files prominently feature Capgo's live update platform. When that developer later encounters app store delays, Capgo is already a trusted dependency in their codebase.Dominant channel 2: bottom-of-funnel migration SEO
Capgo's second acquisition engine captures high-intent developers seeking alternatives to retiring industry solutions. Between 2024 and 2026, two dominant mobile deployment platforms announced end-of-life schedules:
- Microsoft App Center: Microsoft retired App Center build and distribution services on March 31, 2025, with legacy analytics ending March 31, 2027. 3 CodePush stopped operating as a Microsoft-hosted cloud service.
- Ionic Appflow: Ionic stopped accepting new commercial sales on February 11, 2025, placing the platform on a wind-down schedule toward retirement on December 31, 2027. 3
Donadieu captured displaced engineering teams by publishing technical migration guides comparing CI/CD platforms and providing CLI replacements. 3 When engineering leads search Google for App Center alternatives or Appflow migration guides, Capgo ranks at the top of organic results.
Channel scorecard
| Acquisition Channel | Role in growth | Founder execution verdict |
|---|---|---|
| Open-source plugins (npm/GitHub) | Primary discovery engine | High leverage; 78 maintained packages create continuous inbound developer trust and top-of-funnel installations. 7 |
| Migration & comparison SEO | Primary commercial converter | High conversion; captures developers displaced by Microsoft App Center retirement and Ionic Appflow wind-down. 3 |
| Build-in-public (X / Twitter) | Secondary authority & retention | Documents revenue milestones, roadmap items, and technical deep-dives to build peer credibility. 12 |
| Paid ads (Google / Social) | Unused / Zero spend | Developers filter out sponsored ads; organic open-source adoption provides superior qualification. |
| Outbound enterprise sales | Unused / Zero staff | Self-serve onboarding and transparent documentation eliminate the overhead of sales reps. |
Replication checklist: cloning an open-core developer infrastructure wedge
A solo technical founder aiming to build an open-core infrastructure SaaS can follow this ten-part checklist:
- Target an unbundled framework bottleneck. Find frameworks (like Capacitor, Tauri, or Expo) where developers face operational pain that incumbents price exclusively for enterprise buyers.
- Open source the client runtime under a permissive license. Release the client library under MPL-2.0 or MIT to remove integration friction.
- Open source the backend under a copyleft license. Provide an AGPL-3.0 self-hostable server core to eliminate vendor lock-in fears and earn developer trust.
- Complement existing CI/CD instead of replacing it. Build CLI commands that slot into existing GitHub Actions workflows so teams avoid pipeline switching costs.
- Anchor entry pricing at an accessible level. Keep a $10 to $15 monthly tier with full feature parity so individual developers can adopt on personal cards.
- Meter along natural consumption vectors. Scale billing along active users, bandwidth, storage, and build minutes as client applications grow.
- Swap permanent free tiers for time-limited trials. Offer a 14-day trial and direct zero-budget users to the self-hosted repo to protect margins.
- Offer prepaid credits for overages. Prevent unexpected traffic spikes from breaking production deployments or triggering billing shocks.
- Maintain ecosystem utility packages. Build adjacent plugins that solve real framework gaps; each package becomes an inbound discovery node.
- Publish authoritative migration guides for retiring tools. Target displaced commercial demand by documenting exact migration paths from sunsetting legacy platforms.
Honest assessment: the unfair advantages you cannot clone in a weekend
While Capgo's architecture is replicable, several foundational advantages cannot be cloned:
- Prior venture co-founder background: Donadieu spent years co-founding Naas, an open-source platform. 6 That venture background gave him deep understanding of open-core economics and cloud operations.
- A 4.5-year commitment horizon: Donadieu spent over 54 months debugging mobile quirks and supporting users. That multi-year endurance acts as a moat against casual imitators.
- Ecosystem stewardship of 78 plugins: Maintaining 78 community plugins across new iOS and Android releases creates an ecosystem moat few solo developers can match.
- Incumbent retirement windfall: Capgo benefited directly from Microsoft deprecating App Center in March 2025 and Ionic pausing commercial Appflow sales in February 2025. 3 Founders cannot manufacture market timing where two legacy tools exit simultaneously.
Recognizing these factors prevents unrealistic expectations. Capgo succeeded because an experienced systems engineer spent four years turning open-source maintenance into a sustainable infrastructure business.
Three lessons that generalize
- Complement existing pipelines rather than replacing them. Capgo won market share by letting developers keep GitHub Actions and adding live updates with two CLI commands.
- Open source the interface to eliminate lock-in fear; monetize operational peace of mind. Permissive client code and copyleft backends remove adoption resistance while developers pay $12 to $83 per month to avoid running distribution infrastructure.
- Turn ecosystem maintenance into an acquisition engine. Maintaining 78 community plugins gave Capgo permanent organic placement across package searches, creating a moat paid ads cannot match.
Sources table
| Source | What it establishes |
|---|---|
| Maya BuildingNow Ep 5 Announcement (Sep 9, 2026) | Public confirmation of Capgo crossing $25k+ MRR; solo bootstrap journey after leaving VC startup world. |
| Martin Donadieu BuildingNow Response (Sep 9, 2026) | Founder verification of interview appearance and revenue milestones; live profile tracking $20k to $30k MRR. |
| Capgo CI/CD Platform Comparison (Sep 2, 2026) | Architecture comparison; "Keep your CI" wedge; open-source MPL-2.0 and AGPL-3.0 licensing; $12 price stability since launch; Microsoft App Center and Ionic Appflow retirement dates. |
| Capgo Pricing Documentation | Complete pricing tier specs: Solo ($12/mo), Maker ($33/mo), Team ($83/mo), Enterprise ($208+/mo); 14-day free trial; prepaid credit overage rates; customer app download metrics. |
| How Capgo is Born (Updated Aug 27, 2026) | Founder origin story; departure from Naas in July 2021; Captime production bug in December 2021; $400/mo side project; Ionic Appflow pricing friction; solo team confirmation. |
| IdeaWave Developer Tools Index | Third-party revenue verification logging Capgo / Martin Donadieu at $29.5k/mo developer tools bracket. |
| Capgo 2025 Year in Review | Scale of open-source catalog; growth from 20 to 78 maintained Capacitor plugins across community repositories. |
References
- 1
- 2
- 3
- 4Capgo pricing documentation
capgo.app
- 5IdeaWave developer tools startup index
ideawave.io
- 6
- 7
This story was produced automatically by a channel. One sentence is all it takes for Neodrop to keep producing for you.