Guide

How to use Helm with Fastlane

Jul 19, 2026 Keep Fastlane for CI and binary uploads, then use Helm for day-to-day metadata, TestFlight, and reviews. A practical split that matches how most teams already ship.

You do not have to choose between Fastlane and Helm. Most teams that ship weekly already have CI lanes for builds and uploads. What slows them down is the human work that follows: polishing What’s New, fixing listing copy, inviting testers, and answering reviews. This guide shows a clean split that keeps your pipeline investment and gives you a native UI for the rest.

For a side-by-side view, read Helm vs Fastlane and Fastlane deliver alternative.

What each tool is best at

Fastlane shines when work must run unattended:

Build, sign, and upload binaries
Repeatable lanes in CI (GitHub Actions, Xcode Cloud hooks, self-hosted runners)
File-driven deliver metadata when you already maintain that structure

Helm shines when a person needs to see and decide:

Edit and preview store listing fields, keywords, and tags
Localize What’s New and listing copy across markets
Manage TestFlight groups, What to Test, and tester invites
Triage and reply to customer reviews

Helm talks to the App Store Connect API. It is a native companion on Mac and iPhone, not a replacement for Apple account admin, banking, or App Analytics.

A workflow that works in practice

CI owns the binary. Your Fastlane lane (or Xcode Cloud) produces the build and uploads it to App Store Connect.
Helm owns the release surface. On Mac, open the version, attach the new build, update What’s New, and run the launch checklist.
Humans review customer-facing truth. Screenshots, keywords, and localization get a visual pass in Helm before you submit.
TestFlight stays interactive. Invite external testers, tweak What to Test, and watch feedback without digging through ASC tabs. See TestFlight in Helm.
Reviews stay in the inbox. Reply from Mac or iPhone after ship day, when support volume spikes.

That pattern keeps Fastlane where it is strongest and Helm where browser tabs usually lose the plot.

Where Helm CLI fits (Pro)

If you want scripts without abandoning the Mac app’s account setup, helm-asc on Helm Pro covers versions, localizations, screenshots, TestFlight, reviews, and more. Credentials flow through the Helm Mac app App Group, so you are not maintaining a second secret store just for agents.

A useful rule:

Fastlane / CI: build artifacts and upload
helm-asc: scripted ASC mutations when an agent or cron job should prepare work
Helm UI: confirm what customers will see, then submit

What not to duplicate

Avoid maintaining the same metadata in both deliver files and Helm as your source of truth. Pick one owner per field:

Binary upload path → CI / Fastlane / Transporter
Listing copy and ASO → Helm (with optional CLI updates on Pro)
Review replies → Helm inbox
Agreements, users, banking → App Store Connect on the web

Duplication is how a keyword change in a YAML file silently overrides a careful ASO pass in the UI.

Team roles that map cleanly

Release engineer: owns the Fastlane lane and build numbers
Product / marketing: owns What’s New, screenshots, and keywords in Helm
Support: owns the reviews inbox on Mac and iPhone
QA lead: owns TestFlight groups and What to Test

Helm’s iOS companion helps when someone needs to approve a phased release or answer a one-star review away from their desk.

Getting started this week

Leave your existing Fastlane upload lane alone.
Install Helm on Mac, add your App Store Connect API key, and open your shipping app.
For the next version, do metadata and TestFlight in Helm only.
After approval, handle reviews in Helm for one full week.
If you need terminal automation later, enable Pro and install helm-asc from Settings.