Ship updates.
Skip the friction.

One platform to manage application updates, releases, and deployments across your entire technology stack.

Auditable SDKs and public docs, CLI-first. Stacklift tells you plainly what each stack can and can’t update over the air — no pretending.

$ stacklift deploy 2.4.0 --channel production --percentage 10

simulation

40 of 400 devices receive 2.4.0. Move up and nobody leaves the cohort — raising the percentage only adds devices.

One control plane. Five different kinds of release.

An OTA patch, a web deploy and an App Store build are different operations. Stacklift models each for what it really is, instead of squeezing them into one button.

Over-the-air updates
Signed JS bundles and patches delivered to installed apps, within each platform’s rules. Only for stacks where it’s technically and contractually possible.
Web deployments
Versioned, signed bundles. A deployment is an atomic repoint of a channel — your host serves it.
Backend deployments
Track and promote server bundles and container image digests across environments.
Native binary releases
APK, AAB and IPA files are recorded for visibility and compatibility tracking. They ship through the stores — Stacklift never claims to update them over the air.
Config & asset updates
Small signed JSON and asset bundles that your app fetches and applies itself.

From build to production in four steps

  1. 1

    Connect your app

    `stacklift init` detects your stack, validates it against its adapter and writes `stacklift.yaml`.

  2. 2

    Create a release

    Upload artifacts straight to object storage. The server re-hashes every byte, then signs it with your project’s Ed25519 key.

  3. 3

    Deploy gradually

    Push to a channel at 5%, then 25%, then everyone. Percentages only go up — and only when you say so.

  4. 4

    Watch, then keep or roll back

    Install success, failures and adoption stream in. A bad release goes back with one command, with the reason on record.

bash
npm install -g stacklift

stacklift login
stacklift init
stacklift release create --version 2.4.0 \
  --artifact android:js-bundle:./dist/android.zip \
  --artifact ios:js-bundle:./dist/ios.zip
stacklift deploy 2.4.0 --channel production --percentage 5
stacklift status

Honest support for 29 stacks

Every adapter publishes a capability matrix. A check means Stacklift implements it end to end; “partial” and “planned” mean exactly that. Nothing here claims over-the-air updates for native binaries. Desktop apps update by installing a new signed build, which Stacklift delivers and verifies.

StackStatusOTAWebBackendNativeDesktopConfig
Mobile
Flutter Dartplannedplannedpartialpartialpartial
React Native TypeScript / JavaScriptalphapartialpartialpartial
Expo TypeScript / JavaScriptalphapartialpartialpartial
Android (Kotlin) Kotlin / Javaalphapartialpartial
iOS (Swift) Swiftalphapartialpartial
Kotlin Multiplatform / Compose Multiplatform Kotlinalphapartialpartialpartial
Capacitor / Ionic TypeScript / JavaScriptalphapartialpartialpartial
NativeScript TypeScript / JavaScriptalphapartialpartialpartial
.NET MAUI C#alphapartialpartialpartial
Unity C#alphapartialpartialpartial
Desktop
Electron TypeScript / JavaScriptalphaplannedpartialpartialpartial
Tauri Rust + web frontendplannedplannedpartialpartialpartial
.NET desktop (WPF / WinForms / WinUI) C#alphapartialpartialpartial
macOS (Swift / AppKit) Swiftalphapartialpartialpartial
JVM desktop (JavaFX / Compose / Swing) Java / Kotlinalphapartialpartialpartial
Qt / C++ C++alphapartialpartialpartial
Other native desktop Anyalphapartialpartialpartial
Web
React (SPA) TypeScript / JavaScriptbeta
Next.js TypeScript / JavaScriptalpha
Vue TypeScript / JavaScriptalpha
Nuxt TypeScript / JavaScriptalpha
Angular TypeScriptalpha
Svelte TypeScript / JavaScriptalpha
SvelteKit TypeScript / JavaScriptalpha
Backend
Node.js TypeScript / JavaScriptalphapartial
Python Pythonalphapartial
Go Goalphapartial
Java / JVM Java / Kotlinalphapartial
.NET C#alphapartial

Flutter Dart OTA needs a patched engine and a patch toolchain that Stacklift doesn’t ship yet, so it’s listed as planned. React Native, Expo and Capacitor bundle updates are partial: control plane, signing and delivery work today; the on-device loader is on the roadmap. Desktop installers are delivered and verified, but your app runs them. Client SDKs are tested for TypeScript, Swift, Dart, .NET and Java; the Kotlin and Tauri ones are untested source. Details and restrictions per platform are in the adapter docs.

Release management that keeps its promises

A real state machine

Draft, uploading, processing, ready, deploying, active, failed, rolled back, archived. A release is only “active” when a channel actually serves it.

Verified artifacts

Checksums are recomputed server-side from the stored object. A mismatch fails the release before anything can deploy.

Channels and promotion

Production, staging, development, beta — and your own. Promote only what’s already live somewhere.

