Markdown

Stack adapters

Stacklift does not assume every stack can be updated the same way. Each ecosystem is an adapter that declares what is technically and contractually possible, and the control plane enforces it.

An adapter describes:

  • Capabilities — for each update mechanism (ota, web-deploy, backend-deploy, native-release, desktop-update, config-assets): a support level (supported, partial, planned, unsupported), platforms, whether clients verify signatures, platform restrictions and Stacklift's own limitations.
  • Artifacts — accepted kinds, file extensions, size caps and platforms.
  • Rollbackable kinds — which artifact kinds can be reverted by repointing a channel. Native binaries and desktop installers never can.
  • Detection — how stacklift init recognises the stack from a file listing.
  • Validation — project configuration and artifact checks (validateProjectConfig, validateArtifact).
  • Integration guide — Markdown shown in the dashboard and docs.
  • Client runtime — whether anything exists on the device side to *apply* updates.
ts
interface StackAdapter {
  id: string; displayName: string; language: string;
  ecosystem: 'mobile' | 'desktop' | 'web' | 'backend';
  maturity: 'beta' | 'alpha' | 'planned';
  clientRuntime: { status: 'available' | 'partial' | 'planned' | 'not-applicable'; notes: string };
  platforms: Platform[];
  capabilities: AdapterCapability[];
  artifacts: ArtifactSpec[];
  rollbackableKinds: ArtifactKind[];
  detect(probe: FileProbe): DetectionResult;
  validateProjectConfig(config): ValidationIssue[];
  validateArtifact(input): ValidationIssue[];
  integrationGuide(): string;
}

Register a new adapter with registry.register(adapter) from @stacklift/adapters. Everything else — the API, CLI validation, dashboard capability panel and this page — reads from the registry.

Capability matrix

Generated from the registry by pnpm docs:adapters (CI fails if it is stale).

<!-- adapters:start (generated by scripts/adapters-docs.mjs — do not edit) -->

Legend: supported = implemented end to end; *partial* = usable with the restrictions listed in the adapter; *planned* = designed, not implemented; *never* = technically or contractually impossible and never offered; *n/a* = not a capability of this stack.

Mobile (and cross-platform)

StackMaturityPlatformsOTAServer UIScriptsNative releaseDesktop installerConfig & assets
flutter Flutterplannedandroid, ios, web, windows, macos, linuxplannedpartialpartialpartialpartialpartial
react-native React Nativealphaandroid, iospartialpartialn/apartialn/apartial
expo Expoalphaandroid, iospartialn/an/apartialn/apartial
android Android (Kotlin)alphaandroidneverpartialpartialpartialn/apartial
ios iOS (Swift)alphaiosneverpartialpartialpartialn/apartial
kmp Kotlin Multiplatform / Compose Multiplatformalphaandroid, ios, windows, macos, linuxneverpartialpartialpartialpartialpartial
capacitor Capacitor / Ionicalphaandroid, ios, webpartialn/an/apartialn/apartial
nativescript NativeScriptalphaandroid, iospartialn/an/apartialn/apartial
maui .NET MAUIalphaandroid, ios, windows, macosneverpartialpartialpartialpartialpartial
unity Unityalphaandroid, ios, windows, macos, linuxneverpartialpartialpartialpartialpartial

Client runtime (what exists on the device to apply updates):

  • Flutter — *partial*. The Dart SDK (packages/sdk-dart) checks, downloads and verifies config/asset bundles, web builds and desktop installers, and with packages/sdk-flutter-scripts runs signed script bundles (scripted logic updates). Dart code OTA on Android/iOS ("code push") needs a patched Flutter engine and a patch toolchain Stacklift does NOT ship.
  • React Native — *partial*. @stacklift/react-native (packages/sdk-react-native) loads a new JS bundle on the next launch, confirms it, and rolls back to the last good or built-in bundle when a launch never confirms or crashes first. Its native side is the Swift SDK (iOS) and the Android SDK, which verify every bundle (SHA-256 + Ed25519). It also renders server-driven screens. Verified on the iOS simulator, an Android emulator and a physical Android 16 phone; not published to npm yet.
  • Expo — *partial*. @stacklift/sdk-js performs check → download → verification in JS. Activating the bundle needs a native loader or an implementation of the Expo Updates protocol; Stacklift ships neither, so Expo apps do not use expo-updates against Stacklift yet.
  • Android (Kotlin) — *not-applicable*. Binaries are distributed by the platform store. Remote config/asset bundles can be fetched and verified with the Android SDK (packages/sdk-android: Compose screens, QuickJS scripts, update lifecycle; built on the Java SDK in packages/sdk-java; tested on an Android 17 emulator and a physical Android 16 phone; Ed25519 needs Android API 33+, or register BouncyCastle/Conscrypt).
  • iOS (Swift) — *not-applicable*. Binaries are distributed by the platform store. Remote config/asset bundles can be fetched and verified with the Swift package (packages/sdk-swift, tested with swift test on macOS).
  • Kotlin Multiplatform / Compose Multiplatform — *partial*. On Android and JVM desktop use the Java SDK (packages/sdk-java, tested on JDK 21). packages/sdk-kotlin is a coroutine wrapper over it for androidMain/jvmMain; it has NOT been compiled or tested (no Kotlin toolchain in Stacklift CI yet). There is no Kotlin iOS implementation: call the Swift package (packages/sdk-swift) from iOS code.
  • Capacitor / Ionic — *partial*. @stacklift/sdk-js checks, downloads and verifies the web bundle. Unpacking it and pointing the WebView at it needs a native Capacitor plugin that Stacklift does not ship yet.
  • NativeScript — *partial*. @stacklift/sdk-js checks, downloads and verifies the bundle. Activating it on-device is not implemented.
  • .NET MAUI — *partial*. Stacklift.Sdk (netstandard2.0, tested on .NET 10) checks, downloads and verifies. MAUI platform projects were not built here.
  • Unity — *partial*. Stacklift.Sdk (netstandard2.0) can be used from Unity for check, download and verification; it needs the BouncyCastle assembly. Not run inside Unity here. Stacklift does not implement the Addressables remote-catalog protocol.

Desktop

StackMaturityPlatformsDesktop installerNative releaseOTAConfig & assets
electron Electronalphawindows, macos, linuxpartialpartialplannedpartial
tauri Tauriplannedwindows, macos, linuxpartialpartialplannedpartial
dotnet-desktop .NET desktop (WPF / WinForms / WinUI)alphawindowspartialpartialneverpartial
macos macOS (Swift / AppKit)alphamacospartialpartialneverpartial
jvm-desktop JVM desktop (JavaFX / Compose / Swing)alphawindows, macos, linuxpartialpartialneverpartial
qt Qt / C++alphawindows, macos, linuxpartialpartialneverpartial
native-desktop Other native desktopalphawindows, macos, linuxpartialpartialneverpartial

Client runtime (what exists on the device to apply updates):

  • Electron — *partial*. @stacklift/sdk-electron checks, downloads and verifies the installer in the main process and hands it to the OS. It is unit-tested with fakes for the Electron APIs, not inside a running Electron app. No in-place asar patching.
  • Tauri — *planned*. A Rust plugin is provided as source in packages/sdk-tauri. It has NOT been compiled or tested (no Rust toolchain in Stacklift CI yet). From the web frontend you can use @stacklift/sdk-js for check and verification.
  • .NET desktop (WPF / WinForms / WinUI) — *partial*. Stacklift.Sdk (netstandard2.0, tested on .NET 10) checks, downloads and verifies. Launching the MSI/MSIX/EXE is done by your app.
  • macOS (Swift / AppKit) — *partial*. The Stacklift Swift package (CryptoKit, tested with swift test on macOS) checks, downloads and verifies. Opening the DMG/PKG is done by your app. Sparkle can still be used for the install step.
  • JVM desktop (JavaFX / Compose / Swing) — *partial*. The Java SDK (JDK 17+, no dependencies, tested on JDK 21) checks, downloads and verifies. Running the installer is done by your app.
  • Qt / C++ — *planned*. No C++ SDK is shipped. The delivery API is plain HTTPS + JSON and the signature is Ed25519 over a documented text payload, so any language can verify it (see docs/sdk.md).
  • Other native desktop — *planned*. Choose this for any toolkit without its own adapter (GTK, wxWidgets, Win32, Go, Rust ...). No client SDK is shipped for it; the HTTP API and signature format are documented in docs/sdk.md.

