OverAir Get early access

Coming soon

Over-the-air code push for Flutter, on infrastructure you control.

OverAir lets teams ship Dart fixes and features to installed apps between store releases — signed, staged and reversible — from a control plane you can run yourself. We're building it now.

Get early access Follow the build on GitHub
  • Signed by default
  • Self-host or managed
  • Open core
signed updates staged rollouts automatic rollback delta downloads self-hosted or managed bring your own keys

What we're building

Built for teams that answer to auditors, not just app stores.

These are the commitments the product is built around. Nothing here depends on trusting a vendor you can't inspect.

01

Signed by default

Every update is cryptographically signed and verified on the device before anything else runs. Releases can require a second, human approval, and devices refuse anything that lacks it.

$ overair publish --channel production
→ compatible   release 2.14.0 ✓
→ package      delta 183 KB
→ signed       release key ✓  approver ✓
→ rollout      10% of devices

02

Staged rollouts, automatic rollback

Go from 1% to 100% at your own pace and pause or roll back at any point. An update that fails to start is set aside on the device and the app falls back on its own, even offline.

03

Run it where your data must live

A managed multi-region service, or the same software on your own Kubernetes, on-prem, or fully air-gapped. Bring your own keys. Data residency is a deployment choice, not a plan tier.

  • Managed
  • Your cloud
  • On-prem
  • Air-gapped

04

Open core, from day one

The code that runs inside your app is open source, and so is the community edition of the server. Read it before you ship it; run it without asking anyone.

  • On-device updater & SDKopen source
  • Command-line toolingopen source
  • Community server & consoleopen source

How it works

Three steps between a fix and a phone.

The workflow we're building toward. No store review in the loop, no surprises on the device.

  1. 1

    Build

    Build your release with OverAir's tooling. Each build records what it is compatible with, so an update can only ever reach a matching build.

  2. 2

    Publish

    Publish an update to a channel and choose how many devices see it first. Widen, pause or roll back from the console or from CI.

  3. 3

    Apply

    Devices verify the signature, download only what changed, and run the new code on the next launch. If it doesn't come up healthy, they revert without asking anyone.

Early access

Tell us about your app and where it has to run.

We're working with a small number of teams ahead of launch — especially those with residency, self-hosting or audit requirements. Every message gets a personal reply.

hello@overair.dev

Or follow along: github.com/overair-dev · @overairdev