Run your mobile release on autopilot with AI agents.
Plan, prepare, and publish release notes and store copy for every locale with your agent — then review everything in one workspace before it goes live.
Use your favorite agent
- ChatGPT
- Codex
- Cursor
- OpenClaw
- Hermes
- Claude
- Claude Code
Who is HyperRelease for?
Agentic
Teams already shipping with Claude, Cursor, Codex, or OpenClaw who want release prep in the agent and publish from HyperRelease.
Devs
Devs shipping the same app on iOS and Android without duplicating release prep.
Teams & Agencies
Teams and agencies running the same agent-friendly release workflow across client apps without rebuilding checklists every launch.
We ship HyperRelease with HyperRelease!
HyperRelease· View HyperRelease changelog →
Eat your own dog food — Marian, Founder of HyperRelease
AI agents
Your agent runs the release
HyperRelease is the release workspace your agent operates on. Ask it to open a version, fill store copy across locales, and mark iOS and Android ready while you review everything before publish.
Bootstrap the release
Spin up a project, add iOS and Android, and open the first version — your agent handles the setup while HyperRelease keeps the structure.
Write store copy
Draft release notes and promotional text for every locale in one pass — without copying between App Store Connect and Google Play.
Keep both stores aligned
Update iOS and Android fields and statuses together so the team shares one answer to “are we ready to submit?”
Hand off publish
Review in HyperRelease, then push listing copy to the App Store and Google Play when you are ready to ship.
No credit card required. Your first release is free.
In the product
From release draft to both stores
Create the version, add release content, review platforms and locales, send listing copy to the stores, and track what is ready or already published.
No credit card required. Your first release is free.
Release workspace
2.4.0
iOS and Android store copy filled for 8 locales — ready to publish.
The HyperRelease Dashboard
The release tax
Your agent can draft the copy. The stores still need a release workspace.
AI agents are great at writing release notes — but without a shared release object, that work stays in chat threads and spreadsheets while App Store Connect and Google Play wait for manual updates.
Agent draft in chat + 2 stores × 8 locales = still 16 fields to paste by hand.
Release prep lives outside the agent
Your agent writes the notes, then someone copy-pastes them into store consoles — locale by locale, store by store.
iOS and Android drift apart
Even with AI help, both stores get updated on different days unless something keeps them aligned.
Nobody sees readiness in one place
Store copy sits in consoles. Agent output sits in chat. Ship day still starts with “did we miss a locale?”
Release 4.9 prep
No single source of truth
4.9
Status unknown
Screenshots
Store copy
Changelog
Translations
QA sign-off
Deploy notes
FAQ
Frequently asked questions
Straight answers on what HyperRelease does for iOS and Android teams, and how it fits the tools you already use.
A mobile release spans two store consoles, multiple locales, and several people checking readiness. Spreadsheets go stale the moment someone updates store copy in App Store Connect or Google Play. HyperRelease keeps version, iOS and Android status, per-locale store fields, and publish readiness in one live workspace.
Ship your next release for $0Install the HyperRelease skill, create a team API token, and connect the MCP server in Cursor, Claude Code, Codex, or OpenClaw. Your agent uses tools like create_release and update_platform_languages to prepare iOS and Android store copy. HyperRelease publishes to App Store Connect and Google Play when you run store propagation from the console.
Connect your agentProjects with iOS and Android platforms, MCP server and REST API for AI agents, release objects with version tracking, per-platform status (Draft, Ready, Published), per-locale store copy, and automatic store propagation to App Store Connect and Google Play when stores are connected on Pro and Rocket. HyperRelease does not submit builds — it handles release content and store publication prep after the build is ready.
See it in your workspaceSmall mobile teams and studios shipping the same app on iOS and Android — including React Native, Flutter, and native teams from about 1 to 20 people. If you have ever asked whether store copy is done for both stores or every locale, HyperRelease is built for that work.
Start your first releaseConfigure project locales once, then fill release notes and promotional text per language in HyperRelease. When App Store Connect and Google Play are connected, listing copy can propagate through the official store APIs. You can also use guided manual flows when you prefer copy-and-paste or a store is not connected yet.
Organize store copyNo. HyperRelease does not replace your build pipeline. It manages release content, iOS and Android coordination, and store publication work that starts once the build is ready.
Ship your next release for $0Each connected platform moves through Draft, Ready, and Published inside a release. That gives everyone a shared answer to where iOS and Android stand without a standup or a screenshot of a spreadsheet.
Track release readinessYes. HyperRelease pricing is based on release scope, not headcount. Invite engineers, product, marketing, and leadership without a seat calculator.
Invite your teamSign up, set up your app, and start on Pro at no cost until you publish your first iOS or Android release. No credit card required. Subscribe from billing settings when you are ready to keep going.
Ship your next release for $0Visit the pricing page for Pro and Rocket plan details. Your first release is free on Pro — no credit card required.
Compare plansStart here
Run your next mobile release on autopilot.
Install the skill, connect your agent, and let HyperRelease publish every locale to App Store Connect and Google Play.
No credit card required. Your first release is free.
I built HyperRelease so my agent could handle store copy while I focus on the product — not pasting release notes into two consoles.
Marian, Founder of HyperRelease