Web

StackMaturityPlatformsWeb deployConfig & assets
react React (SPA)betawebsupportedsupported
nextjs Next.jsalphawebsupportedsupported
vue Vuealphawebsupportedsupported
nuxt Nuxtalphawebsupportedsupported
angular Angularalphawebsupportedsupported
svelte Sveltealphawebsupportedsupported
sveltekit SvelteKitalphawebsupportedsupported

Client runtime (what exists on the device to apply updates):

  • React (SPA) — *partial*. Stacklift versions, signs and serves the build. Serving it to users is up to your host/edge/CDN: fetch the verified artifact in your deploy pipeline with the delivery API (docs/sdk.md) or @stacklift/sdk-core (Node) / @stacklift/sdk-js. No hosting is provided.
  • Next.js — *partial*. Stacklift versions, signs and serves the build. Serving it to users is up to your host/edge/CDN: fetch the verified artifact in your deploy pipeline with the delivery API (docs/sdk.md) or @stacklift/sdk-core (Node) / @stacklift/sdk-js. No hosting is provided.
  • Vue — *partial*. Stacklift versions, signs and serves the build. Serving it to users is up to your host/edge/CDN: fetch the verified artifact in your deploy pipeline with the delivery API (docs/sdk.md) or @stacklift/sdk-core (Node) / @stacklift/sdk-js. No hosting is provided.
  • Nuxt — *partial*. Stacklift versions, signs and serves the build. Serving it to users is up to your host/edge/CDN: fetch the verified artifact in your deploy pipeline with the delivery API (docs/sdk.md) or @stacklift/sdk-core (Node) / @stacklift/sdk-js. No hosting is provided.
  • Angular — *partial*. Stacklift versions, signs and serves the build. Serving it to users is up to your host/edge/CDN: fetch the verified artifact in your deploy pipeline with the delivery API (docs/sdk.md) or @stacklift/sdk-core (Node) / @stacklift/sdk-js. No hosting is provided.
  • Svelte — *partial*. Stacklift versions, signs and serves the build. Serving it to users is up to your host/edge/CDN: fetch the verified artifact in your deploy pipeline with the delivery API (docs/sdk.md) or @stacklift/sdk-core (Node) / @stacklift/sdk-js. No hosting is provided.
  • SvelteKit — *partial*. Stacklift versions, signs and serves the build. Serving it to users is up to your host/edge/CDN: fetch the verified artifact in your deploy pipeline with the delivery API (docs/sdk.md) or @stacklift/sdk-core (Node) / @stacklift/sdk-js. No hosting is provided.

Backend

StackMaturityPlatformsBackend deployConfig & assets
node Node.jsalphaserverpartialsupported
python Pythonalphaserverpartialsupported
go Goalphaserverpartialsupported
java Java / JVMalphaserverpartialsupported
dotnet .NETalphaserverpartialsupported

Client runtime (what exists on the device to apply updates):

  • Node.js — *partial*. Stacklift stores signed server bundles or container image references and tracks which release each channel points to. Your CD system (fetching and verifying the artifact through the delivery API or an SDK) performs the actual rollout to servers/orchestrators — Stacklift does not run your infrastructure.
  • Python — *partial*. Stacklift stores signed server bundles or container image references and tracks which release each channel points to. Your CD system (fetching and verifying the artifact through the delivery API or an SDK) performs the actual rollout to servers/orchestrators — Stacklift does not run your infrastructure.
  • Go — *partial*. Stacklift stores signed server bundles or container image references and tracks which release each channel points to. Your CD system (fetching and verifying the artifact through the delivery API or an SDK) performs the actual rollout to servers/orchestrators — Stacklift does not run your infrastructure.
  • Java / JVM — *partial*. Stacklift stores signed server bundles or container image references and tracks which release each channel points to. Your CD system (fetching and verifying the artifact through the delivery API or an SDK) performs the actual rollout to servers/orchestrators — Stacklift does not run your infrastructure.
  • .NET — *partial*. Stacklift stores signed server bundles or container image references and tracks which release each channel points to. Your CD system (fetching and verifying the artifact through the delivery API or an SDK) performs the actual rollout to servers/orchestrators — Stacklift does not run your infrastructure.

<!-- adapters:end -->

Honest limits

  • Native iOS/Android binaries can only ship through the stores. Stacklift tracks them; it cannot update them.
  • iOS (App Store Review Guideline 3.3.2) and Android (Google Play policy) restrict downloaded code to interpreted code that doesn't change the app's primary purpose. Compliance is the developer's responsibility.
  • Desktop apps update by installing a new signed build (desktop-installer). Stacklift delivers and verifies it; your app runs it. OS code signing/notarization is yours, installers can't be rolled back, there are no delta updates, and store builds must update through their store. See Desktop apps.
  • Expo, Capacitor, NativeScript can change their JS/web layer over the air within store rules; the on-device loader that applies it is not shipped (partial).
  • Kotlin Multiplatform and Tauri SDKs are untested source (no Kotlin/Rust toolchain in CI). See SDKs.
  • Flutter Dart OTA is planned: it needs a patched engine and a patch toolchain Stacklift doesn't ship.
  • React Native JS-bundle OTA is partial: control plane, signing, rollout and delivery work; the on-device bundle loader isn't shipped yet.
  • Web and backend stacks use deployments: Stacklift versions, signs and serves artifacts, and repoints a channel. Hosting is yours.

Capability matrix

Generated from the adapter registry — the same data the API serves at GET /api/v1/adapters.

Flutter planned

The Dart SDK (packages/sdk-dart) checks, downloads and verifies config/asset bundles, web builds and desktop installers, and with packages/sdk-flutter-scripts runs signed script bundles (scripted logic updates). Dart code OTA on Android/iOS ("code push") needs a patched Flutter engine and a patch toolchain Stacklift does NOT ship.

MechanismSupportPlatformsSignedRestrictions & limitations
otaplannedandroid, iosyes

Apple App Store Review Guideline 3.3.2 only permits downloaded code that does not change the primary purpose of the app and runs inside the OS-provided interpreter/runtime. You are responsible for compliance.

Google Play policy forbids updating the app by any method other than Google Play, except for interpreted code running in a VM/interpreter. You are responsible for compliance.

Patches only apply to the exact base engine/runtimeVersion they were built against.

Not implemented: needs engine integration and a patch builder. Artifact kind "dart-patch" is accepted for storage and delivery only so future tooling has a stable contract.

web-deploysupportedwebyes

Hosting is bring-your-own; Stacklift versions, signs and serves the bundle.

native-releasepartialandroid, iosn/a

Native binaries ship through Google Play / App Store / TestFlight only.

Stacklift records native releases (version, build, commit) for visibility and compatibility tracking. It does not upload to stores or OTA-update binaries.

desktop-updatepartialwindows, macos, linuxyes

Stacklift verifies its own Ed25519 signature, which is independent of OS code signing. Installers must still be signed (Windows Authenticode; macOS Developer ID plus notarization) or the OS warns or blocks them. That is your responsibility.

Builds distributed through the Mac App Store or Microsoft Store must update through that store. Do not self-update store builds.

Stacklift delivers and verifies the installer. Running it and relaunching the app is done by your application (the SDKs provide the download and verification steps). There are no delta updates and no silent in-place patching.

Installers cannot be rolled back through Stacklift: most OS installers refuse downgrades. Fix forward with a higher version.

script-updatepartialandroid, iosyes

