Shipping code over the air shouldn't mean trusting it blindly. Every Birdify bundle is cryptographically signed, verified on the device before it runs, and revertible in one command, and no native code is ever downloaded.
fetch bundle → patch #3 (4.2 MB)verify sha256 … ok 9f2c…a71bverify signature … ok key birdify:shop_appapply on next launch ✓Bundles are signed with your project key at publish time and delivered over TLS 1.3. Before applying an update, the SDK re-computes its SHA-256 checksum and checks the signature; anything that doesn't match is dropped, and the app keeps the last good bundle.
A patch that fails to boot auto-reverts on device, and one command pulls it from the whole fleet. Broken updates never strand your users.
How rollback worksPublishing is scoped per project and gated by API keys you control. Bundles are served from edge storage over encrypted transport, and you can self-host so they never leave your infrastructure.
$ birdify verify patch#3 checksum 9f2c…a71b signer birdify:shop_app signature valid ✓ native code none safe to apply ✓Every release and patch is signed the moment it's cut. Verify any artifact yourself, the same check the SDK runs on device before it applies an update.
The docs walk through signing, on-device verification, the rollback state machine, and how to run Birdify self-hosted, with the exact commands.
How signing, verification and rollback work, and where Birdify stands on compliance.
Install the CLI and start shipping over the air on Flutter and React Native. No rebuilds, no store review, no waiting.
2,000 patch installs a month free · no card
$curl -fsSL https://cli.birdify.dev/install.sh | sh