llms.txt
+39 −24
− > Corenna is a mobile-first platform that turns a GitHub repo into signed, store-ready Android (.apk, .aab) and iOS (.ipa) app files, and pushes updates for apps already on Google Play straight to the store. It is built to be used from a phone: connect a repo, upload signing files, start a build, watch it run, and download the signed app or send it to Google Play, all in a phone's browser. No app to install, no laptop, and no Gradle, Android Studio, Xcode, Mac, or terminal.− Corenna writes a GitHub Actions workflow into the user's own repository, runs the build on GitHub-hosted runners, signs it with the user's keys, and hands back the signed file, or sends Android updates straight to Google Play. iOS builds are signed for App Store Connect, where the user uploads them. Users keep ownership of their code, signing keys, and app files.− - Corenna is a mobile web app designed for phones first: touch-sized controls, one-thumb navigation, and no pinch-zooming. It is a CI/CD platform designed to be operated from a mobile device, and it works in desktop browsers too.− - The phone only runs the interface. Builds run on GitHub-hosted runners in the cloud, so nothing compiles on the device or drains its battery.− - iOS: a signed .ipa for App Store Connect, built on macOS runners, so no Mac is needed.− - Corenna can take over updates for an Android app that is already live on Google Play: no building in Android Studio and no manual upload in the Play Console.− - Each update is built from the repo, signed with the app's existing upload key (uploaded to Corenna once), and sent straight to the chosen Play track (Internal, Alpha, Beta, or Production) with release notes, using a Google Play service account.− - Google requires a brand-new app's very first release to be created by hand in the Play Console. Every update after that can come from Corenna.− - Google Play upload: send a signed .aab straight to the Internal, Alpha, Beta, or Production track, with release notes, using a Google Play service account.− - MCP server for AI assistants: ChatGPT, Claude, and other MCP clients can check repos, list projects and builds, start builds, and fetch results.− - The first successful Android build is free, with no card. Failed builds never count.− - Sandbox builds are free on Android and iOS.− - After that, and for every iOS build: $4.99/month, or $49 once for lifetime access. Cancel the monthly plan anytime; it stays active until the end of the paid period. 30-day money-back guarantee, processed by Paddle.− - Corenna does not copy source code to its own servers. Builds run on GitHub Actions runners inside the user's repository.− - Keystores, passwords, Apple certificates, and provisioning profiles are encrypted at rest and passed to builds as encrypted GitHub Actions secrets. They are never stored in the repo.− - MCP server: https://dqwnwgkjhbiluockgnji.supabase.co/functions/v1/mcp (OAuth sign-in with a Corenna account). Tools: `check_repo` (works without an account), `list_projects`, `list_builds`, `get_build`, `trigger_build`.− - [Connect an AI assistant](https://corenna.dev/connect): How to add the MCP server to ChatGPT or Claude.− - [Pricing](https://corenna.dev/pricing): First Android build free, then $4.99/month or $49 lifetime.− - [Sample apps](https://corenna.dev/examples): Six sample apps (Lovable, Bolt, v0, Replit, FlutterFlow, React Native) and the steps Corenna takes to ship each. Illustrations, not customer stories.− - [FAQ](https://corenna.dev/faq): Builds, signing, refunds, pricing, and the free first build.− - [World's first mobile CI/CD](https://corenna.dev/blog/worlds-first-mobile-cicd): Why Corenna was built for a phone.− - [Choosing a mobile build stack in 2026](https://corenna.dev/blog/mobile-build-stack-2026): CI/CD, signing, and what it actually costs.− - [From Capacitor (or Lovable) to the App Store and Play Store](https://corenna.dev/blog/capacitor-to-app-store-and-play-store): The 2026 playbook.− - [Managing .env files in mobile CI/CD](https://corenna.dev/blog/managing-env-files-mobile-cicd): The safe pattern for GitHub builds.+ > Corenna turns a GitHub repo into signed Android (.apk, .aab) and iOS (.ipa) app files, and can send updates for an app already on Google Play to a Play track. It works in a phone's browser as well as on a desktop: connect a repo, upload signing files, start a build, watch it run, and download the signed app. There is nothing to install: no Gradle, Android Studio, Xcode, Mac or terminal. Android builds are the proven path. iOS builds are in beta.+ Corenna writes a GitHub Actions workflow into the user's own repository, runs the build on GitHub-hosted runners, signs it with the user's keys, and hands back the signed file. A signed .aab can then be sent to a Google Play track. An iOS build produces an .ipa that the user uploads to App Store Connect. iOS builds are in beta: no signed iOS build has finished on Corenna yet, so a free sandbox build is the way to test one first. Users keep ownership of their code, signing keys, and app files.+ - Corenna is a web app laid out for phones first, with touch-sized controls. It also works in desktop browsers.+ - The phone only runs the interface. Builds run on GitHub-hosted runners, so nothing compiles on the device.+ - iOS (beta): an .ipa for App Store Connect, built on GitHub's macOS runners, so no Mac is needed.+ - Corenna can build and send updates for an Android app that is already live on Google Play.+ - Each update is built from the repo, signed with the app's existing upload key (uploaded to Corenna once), and sent to the chosen Play track (Internal, Alpha, Beta, or Production) with release notes, using a Google Play service account.+ - Google requires a new app's first release to be created by hand in the Play Console. Every update after that can come from Corenna.+ - Sending to Google Play is newer than the builds themselves. If an upload fails, the build page says why, and the .aab can still be uploaded by hand.+ - Free store readiness report, part of the repo check: what Apple and Google Play are likely to object to in the app, read from the repo's files, each with a link to the store's own rule. It covers a web app that is only a website in a wrapper (App Review Guideline 4.2), Google sign-in that will not work in an embedded web view, payments that need in-app purchase, account deletion, a privacy policy, and a login for the reviewer. It reports risks only where the repo shows evidence, and it cannot + - Free Android builds: an account without a plan can build its Android app and watch it finish. The signed file is kept in Corenna's storage and downloads once the account has a plan, with nothing to build again.+ - Google Play upload: send a signed .aab to the Internal, Alpha, Beta, or Production track, with release notes, using a Google Play service account.+ - MCP server for AI assistants: Claude, ChatGPT, Claude Code, Cursor and other MCP clients can add a repo as a project, check it, set up Android signing, start builds, read failed build logs, and hand back the download link. Claude Code and Cursor can also fix the code, push and rebuild on their own until the build succeeds.+ - Building an Android app (.apk or .aab) is free, with no card: the build runs on the user's own GitHub Actions minutes and the finished, signed file is kept. Downloading that file, or sending it to Google Play, needs a plan. An account without a plan can have up to 3 finished builds waiting.+ - The plan: $1 for the first month, then $4.99/month, or $49 once for lifetime access. The $1 first month is for an account's first plan. Cancel the monthly plan anytime; it stays active until the end of the paid period. 30-day money-back guarantee, processed by Paddle.+ - iOS builds (.ipa) need the plan before the build starts.+ - Also free, with no card: the repo check, and sandbox builds on Android and iOS (they check the setup but keep no app file).+ - Since November 13, 2026 the plan is asked for at the download instead of before the build.+ - Corenna does not copy source code to its own servers ("zero clone"). It reads a repo's file list, its config files and, for two checks, a limited number of source files through GitHub's API (up to 40 for a Lovable TanStack Start app, up to 10 for the free store readiness check), and keeps none of their contents. Builds run on GitHub Actions runners inside the user's repository.+ - Corenna stores the finished app file, the user's signing keys, build logs, and project settings; no source code or build caches. It keeps a copy of the Android signing key so it can sign builds, and the user can download that key and its passwords at any time.+ - [Zero clone](https://corenna.dev/zero-clone): How builds stay on GitHub, use the user's Actions minutes and Apple account.+ - Keystores, Apple certificates and provisioning profiles are kept in private storage, with their passwords in an encrypted vault, and are passed to builds as encrypted GitHub Actions secrets. They are never committed to the repo.+ - Corenna does not create iOS certificates or provisioning profiles: the user creates them in Apple's developer portal and uploads them. Corenna has not had a third-party security audit.+ - MCP server: https://dqwnwgkjhbiluockgnji.supabase.co/functions/v1/mcp (OAuth sign-in with a Corenna account; every request needs it). Tools: `check_repo`, `list_projects`, `add_project`, `check_project`, `setup_android_signing`, `trigger_build`, `list_builds`, `get_build`, `get_build_logs`, `get_download_link`. Signing passwords and Apple files are never passed through the assistant.+ - Listed on the official MCP Registry as `dev.corenna/mcp`, version 1.2.0. Remote server over streamable HTTP; sign-in is OAuth with dynamic client registration, so clients that support it connect with just the URL.+ - Hands-off builds in Claude Code: `claude mcp add --transport http --scope user corenna https://dqwnwgkjhbiluockgnji.supabase.co/functions/v1/mcp`, sign in with `/mcp`, allow `mcp__corenna__*` and `git add`, `git commit`, `git push` in `~/.claude/settings.json`, and put the build rules from the connect guide in the repo's CLAUDE.md (Cursor reads AGENTS.md). The agent then builds, reads the log on a failure, fixes, pushes and rebuilds, stopping after 3 failures in a row.+ - [Connect an AI assistant](https://corenna.dev/connect): Step-by-step setup for ChatGPT, Claude, Claude Code, and Cursor.+ - [Pricing](https://corenna.dev/pricing): $1 for the first month, then $4.99/month or $49 lifetime.+ - [Examples](https://corenna.dev/examples): A real signed Android build from a public repo (github.com/nathanclaiborne21/corenna-test-flutter, the founder's Flutter test app) with its public GitHub Actions run, plus six sample apps (Lovable, Bolt, v0, Replit, FlutterFlow, React Native) and the steps Corenna takes to ship each. The sample apps are illustrations, not customer stories.+ - [Docs](https://corenna.dev/docs): Every guide, sorted by task: first build, Android and Google Play, iPhone and the App Store, app builders and frameworks, AI assistants, updates, security.+ - [FAQ](https://corenna.dev/faq): Builds, signing, refunds and pricing.+ - [Contact](https://corenna.dev/contact): support@corenna.dev for builds, accounts and billing; security@corenna.dev for security reports; privacy@corenna.dev for data requests. Emails reach the founder, Nathan Claiborne.+ - [Zero-clone mobile builds: why Corenna never copies your code](https://corenna.dev/blog/zero-clone-mobile-builds): Building inside the user's GitHub repo, GitHub's security, Actions minutes, Apple accounts, and the trade-offs.+ - [Build your app from ChatGPT, Claude or Claude Code](https://corenna.dev/blog/build-your-app-from-chatgpt-or-claude): What Corenna's MCP server lets an AI assistant do, and what stays out of the chat.+ - [Cursor to Android and iOS: hands-free builds with Claude or GPT](https://corenna.dev/blog/cursor-autonomous-mobile-builds): Add Corenna to Cursor's mcp.json, allow its tools, and let the agent build, fix and rebuild.+ - [CI/CD from your phone](https://corenna.dev/blog/worlds-first-mobile-cicd): What works in a phone's browser and where it stops.+ - [Choosing a mobile build stack in 2026](https://corenna.dev/blog/mobile-build-stack-2026): Your own workflow, a hosted CI service, or Corenna, and what each costs.+ - [From Capacitor (or Lovable) to the App Store and Play Store](https://corenna.dev/blog/capacitor-to-app-store-and-play-store): A 2026 checklist.+ - [Managing .env files in mobile CI/CD](https://corenna.dev/blog/managing-env-files-mobile-cicd): A safe pattern for GitHub builds.