Apple Developer Program License Agreement 3.3.2 allows downloaded interpreted code only if it does not change the primary purpose of the app, does not create a store for other code, and does not bypass signing or the sandbox. Script hooks must stay within the features the reviewed app already has. You are responsible for compliance.

Google Play Device and Network Abuse policy forbids downloading executable code (dex, JAR, .so) from outside Play, except code that runs in a virtual machine or interpreter with only indirect access to Android APIs. Script runtimes must not expose reflection or raw platform objects. You are responsible for compliance.

Scripts run inside an OS-provided JavaScript interpreter and can only call the functions your app registers. They cannot add native features, call platform APIs directly or change compiled code.

Your app must be written with script hooks: functions it calls into the script (pricing rules, feature logic, validation, content ranking). Logic that is not behind a hook cannot be updated.

The runtime that loads, applies on the next launch and rolls back a script ships for Swift (packages/sdk-swift, JavaScriptCore), Dart/Flutter (packages/sdk-dart with packages/sdk-flutter-scripts) and native Android (packages/sdk-android, QuickJS). C# (MAUI, Unity) and other runtimes are not shipped yet.

ui-updatepartialandroid, iosyes

Use layouts to change how features the reviewed app already has look and are arranged, not to add hidden features. Apple App Review Guideline 2.5.2 and Google Play policy forbid downloading code that adds or changes functionality; a layout contains no code, but you remain responsible for not using it to bypass review.

Layouts arrange components the app already ships (text, list, table, card, button, your registered custom components). A new kind of component or a new native capability still needs one store release.

Layouts are plain JSON in an open, documented format (stacklift-ui/1). Every screen keeps a fallback built into the app, so it keeps working if Stacklift is unreachable or removed.

Renderers ship for SwiftUI (packages/sdk-swift), Flutter (packages/sdk-dart + packages/sdk-flutter-ui), Jetpack Compose (packages/sdk-android) and React Native (packages/sdk-react-native). .NET MAUI, Unity and others are not shipped yet.

config-assetspartialandroid, ios, web, windows, macos, linuxyes

Client must fetch and apply JSON/asset bundles itself via the Dart SDK (packages/sdk-dart).

Artifacts: dart-patch (.patch .bin .zip) · web-bundle (.zip .tar.gz .tgz) · native-binary (.apk .aab .ipa) · assets (.zip .json) · desktop-installer (.exe .msi .msix .dmg .pkg .appimage .deb .rpm .zip .tar.gz .tgz) · script-bundle (.js) · ui-layout (.json)

React Native alpha

@stacklift/react-native (packages/sdk-react-native) loads a new JS bundle on the next launch, confirms it, and rolls back to the last good or built-in bundle when a launch never confirms or crashes first. Its native side is the Swift SDK (iOS) and the Android SDK, which verify every bundle (SHA-256 + Ed25519). It also renders server-driven screens. Verified on the iOS simulator, an Android emulator and a physical Android 16 phone; not published to npm yet.

MechanismSupportPlatformsSignedRestrictions & limitations
otapartialandroid, iosyes

Apple App Store Review Guideline 3.3.2 only permits downloaded code that does not change the primary purpose of the app and runs inside the OS-provided interpreter/runtime. You are responsible for compliance.

Google Play policy forbids updating the app by any method other than Google Play, except for interpreted code running in a VM/interpreter. You are responsible for compliance.

Only JavaScript bundles and assets can change. Any native code/module/permission change requires a store release and a new runtimeVersion.

Code push applies to release builds; debug builds load JavaScript from Metro.

Hermes bytecode bundles must be built against the same Hermes version as the binary (encode in runtimeVersion). Plain JavaScript bundles also run on Hermes.

Not published to npm or the CocoaPods trunk yet: use it from the repository (see packages/sdk-react-native/README.md).

ui-updatepartialandroid, iosyes

Use layouts to change how features the reviewed app already has look and are arranged, not to add hidden features. Apple App Review Guideline 2.5.2 and Google Play policy forbid downloading code that adds or changes functionality; a layout contains no code, but you remain responsible for not using it to bypass review.

Layouts arrange components the app already ships (text, list, table, card, button, your registered custom components). A new kind of component or a new native capability still needs one store release.

Layouts are plain JSON in an open, documented format (stacklift-ui/1). Every screen keeps a fallback built into the app, so it keeps working if Stacklift is unreachable or removed.

Renderers ship for SwiftUI (packages/sdk-swift), Flutter (packages/sdk-dart + packages/sdk-flutter-ui), Jetpack Compose (packages/sdk-android) and React Native (packages/sdk-react-native). .NET MAUI, Unity and others are not shipped yet.

native-releasepartialandroid, iosn/a

Native binaries ship through the stores only.

Release tracking only.

config-assetspartialandroid, iosyes

Artifacts: js-bundle (.zip .bundle .hbc .tar.gz) · assets (.zip) · native-binary (.apk .aab .ipa) · ui-layout (.json)

Expo alpha

@stacklift/sdk-js performs check → download → verification in JS. Activating the bundle needs a native loader or an implementation of the Expo Updates protocol; Stacklift ships neither, so Expo apps do not use expo-updates against Stacklift yet.

MechanismSupportPlatformsSignedRestrictions & limitations
otapartialandroid, iosyes

Apple App Store Review Guideline 3.3.2 only permits downloaded code that does not change the primary purpose of the app and runs inside the OS-provided interpreter/runtime. You are responsible for compliance.

Google Play policy forbids updating the app by any method other than Google Play, except for interpreted code running in a VM/interpreter. You are responsible for compliance.

Changing native modules, permissions or the Expo SDK version needs a store build and a new runtimeVersion.

Control plane, signing, staged rollout and delivery are implemented, and @stacklift/sdk-js verifies the download. The on-device bundle loader and the Expo Updates protocol are not implemented.

native-releasepartialandroid, iosn/a

Native binaries ship through the stores only.

Release tracking only.

config-assetspartialandroid, iosyes

Artifacts: js-bundle (.zip .tar.gz .tgz) · assets (.zip) · native-binary (.apk .aab .ipa)

Android (Kotlin) alpha

Binaries are distributed by the platform store. Remote config/asset bundles can be fetched and verified with the Android SDK (packages/sdk-android: Compose screens, QuickJS scripts, update lifecycle; built on the Java SDK in packages/sdk-java; tested on an Android 17 emulator and a physical Android 16 phone; Ed25519 needs Android API 33+, or register BouncyCastle/Conscrypt).

MechanismSupportPlatformsSignedRestrictions & limitations
native-releasepartialandroidn/a

Google Play policy forbids updating the app by any method other than Google Play, except for interpreted code running in a VM/interpreter. You are responsible for compliance.

Stacklift tracks versions, builds and metadata. It does NOT upload to the store or OTA-update the binary.

otaunsupportedandroidn/a

Google Play policy forbids updating the app by any method other than Google Play, except for interpreted code running in a VM/interpreter. You are responsible for compliance.

Replacing native executable code outside the store is not possible/permitted and is never offered.

script-updatepartialandroidyes

Apple Developer Program License Agreement 3.3.2 allows downloaded interpreted code only if it does not change the primary purpose of the app, does not create a store for other code, and does not bypass signing or the sandbox. Script hooks must stay within the features the reviewed app already has. You are responsible for compliance.

Google Play Device and Network Abuse policy forbids downloading executable code (dex, JAR, .so) from outside Play, except code that runs in a virtual machine or interpreter with only indirect access to Android APIs. Script runtimes must not expose reflection or raw platform objects. You are responsible for compliance.

Scripts run inside an OS-provided JavaScript interpreter and can only call the functions your app registers. They cannot add native features, call platform APIs directly or change compiled code.

Your app must be written with script hooks: functions it calls into the script (pricing rules, feature logic, validation, content ranking). Logic that is not behind a hook cannot be updated.

