Getting started

This documentation will explain how to run your own auto-update server.

Introduction

If you find this work helpful, please consider supporting my work by becoming a Github sponsor.

I made a bet to open-source all the code I built here instead of paywalling it. By opening it up instead of fighting and hiding, I believe we can make the world a better place.

Furthermore, I want to focus on Capgo tooling, and make it an open and transparent business.

But to make it possible, it is necessary for all of us to do our part, including you 🥹.

If Capgo doesn’t suit you, then pay your own price and back a bootstrapped Maker on your terms.

Consider Contributing

Features parity

If you choose to go with your own server, you will lose the 5-min setup flow.
You need to implement all of these features yourself.

Features	Capgo	Self hosted
Updates	✅	🚧
Auto revert	✅	🚧
Email alerts on fail	✅	🚧
Channels	✅	🚧
Channels Override	✅	🚧
Device Override	✅	🚧
Channels Settings	✅	🚧
Device Settings	✅	🚧
Custom ID	✅	🚧
Auto Set Channels	✅	🚧
API Channels	✅	🚧
Updates Statistics	✅	🚧
Fail Download Statistics	✅	🚧
App Usage Statistics	✅	🚧
Update Encryption	✅	🚧

Be mindful that you can’t use the Capgo cloud and your server at the same time.

Choose between Auto and Manual

In auto mode, part of the logic is handled by the Native code, updates are decided server side, this is more secure and allows fine grain updates, partial deployment to one device or group and more.

In manual mode, all the logic is handled by the JS.

Auto Update

Manual

Install Capacitor updater

npm install @capgo/capacitor-updater
npx cap sync

Prepare your bundle

To send updates to your app, you need to zip it. The best way to be certain your zip is good is to use the Capgo CLI for zipping.

npx @capgo/cli/latest bundle zip

You will have to serve this zip from your server on your own.

Auto Update

Manual