Stallion Hierarchy

How Organizations, Projects, Buckets, Bundles, and Releases fit together in Stallion.

Stallion Hierarchy

Stallion organizes your OTA workflow under a simple hierarchy. This page defines each layer and how they connect from upload to production.

The hierarchy

Organization
  └── Project
        ├── Buckets  →  Bundles (uploaded JS artifacts)
        └── Releases (promoted bundles, targeted at an app version)
LayerWhat it is
OrganizationYour team or company account. Holds members, access control, and projects.
ProjectA Stallion app target. The native app connects to a project via StallionProjectId and StallionAppToken.
BucketA named folder inside a project where you upload bundles. Name and organize them however you want.
BundleA published JS OTA artifact stored in a bucket.
ReleaseA bundle that has been promoted for a specific app version.

CLI upload paths follow the same shape: org-name/project-name/bucket-name.

Buckets

Buckets are folders for organizing uploaded bundles — for example by feature, platform, or team. You choose the names and structure.

Internal testing

Buckets are used by the Stallion Testing modal. In your app:

  1. Open the Testing tab.
  2. Select a bucket.
  3. Download and install any bundle from that bucket.

That lets your team try builds during development and QA without promoting them first.

Promotion and Releases

The path from upload to production:

  1. Publish a bundle into a bucket (stallion publish-bundle).
  2. Promote that bundle (Console or stallion release-bundle).
  3. Target a specific app version (the version users installed from the store).
  4. That creates a Release under the project.

Once promoted, apps receive the Release based on the project they are configured with and the app version they are running (plus rollout percentage).

How the SDK connects

The Stallion SDK reads StallionProjectId and StallionAppToken from the native build. Those credentials select the project. The SDK then checks for a promoted Release for the running app version.

Multiple environments

For Dev, QA, Production, and similar app flavours, see Handling Multiple Environments.