The runtime that loads, applies on the next launch and rolls back a script ships for Swift (packages/sdk-swift, JavaScriptCore), Dart/Flutter (packages/sdk-dart with packages/sdk-flutter-scripts) and native Android (packages/sdk-android, QuickJS). C# (MAUI, Unity) and other runtimes are not shipped yet.

ui-updatepartialandroidyes

Use layouts to change how features the reviewed app already has look and are arranged, not to add hidden features. Apple App Review Guideline 2.5.2 and Google Play policy forbid downloading code that adds or changes functionality; a layout contains no code, but you remain responsible for not using it to bypass review.

Layouts arrange components the app already ships (text, list, table, card, button, your registered custom components). A new kind of component or a new native capability still needs one store release.

Layouts are plain JSON in an open, documented format (stacklift-ui/1). Every screen keeps a fallback built into the app, so it keeps working if Stacklift is unreachable or removed.

Renderers ship for SwiftUI (packages/sdk-swift), Flutter (packages/sdk-dart + packages/sdk-flutter-ui), Jetpack Compose (packages/sdk-android) and React Native (packages/sdk-react-native). .NET MAUI, Unity and others are not shipped yet.

config-assetspartialandroidyes

Non-executable JSON/asset bundles only.

Artifacts: native-binary (.apk .aab) · script-bundle (.js) · ui-layout (.json) · config (.json) · assets (.zip)

iOS (Swift) alpha

Binaries are distributed by the platform store. Remote config/asset bundles can be fetched and verified with the Swift package (packages/sdk-swift, tested with swift test on macOS).

MechanismSupportPlatformsSignedRestrictions & limitations
native-releasepartialiosn/a

Apple App Store Review Guideline 3.3.2 only permits downloaded code that does not change the primary purpose of the app and runs inside the OS-provided interpreter/runtime. You are responsible for compliance.

Stacklift tracks versions, builds and metadata. It does NOT upload to the store or OTA-update the binary.

otaunsupportediosn/a

Apple App Store Review Guideline 3.3.2 only permits downloaded code that does not change the primary purpose of the app and runs inside the OS-provided interpreter/runtime. You are responsible for compliance.

Replacing native executable code outside the store is not possible/permitted and is never offered.

script-updatepartialiosyes

Apple Developer Program License Agreement 3.3.2 allows downloaded interpreted code only if it does not change the primary purpose of the app, does not create a store for other code, and does not bypass signing or the sandbox. Script hooks must stay within the features the reviewed app already has. You are responsible for compliance.

Google Play Device and Network Abuse policy forbids downloading executable code (dex, JAR, .so) from outside Play, except code that runs in a virtual machine or interpreter with only indirect access to Android APIs. Script runtimes must not expose reflection or raw platform objects. You are responsible for compliance.

Scripts run inside an OS-provided JavaScript interpreter and can only call the functions your app registers. They cannot add native features, call platform APIs directly or change compiled code.

Your app must be written with script hooks: functions it calls into the script (pricing rules, feature logic, validation, content ranking). Logic that is not behind a hook cannot be updated.

The runtime that loads, applies on the next launch and rolls back a script ships for Swift (packages/sdk-swift, JavaScriptCore), Dart/Flutter (packages/sdk-dart with packages/sdk-flutter-scripts) and native Android (packages/sdk-android, QuickJS). C# (MAUI, Unity) and other runtimes are not shipped yet.

ui-updatepartialiosyes

Use layouts to change how features the reviewed app already has look and are arranged, not to add hidden features. Apple App Review Guideline 2.5.2 and Google Play policy forbid downloading code that adds or changes functionality; a layout contains no code, but you remain responsible for not using it to bypass review.

Layouts arrange components the app already ships (text, list, table, card, button, your registered custom components). A new kind of component or a new native capability still needs one store release.

Layouts are plain JSON in an open, documented format (stacklift-ui/1). Every screen keeps a fallback built into the app, so it keeps working if Stacklift is unreachable or removed.

Renderers ship for SwiftUI (packages/sdk-swift), Flutter (packages/sdk-dart + packages/sdk-flutter-ui), Jetpack Compose (packages/sdk-android) and React Native (packages/sdk-react-native). .NET MAUI, Unity and others are not shipped yet.

config-assetspartialiosyes

Non-executable JSON/asset bundles only.

Artifacts: native-binary (.ipa) · script-bundle (.js) · ui-layout (.json) · config (.json) · assets (.zip)

Kotlin Multiplatform / Compose Multiplatform alpha

On Android and JVM desktop use the Java SDK (packages/sdk-java, tested on JDK 21). packages/sdk-kotlin is a coroutine wrapper over it for androidMain/jvmMain; it has NOT been compiled or tested (no Kotlin toolchain in Stacklift CI yet). There is no Kotlin iOS implementation: call the Swift package (packages/sdk-swift) from iOS code.

MechanismSupportPlatformsSignedRestrictions & limitations
native-releasepartialandroid, iosn/a

Native mobile binaries ship through the stores only.

Stacklift tracks versions and builds. It does NOT upload to the stores or OTA-update binaries.

otaunsupportedandroid, iosn/a

Apple App Store Review Guideline 3.3.2 only permits downloaded code that does not change the primary purpose of the app and runs inside the OS-provided interpreter/runtime. You are responsible for compliance.

Google Play policy forbids updating the app by any method other than Google Play, except for interpreted code running in a VM/interpreter. You are responsible for compliance.

Replacing compiled native code outside the store is not possible/permitted and is never offered.

script-updatepartialandroid, iosyes

Apple Developer Program License Agreement 3.3.2 allows downloaded interpreted code only if it does not change the primary purpose of the app, does not create a store for other code, and does not bypass signing or the sandbox. Script hooks must stay within the features the reviewed app already has. You are responsible for compliance.

Google Play Device and Network Abuse policy forbids downloading executable code (dex, JAR, .so) from outside Play, except code that runs in a virtual machine or interpreter with only indirect access to Android APIs. Script runtimes must not expose reflection or raw platform objects. You are responsible for compliance.

Scripts run inside an OS-provided JavaScript interpreter and can only call the functions your app registers. They cannot add native features, call platform APIs directly or change compiled code.

Your app must be written with script hooks: functions it calls into the script (pricing rules, feature logic, validation, content ranking). Logic that is not behind a hook cannot be updated.

The runtime that loads, applies on the next launch and rolls back a script ships for Swift (packages/sdk-swift, JavaScriptCore), Dart/Flutter (packages/sdk-dart with packages/sdk-flutter-scripts) and native Android (packages/sdk-android, QuickJS). C# (MAUI, Unity) and other runtimes are not shipped yet.

ui-updatepartialandroid, iosyes

Use layouts to change how features the reviewed app already has look and are arranged, not to add hidden features. Apple App Review Guideline 2.5.2 and Google Play policy forbid downloading code that adds or changes functionality; a layout contains no code, but you remain responsible for not using it to bypass review.

Layouts arrange components the app already ships (text, list, table, card, button, your registered custom components). A new kind of component or a new native capability still needs one store release.

Layouts are plain JSON in an open, documented format (stacklift-ui/1). Every screen keeps a fallback built into the app, so it keeps working if Stacklift is unreachable or removed.

Renderers ship for SwiftUI (packages/sdk-swift), Flutter (packages/sdk-dart + packages/sdk-flutter-ui), Jetpack Compose (packages/sdk-android) and React Native (packages/sdk-react-native). .NET MAUI, Unity and others are not shipped yet.

desktop-updatepartialwindows, macos, linuxyes

Stacklift verifies its own Ed25519 signature, which is independent of OS code signing. Installers must still be signed (Windows Authenticode; macOS Developer ID plus notarization) or the OS warns or blocks them. That is your responsibility.

Builds distributed through the Mac App Store or Microsoft Store must update through that store. Do not self-update store builds.

Stacklift delivers and verifies the installer. Running it and relaunching the app is done by your application (the SDKs provide the download and verification steps). There are no delta updates and no silent in-place patching.