Compatible rollbacks only

A rollback is refused if the runtime version differs, a platform is missing, or an artifact is unverified. The reasons are shown.

Release comparison

Diff two releases’ artifacts, runtime and platforms, and see whether one can safely replace the other.

Everything audited

Who deployed, who paused, who rolled back and why — recorded and filterable.

Staged rollouts you control

Release to 1%, 5%, 10%, 25%, 50%, 75%, then 100%. Devices are bucketed by a stable hash, so the cohort only ever grows.

  • Manual by default. A rollout never moves without you unless you opt in to an explicit schedule.
  • Safety, not surprise. An optional failure-rate guard can pause a rollout. It can never expand one.
  • Pause, resume, cancel. Cancelling returns the cohort to the baseline; a rollback moves the whole channel.
  • Live. Progress and install health update as events arrive.
yaml
# stacklift.yaml
rollout:
  percentage: 5
  autoExpand: true        # explicit opt-in
  steps: [5, 25, 50, 100]
  intervalMinutes: 120
  maxFailureRate: 0.05    # auto-pause above 5%

The CLI is the product

Everything in the dashboard is a command first. JSON output, CI-friendly exit codes, and no interactive prompts when there’s no TTY.

terminal
$ stacklift release create --version 2.4.0 --channel staging
› Hashing 2 artifact(s)…
✔ Created release 2.4.0
› android/js-bundle  android.zip  1.8 MB
› ios/js-bundle      ios.zip      1.9 MB
› Waiting for server-side verification…
✔ Release 2.4.0 is READY — every artifact checksum-verified and signed.
✔ 2.4.0 → staging: deployed to 100%

$ stacklift release promote 2.4.0 --to production --percentage 10
✔ 2.4.0 → production: rollout started at 10% (in progress — not fully live)

$ stacklift status --json | jq '.channels[].currentRelease.version'

Illustrative output. Run stacklift --help for every command: login, init, project, release, channel, deploy, rollout, status, doctor, upgrade.

Fits the pipeline you have

CI works today through the CLI and a scoped project key. Deeper source-control triggers are planned and marked as such.

Available

  • Webhooks — HMAC-signed, retried, with delivery logs
  • GitHub Actions — via the CLI
  • GitLab CI/CD — via the CLI
  • Jenkins — via the CLI
  • Docker — run the CLI; track image digests

Planned

  • GitHub, GitLab and Bitbucket branch/tag release triggers
  • Slack notifications (use a webhook relay today)
  • Discord notifications (use a webhook relay today)
  • First-party GitHub Action and GitLab component

Security and reliability, built in

Signed artifacts

Ed25519 per project. Private keys are encrypted at rest (AES-256-GCM) and never leave the control plane.

Integrity everywhere

Server re-hashing on upload; SDKs verify size, SHA-256 and signature before applying anything.

Tenant isolation

Every query is scoped to an organization. Another tenant’s resource isn’t forbidden — it’s simply not found.

Scoped credentials

Public keys can only check for updates. Secret keys are confined to one project and its scopes. Both are stored hashed.

Control and delivery planes

Artifacts are served from object storage via short-lived signed URLs, never through the API.

Idempotent operations

Deploys accept an idempotency key; jobs retry with backoff; releases move through a locked state machine.

Read the security model

Pricing

Stacklift is a hosted service. The plans below are the intended shape — billing isn’t live, so nothing is charged and limits aren’t enforced yet.

Free

$0

For side projects and evaluation

  • 1 organization, up to 3 projects
  • All stack adapters
  • Staged rollouts and rollbacks
  • Community support

Team

$49/month

For product teams shipping weekly

  • Unlimited projects
  • Roles and audit log
  • Webhooks with delivery history
  • Email support

Enterprise

Custom

For security-conscious organizations

  • SSO and SCIM (planned)
  • Bring-your-own KMS
  • Private storage and CDN
  • Support SLA

Questions, answered plainly

Can Stacklift update my native iOS or Android app over the air?+

No. Native binaries must go through the App Store and Google Play. Stacklift records those releases for tracking, and delivers JavaScript bundles and assets where the platform allows interpreted-code updates.

Is Flutter OTA available?+

Not yet. Dart code push needs a patched engine and a patch builder, which Stacklift doesn’t ship. Flutter is supported for web builds, config/assets and native release tracking.

Do you host my web app or API?+

No. Stacklift versions, signs and serves the build artifacts; your host or CDN serves the site. Deployments repoint a channel.

What is a runtime version?+

A compatibility key you control. An update only reaches binaries reporting the same runtime version, so a JS bundle never lands on an incompatible native build.

Will a rollout ever expand on its own?+

Only if you configured an auto-expand policy with an interval. Otherwise percentages change only when a person changes them.

Can I self-host it?+

Not today — Stacklift is hosted only. Your apps never depend on it to run: updates are plain signed files you can serve yourself, and the SDK source is public for you to audit.

Ship your first update today.