buildtree

Share mobile builds with QA, Product, stakeholders, or clients

Upload an IPA or APK and share an install link or QR code. Keep builds organised by branch and environment, with tester feedback attached to each build.

Start freeSee pricing

Free forever for 1 project. No credit card.

~/trail-atlas
$ buildtree upload ./app.ipa --env dev --branch feature/payments
  ↳ Uploading app.ipa (28.4 MB)…
  ↳ Confirming upload…
✓ Uploaded (com.trailatlas.mobile v1.5.0 build 142)
  https://buildtree.sh/install/folder/trail-atlas/dev/feature/payments

Get builds onto your testers’ phones

Register iOS test devices, share install links and collect feedback on each build. Upload from your computer or CI, then send testers the link for the build or branch they need.

For iOS and Android

Upload builds from React Native, Expo, Flutter, Xcode or Android Studio. Use your existing build tools to produce an .ipa or .apk.

A folder for every branch

Each branch has a stable install link. Share it with QA once; later uploads appear at the same address.

QR + CLI workflow

Upload from your terminal or CI in one command. Pin an install URL to a build, point at the latest in a folder, or freeze it to a release tag.

Works from your AI coding agent too. Add the buildtree MCP server to Claude Code, Codex or Cursor and ask for a QR code.

Build, upload, share.

Use the CLI to share the build you already have.

01

Build your app

Build on your computer or in CI using your existing tools.

ci
$ eas build --local
  ↳ build/App.ipa
02

Upload via CLI

Upload the .ipa or .apk from your terminal. The CLI returns an install link and QR code.

ci
$ buildtree upload App.ipa
✓ build id 7f3e…
03

Share QR or install link

Share a specific build for review, or a branch link that updates with each upload.

ci
  /install/folder/trail-atlas/uat
  /install/release/trail-atlas/v1.5.0

Test each branch before merging

Add an upload step to CI so each feature branch gets an install link. QA can test changes before they merge into develop, then use the environment link to check the merged build.

  1. PR opens for feature/payments

    CI runs buildtree upload --env dev --branch feature/payments

  2. QA gets a branch URL that auto-updates

    /install/folder/<project>/dev/feature/payments stays the same every commit

  3. Tester signs off, PR merges to develop

    Testers can reopen the same link to check fixes before approving the PR.

  4. Merge produces the new develop checkpoint

    buildtree upload --env dev (no --branch) updates the shared link for the merged build.

Full pre-merge QA guide

Guides for your stack

From the first build to an install link on every pull request.

Choose a plan for your projects

Monthly plans with fixed storage and project limits. No overage charges.

Free

Share builds from one app.

$0
  • 1 project
  • 5 GB storage
  • 30-day retention
  • Public QR links
  • Tester feedback with screenshots
Start free

Solo

For developers managing a few apps.

$9/mo
  • 3 projects
  • 25 GB storage
  • 90-day retention
  • A folder for every branch
  • Private install links
Sign up to subscribe
Recommended

Team

For teams testing several apps.

$29/mo
  • 10 projects
  • 100 GB storage
  • Unlimited retention
  • Team members + roles
  • Install analytics
  • Slack notifications
Sign up to subscribe

Business

For organisations managing many apps.

$99/mo
  • Unlimited projects
  • 500 GB storage
  • SSO / SAML
  • Audit logs
  • Custom domain
  • Priority support
Sign up to subscribe

Hard limits per tier. No usage-based overage billing. Customers approaching limits get warned at 80% and 100%.

Ready to share your first build?

Start with one free project. Sign in with your email, upload a build and share the install link. No credit card required.

Start free