Installers cannot be rolled back through Stacklift: most OS installers refuse downgrades. Fix forward with a higher version.

config-assetspartialandroid, ios, windows, macos, linuxyes

Non-executable JSON/asset bundles only, fetched and applied by the app through the SDK.

Artifacts: native-binary (.apk .aab .ipa) · desktop-installer (.exe .msi .msix .dmg .pkg .appimage .deb .rpm .zip .tar.gz .tgz) · script-bundle (.js) · ui-layout (.json) · config (.json) · assets (.zip)

Capacitor / Ionic alpha

@stacklift/sdk-js checks, downloads and verifies the web bundle. Unpacking it and pointing the WebView at it needs a native Capacitor plugin that Stacklift does not ship yet.

MechanismSupportPlatformsSignedRestrictions & limitations
otapartialandroid, ios, webyes

Apple App Store Review Guideline 3.3.2 only permits downloaded code that does not change the primary purpose of the app and runs inside the OS-provided interpreter/runtime. You are responsible for compliance.

Google Play policy forbids updating the app by any method other than Google Play, except for interpreted code running in a VM/interpreter. You are responsible for compliance.

Only web-layer assets (HTML/JS/CSS) can change. New or updated native plugins, permissions or Capacitor versions require a store build and a new runtimeVersion.

Control plane, signing, staged rollout and delivery are implemented, and @stacklift/sdk-js verifies the download. The native plugin that swaps the WebView content is not implemented.

native-releasepartialandroid, ios, webn/a

Native binaries ship through the stores only.

Release tracking only.

config-assetspartialandroid, ios, webyes

Artifacts: web-bundle (.zip .tar.gz .tgz) · assets (.zip) · native-binary (.apk .aab .ipa)

NativeScript alpha

@stacklift/sdk-js checks, downloads and verifies the bundle. Activating it on-device is not implemented.

MechanismSupportPlatformsSignedRestrictions & limitations
otapartialandroid, iosyes

Apple App Store Review Guideline 3.3.2 only permits downloaded code that does not change the primary purpose of the app and runs inside the OS-provided interpreter/runtime. You are responsible for compliance.

Google Play policy forbids updating the app by any method other than Google Play, except for interpreted code running in a VM/interpreter. You are responsible for compliance.

Native plugin or runtime changes need a store build and a new runtimeVersion.

Control plane, signing, staged rollout and delivery are implemented, and @stacklift/sdk-js verifies the download. The on-device bundle loader is not implemented.

native-releasepartialandroid, iosn/a

Native binaries ship through the stores only.

Release tracking only.

config-assetspartialandroid, iosyes

Artifacts: js-bundle (.zip .tar.gz .tgz) · assets (.zip) · native-binary (.apk .aab .ipa)

.NET MAUI alpha

Stacklift.Sdk (netstandard2.0, tested on .NET 10) checks, downloads and verifies. MAUI platform projects were not built here.

MechanismSupportPlatformsSignedRestrictions & limitations
native-releasepartialandroid, iosn/a

Native mobile binaries ship through the stores only.

Stacklift tracks versions and builds. It does NOT upload to the stores or OTA-update binaries.

otaunsupportedandroid, iosn/a

Apple App Store Review Guideline 3.3.2 only permits downloaded code that does not change the primary purpose of the app and runs inside the OS-provided interpreter/runtime. You are responsible for compliance.

Google Play policy forbids updating the app by any method other than Google Play, except for interpreted code running in a VM/interpreter. You are responsible for compliance.

Replacing compiled native code outside the store is not possible/permitted and is never offered.

script-updatepartialandroid, iosyes

Apple Developer Program License Agreement 3.3.2 allows downloaded interpreted code only if it does not change the primary purpose of the app, does not create a store for other code, and does not bypass signing or the sandbox. Script hooks must stay within the features the reviewed app already has. You are responsible for compliance.

Google Play Device and Network Abuse policy forbids downloading executable code (dex, JAR, .so) from outside Play, except code that runs in a virtual machine or interpreter with only indirect access to Android APIs. Script runtimes must not expose reflection or raw platform objects. You are responsible for compliance.

Scripts run inside an OS-provided JavaScript interpreter and can only call the functions your app registers. They cannot add native features, call platform APIs directly or change compiled code.

Your app must be written with script hooks: functions it calls into the script (pricing rules, feature logic, validation, content ranking). Logic that is not behind a hook cannot be updated.

The runtime that loads, applies on the next launch and rolls back a script ships for Swift (packages/sdk-swift, JavaScriptCore), Dart/Flutter (packages/sdk-dart with packages/sdk-flutter-scripts) and native Android (packages/sdk-android, QuickJS). C# (MAUI, Unity) and other runtimes are not shipped yet.

ui-updatepartialandroid, iosyes

Use layouts to change how features the reviewed app already has look and are arranged, not to add hidden features. Apple App Review Guideline 2.5.2 and Google Play policy forbid downloading code that adds or changes functionality; a layout contains no code, but you remain responsible for not using it to bypass review.

Layouts arrange components the app already ships (text, list, table, card, button, your registered custom components). A new kind of component or a new native capability still needs one store release.

Layouts are plain JSON in an open, documented format (stacklift-ui/1). Every screen keeps a fallback built into the app, so it keeps working if Stacklift is unreachable or removed.

Renderers ship for SwiftUI (packages/sdk-swift), Flutter (packages/sdk-dart + packages/sdk-flutter-ui), Jetpack Compose (packages/sdk-android) and React Native (packages/sdk-react-native). .NET MAUI, Unity and others are not shipped yet.

desktop-updatepartialwindows, macosyes

Stacklift verifies its own Ed25519 signature, which is independent of OS code signing. Installers must still be signed (Windows Authenticode; macOS Developer ID plus notarization) or the OS warns or blocks them. That is your responsibility.

Builds distributed through the Mac App Store or Microsoft Store must update through that store. Do not self-update store builds.

Stacklift delivers and verifies the installer. Running it and relaunching the app is done by your application (the SDKs provide the download and verification steps). There are no delta updates and no silent in-place patching.

Installers cannot be rolled back through Stacklift: most OS installers refuse downgrades. Fix forward with a higher version.

config-assetspartialandroid, ios, windows, macosyes

Non-executable JSON/asset bundles only, fetched and applied by the app through the SDK.

Artifacts: native-binary (.apk .aab .ipa) · desktop-installer (.exe .msi .msix .dmg .pkg .appimage .deb .rpm .zip .tar.gz .tgz) · script-bundle (.js) · ui-layout (.json) · config (.json) · assets (.zip)

Unity alpha

Stacklift.Sdk (netstandard2.0) can be used from Unity for check, download and verification; it needs the BouncyCastle assembly. Not run inside Unity here. Stacklift does not implement the Addressables remote-catalog protocol.

MechanismSupportPlatformsSignedRestrictions & limitations
native-releasepartialandroid, iosn/a

Native mobile binaries ship through the stores only.

Stacklift tracks versions and builds. It does NOT upload to the stores or OTA-update binaries.

otaunsupportedandroid, iosn/a

Apple App Store Review Guideline 3.3.2 only permits downloaded code that does not change the primary purpose of the app and runs inside the OS-provided interpreter/runtime. You are responsible for compliance.

Google Play policy forbids updating the app by any method other than Google Play, except for interpreted code running in a VM/interpreter. You are responsible for compliance.

Replacing compiled native code outside the store is not possible/permitted and is never offered.

script-updatepartialandroid, iosyes

Apple Developer Program License Agreement 3.3.2 allows downloaded interpreted code only if it does not change the primary purpose of the app, does not create a store for other code, and does not bypass signing or the sandbox. Script hooks must stay within the features the reviewed app already has. You are responsible for compliance.

Google Play Device and Network Abuse policy forbids downloading executable code (dex, JAR, .so) from outside Play, except code that runs in a virtual machine or interpreter with only indirect access to Android APIs. Script runtimes must not expose reflection or raw platform objects. You are responsible for compliance.

