BuildStack All guides

Guides › BuildStack: an Expo EAS Build alternative

BuildStack: an Expo EAS Build alternative

5 min read

Expo EAS Build is Expo’s official cloud build service, configured through eas.json and billed on usage credits. BuildStack is an alternative to EAS Build for teams who want the same outcome, a signed Android APK or AAB and an iOS IPA built in the cloud, but driven from a plain HTTP API rather than one toolchain. EAS and EAS Build are trademarks of Expo.

Cloud builds for Expo and React Native, no Mac required

BuildStack builds Expo and React Native projects on managed runners, so there is no local Android SDK to install and no Mac of your own to keep for iOS. Expo projects are prebuilt and native dependencies are resolved for you; Android produces an APK or AAB, and iOS is archived on a managed Mac agent to produce an IPA.

Managed signing you configure once

Your Android keystore is sealed and encrypted at rest, and Apple credentials are managed for you, so a build with sign set to true is signed without a secret passing through your CI. If you do not have a keystore yet, BuildStack can generate and manage one for a supported Android project.

curl -X POST https://api.mybuildstack.com/api/projects/$PROJECT/builds \
  -H "Authorization: Bearer $BUILDSTACK_KEY" \
  -d '{"variant":"release","format":"aab","sign":true}'

Publish to Google Play and TestFlight

Add a publish target and a release build goes straight to a Google Play track (internal, alpha, beta or production) or to TestFlight, with no Transporter or Xcode on your side. Share the scan-to-install QR with testers while store review runs.

Trigger from any CI over HTTP

Because the API is plain HTTP, there is no marketplace action or build config to adopt. The same call runs from GitHub Actions, GitLab CI or your own self-hosted runners, so you keep the pipeline you already have. Builds are billed on build minutes, and workspaces with members and roles keep projects and credentials shared across the team.

# .github/workflows/release.yml
- name: Build & sign with BuildStack
  run: |
    curl -sfX POST "https://api.mybuildstack.com/api/projects/$PROJECT/builds" \
      -H "Authorization: Bearer ${{ secrets.BUILDSTACK_KEY }}" \
      -d '{"variant":"release","format":"aab","sign":true,"publish":"internal"}'
  env:
    PROJECT: ${{ vars.BUILDSTACK_PROJECT }}

If you are weighing up EAS Build, it is worth trying the same release on BuildStack: point a project at your repo, add your signing credentials once, and run a signed build from the API. Create a workspace to get a project id and an API key.

Ship it with BuildStack.

Cloud builds, managed signing and one-call Play publishing for Expo & React Native.

Start free