bedrock
Docs

Quickstart

From zero to a signed Android build in four steps.

1. Install the CLI

See Install the CLI for the one-line installer and manual download links. Once it's on your PATH:

bedrock --version

2. Sign in

bedrock login

Opens your browser to sign in with GitHub, then waits for you to approve it. On first sign-in you'll be prompted to create an organization.

3. Link your project

From the root of an existing Expo or React Native project:

bedrock init

A wizard walks you through picking (or creating) an organization, project, and app, then writes a small bedrock.json in the current directory linking it to that app. Every command below reads from this file, so you only do this once per project.

4. Build

bedrock build

Runs a real Android release build remotely. No local Android SDK required. Drops into a full-screen view: a sidebar of builds (switch between them with arrow keys or digits) next to a live log pane for whichever one is selected, and prints a dashboard link so you can watch from the browser instead. When it finishes, you'll have a shareable download link for the resulting APK/AAB.

Next: signing and secrets

Before shipping a real release build, most apps need two more things:

bedrock signing upload --keystore <path> --alias <alias>   # once per app
bedrock env set API_URL=https://api.example.com --profile release

See the CLI reference for every command and flag, or Security for exactly how your keystore and secrets are protected.