Scripts run inside an OS-provided JavaScript interpreter and can only call the functions your app registers. They cannot add native features, call platform APIs directly or change compiled code.

Your app must be written with script hooks: functions it calls into the script (pricing rules, feature logic, validation, content ranking). Logic that is not behind a hook cannot be updated.

The runtime that loads, applies on the next launch and rolls back a script ships for Swift (packages/sdk-swift, JavaScriptCore), Dart/Flutter (packages/sdk-dart with packages/sdk-flutter-scripts) and native Android (packages/sdk-android, QuickJS). C# (MAUI, Unity) and other runtimes are not shipped yet.

ui-updatepartialandroid, iosyes

Use layouts to change how features the reviewed app already has look and are arranged, not to add hidden features. Apple App Review Guideline 2.5.2 and Google Play policy forbid downloading code that adds or changes functionality; a layout contains no code, but you remain responsible for not using it to bypass review.

Layouts arrange components the app already ships (text, list, table, card, button, your registered custom components). A new kind of component or a new native capability still needs one store release.

Layouts are plain JSON in an open, documented format (stacklift-ui/1). Every screen keeps a fallback built into the app, so it keeps working if Stacklift is unreachable or removed.

Renderers ship for SwiftUI (packages/sdk-swift), Flutter (packages/sdk-dart + packages/sdk-flutter-ui), Jetpack Compose (packages/sdk-android) and React Native (packages/sdk-react-native). .NET MAUI, Unity and others are not shipped yet.

desktop-updatepartialwindows, macos, linuxyes

Stacklift verifies its own Ed25519 signature, which is independent of OS code signing. Installers must still be signed (Windows Authenticode; macOS Developer ID plus notarization) or the OS warns or blocks them. That is your responsibility.

Builds distributed through the Mac App Store or Microsoft Store must update through that store. Do not self-update store builds.

Stacklift delivers and verifies the installer. Running it and relaunching the app is done by your application (the SDKs provide the download and verification steps). There are no delta updates and no silent in-place patching.

Installers cannot be rolled back through Stacklift: most OS installers refuse downgrades. Fix forward with a higher version.

config-assetspartialandroid, ios, windows, macos, linuxyes

Non-executable JSON/asset bundles only, fetched and applied by the app through the SDK.

Artifacts: native-binary (.apk .aab .ipa) · desktop-installer (.exe .msi .msix .dmg .pkg .appimage .deb .rpm .zip .tar.gz .tgz) · script-bundle (.js) · ui-layout (.json) · config (.json) · assets (.zip)

Electron alpha

@stacklift/sdk-electron checks, downloads and verifies the installer in the main process and hands it to the OS. It is unit-tested with fakes for the Electron APIs, not inside a running Electron app. No in-place asar patching.

MechanismSupportPlatformsSignedRestrictions & limitations
desktop-updatepartialwindows, macos, linuxyes

Stacklift verifies its own Ed25519 signature, which is independent of OS code signing. Installers must still be signed (Windows Authenticode; macOS Developer ID plus notarization) or the OS warns or blocks them. That is your responsibility.

Builds distributed through the Mac App Store or Microsoft Store must update through that store. Do not self-update store builds.

Stacklift delivers and verifies the installer. Running it and relaunching the app is done by your application (the SDKs provide the download and verification steps). There are no delta updates and no silent in-place patching.

Installers cannot be rolled back through Stacklift: most OS installers refuse downgrades. Fix forward with a higher version.

otaplannedwindows, macos, linuxyes

Swapping app.asar / renderer assets without a new installer is not implemented (it also interacts with ASAR integrity fuses and macOS code-signature validity).

native-releasepartialwindows, macos, linuxn/a

Builds distributed through the Mac App Store or Microsoft Store must update through that store. Do not self-update store builds.

For builds you distribute elsewhere (store packages, your own website). Stacklift records version/build metadata only; it neither hosts nor delivers them.

config-assetspartialwindows, macos, linuxyes

Non-executable JSON/asset bundles only. The app fetches and applies them itself through the SDK.

Artifacts: desktop-installer (.exe .msi .msix .dmg .pkg .appimage .deb .rpm .zip .tar.gz .tgz) · native-binary (.msix .pkg .exe .dmg .appimage .deb .rpm) · config (.json) · assets (.zip)

Tauri planned

A Rust plugin is provided as source in packages/sdk-tauri. It has NOT been compiled or tested (no Rust toolchain in Stacklift CI yet). From the web frontend you can use @stacklift/sdk-js for check and verification.

MechanismSupportPlatformsSignedRestrictions & limitations
desktop-updatepartialwindows, macos, linuxyes

Stacklift verifies its own Ed25519 signature, which is independent of OS code signing. Installers must still be signed (Windows Authenticode; macOS Developer ID plus notarization) or the OS warns or blocks them. That is your responsibility.

Builds distributed through the Mac App Store or Microsoft Store must update through that store. Do not self-update store builds.

Stacklift delivers and verifies the installer. Running it and relaunching the app is done by your application (the SDKs provide the download and verification steps). There are no delta updates and no silent in-place patching.

Installers cannot be rolled back through Stacklift: most OS installers refuse downgrades. Fix forward with a higher version.

otaplannedwindows, macos, linuxyes

Swapping the web frontend without a new installer is not implemented.

native-releasepartialwindows, macos, linuxn/a

Builds distributed through the Mac App Store or Microsoft Store must update through that store. Do not self-update store builds.

For builds you distribute elsewhere (store packages, your own website). Stacklift records version/build metadata only; it neither hosts nor delivers them.

config-assetspartialwindows, macos, linuxyes

Non-executable JSON/asset bundles only. The app fetches and applies them itself through the SDK.

Artifacts: desktop-installer (.exe .msi .msix .dmg .pkg .appimage .deb .rpm .zip .tar.gz .tgz) · native-binary (.msix .pkg .exe .dmg .appimage .deb .rpm) · config (.json) · assets (.zip)

.NET desktop (WPF / WinForms / WinUI) alpha

Stacklift.Sdk (netstandard2.0, tested on .NET 10) checks, downloads and verifies. Launching the MSI/MSIX/EXE is done by your app.

MechanismSupportPlatformsSignedRestrictions & limitations
desktop-updatepartialwindowsyes

Stacklift verifies its own Ed25519 signature, which is independent of OS code signing. Installers must still be signed (Windows Authenticode; macOS Developer ID plus notarization) or the OS warns or blocks them. That is your responsibility.

Builds distributed through the Mac App Store or Microsoft Store must update through that store. Do not self-update store builds.

Stacklift delivers and verifies the installer. Running it and relaunching the app is done by your application (the SDKs provide the download and verification steps). There are no delta updates and no silent in-place patching.

Installers cannot be rolled back through Stacklift: most OS installers refuse downgrades. Fix forward with a higher version.

otaunsupportedwindowsn/a

Compiled code is replaced by installing a new build — use desktop-update instead. In-place patching of a running binary is never offered.

native-releasepartialwindowsn/a

Builds distributed through the Mac App Store or Microsoft Store must update through that store. Do not self-update store builds.

For builds you distribute elsewhere (store packages, your own website). Stacklift records version/build metadata only; it neither hosts nor delivers them.

config-assetspartialwindowsyes

Non-executable JSON/asset bundles only. The app fetches and applies them itself through the SDK.

Artifacts: desktop-installer (.exe .msi .msix .dmg .pkg .appimage .deb .rpm .zip .tar.gz .tgz) · native-binary (.msix .pkg .exe .dmg .appimage .deb .rpm) · config (.json) · assets (.zip)

macOS (Swift / AppKit) alpha

The Stacklift Swift package (CryptoKit, tested with swift test on macOS) checks, downloads and verifies. Opening the DMG/PKG is done by your app. Sparkle can still be used for the install step.

MechanismSupportPlatformsSignedRestrictions & limitations
desktop-updatepartialmacosyes

