The release dashboard for
mobile app teams.
Stop wrangling with CI pipelines. Quit tracking releases on spreadsheets.
Tramline transforms your app releases into well-defined workflows on autopilot.
Free your engineers. More output, less busywork.
CI/CD doesn't cut it
CI pipelines are great for running tests and creating builds. But app releases involve different types of builds (staging, RC), lots of tools (build distribution, app stores, observability), and multiple stakeholders (developers, product, marketing).
Tramline coordinates all those parts so your team can focus on the real work.
By combining data from the tools that you already use, Tramline lets anyone run a successful release. It uses official APIs to get the work done, so no more worrying about individual access control either.
Say goodbye to switching through documents and checklists.
Tramline sends context-specific notifications as your release makes its way to completion, so stakeholders only get alerts for the things they care about.
Every action gets recorded automatically, whether it's done by the system or a user, giving you a precise audit trail of every release.
Customer Reviews
Intelligent Store Rollouts
All mobile teams have felt the stress that comes with releasing a bad update to users. App stores do not allow pulling a broken build that has been installed on a user's device. Tramline reduces this stress by giving superpowers to the phased release (or staged rollout) process.
Get data from monitoring and analytics systems, stitch it together the way you want, and send out alerts that you really need.
Determining the stability of a release is based on looking at multiple sources of data: crashes, business analytics, product metrics. Tramline connects to the platforms you use every day, and gives you a release-specific window into all that data.
For e.g. in this release, how does user adoption correlate with phased release stage and checkout success rate?
Equipped with multi-dimensional data, Tramline can be configured to send alerts when something starts to look amiss, or even halt the rollout immediately. For e.g. in this release, when adoption is more than 50%, checkout success is more than 99% but refund rate is more than 25%, send an alert on Slack.
For mobile developers, by mobile developers
Automate the busywork that developers do during releases so they can focus on building. Creating release branches and tagging builds is easy, but Tramline also guarantees that work from the previous release has been merged before starting a new one. And that's not all.
No more merge hells. Or remembering to increment versions. Or clicking around in store consoles to submit a new build. You write the code, Tramline does the grunt work.
When things start breaking on user devices, panic sets in. The release must be patched and updated on the store quickly, but which commit created it? On which branch?
Tramline makes it easy: you start a hotfix for a release, copy the hotfix branch name, and land the fix(es). Tramline will then create a new release, generate a build with the correct version, close the live release, and start the new rollout... without you having to lift a finger.
And much, much more
Mobile DevOps Reports
Your mobile team has special DevOps metrics that Tramline tracks automatically. Release frequency, release duration, number of contributors (including breakdown by team), hotfixes done, and many more are measured and charted to show trends across releases.
Build Queue
When developers rapidly create fixes on the release branch, testers can get swamped with builds. The Build Queue can be configured to wait before triggering a new build, saving expensive CI minutes.
Scheduled Releases
Tramline can automatically kick-off production releases, and nightly releases can run all the way without any manual intervention. Haven't added new code? Tramline will not release the same commit twice!
Cross-Platform Releases
Take the cross-platform advantage to releases! Tramline can run App Store and Play Store releases together in a synchronized manner, giving teams a single view to manage both releases.
Automatic Backmerges
Any fixes that land on the release branch are automatically cherry-picked onto the working branch, in real time. It saves hours of time during release week, and lets developers focus on work.
Pure open source, no caveats
No SSPL, no BSL, no exceptions. Tramline is open source, through and through, under the universally accepted Apache 2.0 License. Check out our source code, issue queue, or just run the system yourself, no strings attached.
Why? We believe critical software should be open to public review and scrutiny. Modern release engineering practices are built on a backbone of open source software and we benefit from that too. Being open source guarantees the longevity of our product, and inspires confidence in our enterprise customers.