TOOLS
My Vodafone
Carrier app with account, top-up, support, and notification surfaces.
11.1M installs4.6 rating
Ionic Enterprise Plugins
Open source alternatives to Ionic Enterprise Plugins
Move from closed enterprise-only plugins to Capgo's open source Capacitor stack. Use the plugins before you pay, add support when it becomes critical, and use Builder when native builds are part of the migration.
Why Capgo is different from an enterprise plugin contract
Ionic Enterprise plugins are sold as a commercial package. Capgo takes a different path: the plugins are open source, the migration guides are public, and paid help is there when your team needs guaranteed response times, expert migration work, or native build capacity.
Open source first
Capgo-maintained plugins are visible, auditable, and forkable. You can inspect the native code, patch it, or keep control if your security team asks what ships in the app.
Use before you pay
You do not need a paid enterprise contract just to try the plugins. Pay when it is critical: migration help, guaranteed support, governance, or business-critical delivery.
A broader Capacitor stack
The directory covers 142+ plugins across auth, storage, payments, MDM, analytics, device APIs, native UI, and live updates. Start from the exact native capability you need, not a bundle.
Builder included in the path
When a migration touches native projects, Capgo Builder can produce iOS and Android builds with logs, signing, and store-ready artifacts instead of leaving CI work to your team.
| Decision | Capgo | Typical Ionic enterprise route |
|---|---|---|
| Source code and auditability | Open source plugin code, public docs, and the option to fork or self-maintain if your policy requires it. | Commercial packages where access and fixes depend on the vendor relationship. |
| When you pay | Use the plugin stack first. Pay for support, migration, enterprise guarantees, or native build capacity when those become important. | Enterprise value is commonly tied to a paid contract before teams can standardize on the package. |
| Native delivery | Capgo pairs plugins with live updates and Builder, so teams can migrate code and still produce signed native builds. | Plugin licensing and CI/build delivery are often separate decisions. |
| App composition products | Capgo does not ship an Ionic Portals or App Federation replacement yet. We focus on plugins, live updates, native builds, and custom native gaps. | If your main requirement is embedding multiple mini-apps in one native shell, keep evaluating dedicated portal or federation tools. |
Plugin replacements and migration guides
Start with the direct replacements, then decide where you need support, migration help, or Capgo Builder for native delivery.
| Ionic plugin | Capgo alternative | Migration guide |
|---|---|---|
| Ionic Secure Storage | Fast SQL or Data Storage SQLite | Migration guide |
| Ionic Auth Connect | Social Login | Migration guide |
| Ionic Identity Vault | Native Biometric + Fast SQL or Data Storage SQLite | Migration guide |
| Ionic Intune | Intune | Migration guide |
| Ionic Payments | @capgo/capacitor-pay | Migration guide |
| Ionic Zebra Scanner | Zebra DataWedge | Migration guide |
| @ionic-enterprise/ssl-pinning | capacitor-ssl-pinning | Migration guide |
Migration steps
1
Map each Ionic enterprise plugin to its Capgo replacement.
2
Install the new plugins and sync native code.
3
Migrate stored data and update auth flows, then remove Ionic dependencies.
Where Capgo fits
What Capgo replaces today
Capgo is not trying to clone every Ionic enterprise product. It is the practical path when you need open source native plugins, live updates, native builds, and direct help for app-specific native gaps.
Strong fit today
- Enterprise plugin migration
- Secure storage, biometrics, social login, Intune, payments, Zebra scanning, SSL pinning, and related Capacitor-native needs.
- Broader plugin coverage
- 142+ plugins across mobile capabilities, with public docs and package-level migration paths.
- Native delivery
- Use Capgo Builder when native project changes need signed iOS and Android builds.
- Critical support
- Keep the open source path for normal use, then add paid support or migration services when the business risk justifies it.
Not a full Ionic platform clone
- No Ionic Portals replacement yet
- Capgo does not yet productize embedded mini-app orchestration inside a host native app.
- No App Federation product yet
- If your priority is federated app composition, keep that evaluation separate from plugin migration.
- No forced bundle
- Capgo is strongest when you choose the plugin, live update, build, or support layer you need instead of buying a large suite.
- Custom gaps are handled directly
- If a feature is missing, we would rather scope the native work than imply it already exists.
Open source plugins. Optional paid support.
Every Capgo plugin is open source, so you can audit, fork, and self-host if you want. If you need guaranteed response times or migration help, paid support is optional - see support options.
That means a prototype, internal tool, or noncritical plugin migration can start without procurement. If the feature becomes production critical, support becomes a risk-control decision instead of a license tax.
What paid help is for
- Guaranteed response expectations when a native capability blocks a release.
- Migration review for storage, authentication, biometric, MDM, or payment flows.
- Custom native work through Capgo Consulting when a gap is specific to your app.
- Builder setup help for signing, build logs, and repeatable iOS or Android release artifacts.
Apps built with Capacitor
Enterprise self-service apps depend on native integrations
Telecom and account apps touch authentication, device state, notifications, support, and payments. Open Capacitor plugins help replace expensive closed SDK coverage one capability at a time.
- App type
- Plugin replacement
- Store categories
- TOOLS, PRODUCTIVITY
- Source
- Public store dataset
PRODUCTIVITY
My Swisscom
Self-service app with billing, plan, support, and device-management paths.
1.8M installs4.4 rating
TOOLS
Mi Orange
Telecom account app where native capabilities can be replaced incrementally.
9.3M installs4.2 rating
Plugin migration proof
Teams replacing plugin gaps need a release path that keeps working
Short reviews from developers using Capgo plugins and updater workflows in production apps.
Mikołaj Wilczek
Principal Mobile Platform Engineer, Tellent
“We originally discovered Capgo through its plugins, and that turned out to be a great entry point into a much more efficient release process for our team.”
Sergiu S
Lead Developer, drivolino GmbH
“The Capgo Capacitor Updater plugin completely transformed how we ship updates. What used to take days now takes just minutes.”
Next step
Pick the migration path
Start with the plugin replacement, then add Builder or hands-on support only when native delivery becomes the bottleneck.
Find the replacement plugin
Search the open source Capgo plugin directory and map each Ionic dependency to a maintained Capacitor package.
Install and migrate safely
Use the docs to update native projects, migrate stored data, and remove closed plugin dependencies without guessing.
Build the native release
When the migration changes iOS or Android code, use Capgo Builder for signed artifacts, logs, and repeatable delivery.
Bring Capgo in when it is critical
Get help for authentication, storage, MDM, payments, or custom native gaps that need production-grade review.
Ready to move from closed enterprise plugins?
Start with the migration guides, use the open source plugins, or bring in Capgo when support and delivery become critical.