Stacklift verifies its own Ed25519 signature, which is independent of OS code signing. Installers must still be signed (Windows Authenticode; macOS Developer ID plus notarization) or the OS warns or blocks them. That is your responsibility.

Builds distributed through the Mac App Store or Microsoft Store must update through that store. Do not self-update store builds.

Stacklift delivers and verifies the installer. Running it and relaunching the app is done by your application (the SDKs provide the download and verification steps). There are no delta updates and no silent in-place patching.

Installers cannot be rolled back through Stacklift: most OS installers refuse downgrades. Fix forward with a higher version.

otaunsupportedmacosn/a

Compiled code is replaced by installing a new build — use desktop-update instead. In-place patching of a running binary is never offered.

native-releasepartialmacosn/a

Builds distributed through the Mac App Store or Microsoft Store must update through that store. Do not self-update store builds.

For builds you distribute elsewhere (store packages, your own website). Stacklift records version/build metadata only; it neither hosts nor delivers them.

config-assetspartialmacosyes

Non-executable JSON/asset bundles only. The app fetches and applies them itself through the SDK.

Artifacts: desktop-installer (.exe .msi .msix .dmg .pkg .appimage .deb .rpm .zip .tar.gz .tgz) · native-binary (.msix .pkg .exe .dmg .appimage .deb .rpm) · config (.json) · assets (.zip)

JVM desktop (JavaFX / Compose / Swing) alpha

The Java SDK (JDK 17+, no dependencies, tested on JDK 21) checks, downloads and verifies. Running the installer is done by your app.

MechanismSupportPlatformsSignedRestrictions & limitations
desktop-updatepartialwindows, macos, linuxyes

Stacklift verifies its own Ed25519 signature, which is independent of OS code signing. Installers must still be signed (Windows Authenticode; macOS Developer ID plus notarization) or the OS warns or blocks them. That is your responsibility.

Builds distributed through the Mac App Store or Microsoft Store must update through that store. Do not self-update store builds.

Stacklift delivers and verifies the installer. Running it and relaunching the app is done by your application (the SDKs provide the download and verification steps). There are no delta updates and no silent in-place patching.

Installers cannot be rolled back through Stacklift: most OS installers refuse downgrades. Fix forward with a higher version.

otaunsupportedwindows, macos, linuxn/a

Compiled code is replaced by installing a new build — use desktop-update instead. In-place patching of a running binary is never offered.

native-releasepartialwindows, macos, linuxn/a

Builds distributed through the Mac App Store or Microsoft Store must update through that store. Do not self-update store builds.

For builds you distribute elsewhere (store packages, your own website). Stacklift records version/build metadata only; it neither hosts nor delivers them.

config-assetspartialwindows, macos, linuxyes

Non-executable JSON/asset bundles only. The app fetches and applies them itself through the SDK.

Artifacts: desktop-installer (.exe .msi .msix .dmg .pkg .appimage .deb .rpm .zip .tar.gz .tgz) · native-binary (.msix .pkg .exe .dmg .appimage .deb .rpm) · config (.json) · assets (.zip)

Qt / C++ alpha

No C++ SDK is shipped. The delivery API is plain HTTPS + JSON and the signature is Ed25519 over a documented text payload, so any language can verify it (see docs/sdk.md).

MechanismSupportPlatformsSignedRestrictions & limitations
desktop-updatepartialwindows, macos, linuxyes

Stacklift verifies its own Ed25519 signature, which is independent of OS code signing. Installers must still be signed (Windows Authenticode; macOS Developer ID plus notarization) or the OS warns or blocks them. That is your responsibility.

Builds distributed through the Mac App Store or Microsoft Store must update through that store. Do not self-update store builds.

Stacklift delivers and verifies the installer. Running it and relaunching the app is done by your application (the SDKs provide the download and verification steps). There are no delta updates and no silent in-place patching.

Installers cannot be rolled back through Stacklift: most OS installers refuse downgrades. Fix forward with a higher version.

otaunsupportedwindows, macos, linuxn/a

Compiled code is replaced by installing a new build — use desktop-update instead. In-place patching of a running binary is never offered.

native-releasepartialwindows, macos, linuxn/a

Builds distributed through the Mac App Store or Microsoft Store must update through that store. Do not self-update store builds.

For builds you distribute elsewhere (store packages, your own website). Stacklift records version/build metadata only; it neither hosts nor delivers them.

config-assetspartialwindows, macos, linuxyes

Non-executable JSON/asset bundles only. The app fetches and applies them itself through the SDK.

Artifacts: desktop-installer (.exe .msi .msix .dmg .pkg .appimage .deb .rpm .zip .tar.gz .tgz) · native-binary (.msix .pkg .exe .dmg .appimage .deb .rpm) · config (.json) · assets (.zip)

Other native desktop alpha

Choose this for any toolkit without its own adapter (GTK, wxWidgets, Win32, Go, Rust ...). No client SDK is shipped for it; the HTTP API and signature format are documented in docs/sdk.md.

MechanismSupportPlatformsSignedRestrictions & limitations
desktop-updatepartialwindows, macos, linuxyes

Stacklift verifies its own Ed25519 signature, which is independent of OS code signing. Installers must still be signed (Windows Authenticode; macOS Developer ID plus notarization) or the OS warns or blocks them. That is your responsibility.

Builds distributed through the Mac App Store or Microsoft Store must update through that store. Do not self-update store builds.

Stacklift delivers and verifies the installer. Running it and relaunching the app is done by your application (the SDKs provide the download and verification steps). There are no delta updates and no silent in-place patching.

Installers cannot be rolled back through Stacklift: most OS installers refuse downgrades. Fix forward with a higher version.

otaunsupportedwindows, macos, linuxn/a

Compiled code is replaced by installing a new build — use desktop-update instead. In-place patching of a running binary is never offered.

native-releasepartialwindows, macos, linuxn/a

Builds distributed through the Mac App Store or Microsoft Store must update through that store. Do not self-update store builds.

For builds you distribute elsewhere (store packages, your own website). Stacklift records version/build metadata only; it neither hosts nor delivers them.

config-assetspartialwindows, macos, linuxyes

Non-executable JSON/asset bundles only. The app fetches and applies them itself through the SDK.

Artifacts: desktop-installer (.exe .msi .msix .dmg .pkg .appimage .deb .rpm .zip .tar.gz .tgz) · native-binary (.msix .pkg .exe .dmg .appimage .deb .rpm) · config (.json) · assets (.zip)

React (SPA) beta

Stacklift versions, signs and serves the build. Serving it to users is up to your host/edge/CDN: fetch the verified artifact in your deploy pipeline with the delivery API (docs/sdk.md) or @stacklift/sdk-core (Node) / @stacklift/sdk-js. No hosting is provided.

MechanismSupportPlatformsSignedRestrictions & limitations
web-deploysupportedwebyes

Deployment = atomically repointing a channel to a verified bundle. Stacklift does not host or serve your site.

config-assetssupportedwebyes
otaunsupportedwebn/a

Not applicable: web apps are deployed, not patched on-device.

native-releaseunsupportedwebn/a

Artifacts: web-bundle (.zip .tar.gz .tgz) · assets (.zip .tar.gz) · config (.json)

Next.js alpha

Stacklift versions, signs and serves the build. Serving it to users is up to your host/edge/CDN: fetch the verified artifact in your deploy pipeline with the delivery API (docs/sdk.md) or @stacklift/sdk-core (Node) / @stacklift/sdk-js. No hosting is provided.

MechanismSupportPlatformsSignedRestrictions & limitations
web-deploysupportedwebyes

Deployment = atomically repointing a channel to a verified bundle. Stacklift does not host or serve your site.

Static export is a web-bundle. SSR apps should be released through the Node adapter (server-bundle / container reference).

config-assetssupportedwebyes
otaunsupportedwebn/a

Not applicable: web apps are deployed, not patched on-device.

native-releaseunsupportedwebn/a

Artifacts: web-bundle (.zip .tar.gz .tgz) · assets (.zip .tar.gz) · config (.json)

Vue alpha

Stacklift versions, signs and serves the build. Serving it to users is up to your host/edge/CDN: fetch the verified artifact in your deploy pipeline with the delivery API (docs/sdk.md) or @stacklift/sdk-core (Node) / @stacklift/sdk-js. No hosting is provided.

MechanismSupportPlatformsSignedRestrictions & limitations
web-deploysupportedwebyes

Deployment = atomically repointing a channel to a verified bundle. Stacklift does not host or serve your site.

config-assetssupportedwebyes
otaunsupportedwebn/a

Not applicable: web apps are deployed, not patched on-device.

native-releaseunsupportedwebn/a

Artifacts: web-bundle (.zip .tar.gz .tgz) · assets (.zip .tar.gz) · config (.json)

Nuxt alpha

Stacklift versions, signs and serves the build. Serving it to users is up to your host/edge/CDN: fetch the verified artifact in your deploy pipeline with the delivery API (docs/sdk.md) or @stacklift/sdk-core (Node) / @stacklift/sdk-js. No hosting is provided.

MechanismSupportPlatformsSignedRestrictions & limitations
web-deploysupportedwebyes

Deployment = atomically repointing a channel to a verified bundle. Stacklift does not host or serve your site.

config-assetssupportedwebyes
otaunsupportedwebn/a

Not applicable: web apps are deployed, not patched on-device.

native-releaseunsupportedwebn/a

Artifacts: web-bundle (.zip .tar.gz .tgz) · assets (.zip .tar.gz) · config (.json)

Angular alpha

Stacklift versions, signs and serves the build. Serving it to users is up to your host/edge/CDN: fetch the verified artifact in your deploy pipeline with the delivery API (docs/sdk.md) or @stacklift/sdk-core (Node) / @stacklift/sdk-js. No hosting is provided.

MechanismSupportPlatformsSignedRestrictions & limitations
web-deploysupportedwebyes

Deployment = atomically repointing a channel to a verified bundle. Stacklift does not host or serve your site.

config-assetssupportedwebyes
otaunsupportedwebn/a

Not applicable: web apps are deployed, not patched on-device.

native-releaseunsupportedwebn/a

Artifacts: web-bundle (.zip .tar.gz .tgz) · assets (.zip .tar.gz) · config (.json)

Svelte alpha

Stacklift versions, signs and serves the build. Serving it to users is up to your host/edge/CDN: fetch the verified artifact in your deploy pipeline with the delivery API (docs/sdk.md) or @stacklift/sdk-core (Node) / @stacklift/sdk-js. No hosting is provided.

MechanismSupportPlatformsSignedRestrictions & limitations
web-deploysupportedwebyes

Deployment = atomically repointing a channel to a verified bundle. Stacklift does not host or serve your site.

config-assetssupportedwebyes
otaunsupportedwebn/a

Not applicable: web apps are deployed, not patched on-device.

native-releaseunsupportedwebn/a

Artifacts: web-bundle (.zip .tar.gz .tgz) · assets (.zip .tar.gz) · config (.json)

SvelteKit alpha

Stacklift versions, signs and serves the build. Serving it to users is up to your host/edge/CDN: fetch the verified artifact in your deploy pipeline with the delivery API (docs/sdk.md) or @stacklift/sdk-core (Node) / @stacklift/sdk-js. No hosting is provided.

MechanismSupportPlatformsSignedRestrictions & limitations
web-deploysupportedwebyes

Deployment = atomically repointing a channel to a verified bundle. Stacklift does not host or serve your site.

config-assetssupportedwebyes
otaunsupportedwebn/a

Not applicable: web apps are deployed, not patched on-device.

native-releaseunsupportedwebn/a

Artifacts: web-bundle (.zip .tar.gz .tgz) · assets (.zip .tar.gz) · config (.json)

Node.js alpha

Stacklift stores signed server bundles or container image references and tracks which release each channel points to. Your CD system (fetching and verifying the artifact through the delivery API or an SDK) performs the actual rollout to servers/orchestrators — Stacklift does not run your infrastructure.

MechanismSupportPlatformsSignedRestrictions & limitations
backend-deploypartialserveryes

Release registry + channel pointers + signed bundles are implemented. Executing the deployment on your hosts/Kubernetes is an integration boundary (webhooks / CLI in CI).

Percentage rollouts are cohort-based on device/instance id; load-balancer weighting must be done by your platform.

config-assetssupportedserveryes
otaunsupportedservern/a

Not applicable to backend services.

native-releaseunsupportedservern/a

Artifacts: server-bundle (.tar.gz .tgz .zip) · container-image-ref (.json) · config (.json)

Python alpha

Stacklift stores signed server bundles or container image references and tracks which release each channel points to. Your CD system (fetching and verifying the artifact through the delivery API or an SDK) performs the actual rollout to servers/orchestrators — Stacklift does not run your infrastructure.

MechanismSupportPlatformsSignedRestrictions & limitations
backend-deploypartialserveryes

Release registry + channel pointers + signed bundles are implemented. Executing the deployment on your hosts/Kubernetes is an integration boundary (webhooks / CLI in CI).

Percentage rollouts are cohort-based on device/instance id; load-balancer weighting must be done by your platform.

config-assetssupportedserveryes
otaunsupportedservern/a

Not applicable to backend services.

native-releaseunsupportedservern/a

Artifacts: server-bundle (.tar.gz .whl .zip) · container-image-ref (.json) · config (.json)

Go alpha

Stacklift stores signed server bundles or container image references and tracks which release each channel points to. Your CD system (fetching and verifying the artifact through the delivery API or an SDK) performs the actual rollout to servers/orchestrators — Stacklift does not run your infrastructure.

MechanismSupportPlatformsSignedRestrictions & limitations
backend-deploypartialserveryes

Release registry + channel pointers + signed bundles are implemented. Executing the deployment on your hosts/Kubernetes is an integration boundary (webhooks / CLI in CI).

Percentage rollouts are cohort-based on device/instance id; load-balancer weighting must be done by your platform.

config-assetssupportedserveryes
otaunsupportedservern/a

Not applicable to backend services.

native-releaseunsupportedservern/a

Artifacts: server-bundle (.tar.gz .zip) · container-image-ref (.json) · config (.json)

Java / JVM alpha

Stacklift stores signed server bundles or container image references and tracks which release each channel points to. Your CD system (fetching and verifying the artifact through the delivery API or an SDK) performs the actual rollout to servers/orchestrators — Stacklift does not run your infrastructure.

MechanismSupportPlatformsSignedRestrictions & limitations
backend-deploypartialserveryes

Release registry + channel pointers + signed bundles are implemented. Executing the deployment on your hosts/Kubernetes is an integration boundary (webhooks / CLI in CI).

Percentage rollouts are cohort-based on device/instance id; load-balancer weighting must be done by your platform.

config-assetssupportedserveryes
otaunsupportedservern/a

Not applicable to backend services.

native-releaseunsupportedservern/a

Artifacts: server-bundle (.jar .war .tar.gz .zip) · container-image-ref (.json) · config (.json)

.NET alpha

Stacklift stores signed server bundles or container image references and tracks which release each channel points to. Your CD system (fetching and verifying the artifact through the delivery API or an SDK) performs the actual rollout to servers/orchestrators — Stacklift does not run your infrastructure.

MechanismSupportPlatformsSignedRestrictions & limitations
backend-deploypartialserveryes

Release registry + channel pointers + signed bundles are implemented. Executing the deployment on your hosts/Kubernetes is an integration boundary (webhooks / CLI in CI).

Percentage rollouts are cohort-based on device/instance id; load-balancer weighting must be done by your platform.

config-assetssupportedserveryes
otaunsupportedservern/a

Not applicable to backend services.

native-releaseunsupportedservern/a

Artifacts: server-bundle (.zip .tar.gz) · container-image-ref (.json) · config (.json)