launchpad
Health Warn
- License — License: NOASSERTION
- Description — Repository has a description
- Active repo — Last push 0 days ago
- Low visibility — Only 5 GitHub stars
Code Fail
- exec() — Shell command execution in plugins/launchpad/dist/launchpad.mjs
- process.env — Environment variable access in plugins/launchpad/dist/launchpad.mjs
- network request — Outbound network request in plugins/launchpad/dist/launchpad.mjs
- crypto private key — Private key handling in plugins/launchpad/dist/launchpad.mjs
Permissions Pass
- Permissions — No dangerous permissions requested
No AI report is available for this listing yet.
Tell Claude your idea and launchpad gets it live: hosting, payments, analytics and app testing, set up properly on free tiers. It costs $49 once for unlimited apps.
launchpad
Ship the app on your laptop: live, secure and measured.
launchpad is a Claude Code plugin. Point it at a repository and it takes the app through a production checklist
using industry standards: builds in the cloud, signing, a release channel, keys in your vault, crash reports,
analytics, uptime alerts and the store paperwork. Mission Control, a dashboard on your own machine, shows every
project, its progress and its next step.
- One payment. $49 once for the first 1,000 buyers, then $129. No subscription.
All 1.x updates are included; 2.0 is a paid upgrade, discounted for owners. - Runs on your Claude subscription. Onboarding a project usually fits well under one 5-hour session limit.
- Runs on your machine. Your code and your keys stay with you. launchpad asks before anything that costs money,
changes DNS or uploads to a store.
What it works on
launchpad ships six kinds of app — iOS app, Android app, macOS app (DMG), Web app, Static site, Backend service — built with any of these:
| Built with | Surface | Where it ships |
|---|---|---|
| Flutter | iOS app + Android app | TestFlight and the App Store for iOS; Firebase App Distribution for Android (a Play upload is not wired — the release build is yours to upload). |
| Swift / Xcode (iOS) | iOS app | TestFlight on a push to your test branch, the App Store on a tag. |
| Swift / Xcode (macOS) | macOS app (DMG) | A signed, notarized, stapled DMG on your own download URL, with Sparkle in-app auto-update. |
| Next.js, Nuxt, SvelteKit, Astro, React Router, TanStack Start, Remix, Angular, Qwik, SolidStart, Gatsby, Vite, Create React App | Web app | Vercel |
| Hugo, Jekyll, Eleventy, MkDocs, Zola, Astro (static), Docusaurus, Hand-written HTML | Static site | Cloudflare Pages |
| Android (Kotlin / Java) | Android app | Firebase App Distribution on a push, and the AAB Play wants kept on every build. |
| React Native | iOS app + Android app | TestFlight and the App Store for iOS; Firebase App Distribution for Android. |
| Expo | iOS app + Android app | TestFlight and the App Store for iOS; Firebase App Distribution for Android — or, on EAS Build, EAS's install links and its submission to both stores. |
| Cloudflare Worker | Backend service | Cloudflare Workers — a deploy on every push, staging as its own Worker, and its own cron triggers and queues. |
| Hono, itty-router | Backend service | Cloudflare Workers or Google Cloud Run |
| Express, Fastify, NestJS, Koa, hapi, Elysia, Go HTTP server, Python web service, Containerised service | Backend service | Google Cloud Run |
Where a stack has a limit, /launchpad:status says so for your app.
Recognised, with no pipeline yet. launchpad scores these and shows them on Mission Control, and says that it has no pipeline to write: Tauri desktop app, Electron desktop app, Swift package, Ruby on Rails app, Django app, WordPress site, Laravel app, Phoenix app, Elixir project, Rust project, Go project, Python package, Ruby gem, .NET project, JVM project, Deno app, Wasp app, Browser extension, Node CLI, Node package.
Not supported yet: Capacitor / Ionic.
A repository can hold several of these; launchpad finds each app in it. Every pipeline is a GitHub Actions workflow,
so the repository has to be on GitHub (a mirror is enough).
Install
You need Node.js 20 or newer on your computer. To check, type node --version in a terminal; the installer is at
nodejs.org.
Inside Claude Code, one at a time: paste the first line and press Enter, then the second. The second opens a short
review screen, and Enter accepts its first choice, which installs launchpad for your user.
/plugin marketplace add shiplaunchpad/launchpad
/plugin install launchpad@launchpad
Or from a terminal:
claude plugin marketplace add shiplaunchpad/launchpad
claude plugin install launchpad@launchpad
In VS Code's Claude Code panel, plugins are added from its own plugin manager. Paste this link into your browser's
address bar: VS Code opens the manager, asks to add launchpad's marketplace, then where to install it (choose your user).
vscode://anthropic.claude-code/install-plugin?plugin=launchpad&marketplace=shiplaunchpad/launchpad
Or type /plugins in the panel, add shiplaunchpad/launchpad on the Marketplaces tab, then press Install next to
launchpad on the Plugins tab. In the Claude desktop app, or when neither shows up, run the two terminal lines above:
every Claude Code you use on this computer then has launchpad.
Installing costs nothing, and nothing runs until you
activate a key. Installed inside Claude Code, the /launchpad: commands work at once. Installed from a terminal while
Claude Code is open, type /reload-plugins in Claude Code first.
Claude Code warns you to trust a plugin before you install it. launchpad is published by its author on GitHub atshiplaunchpad/launchpad. After you activate, everything it runs is in plain files on your machine (see
What launchpad stores on your computer), so you can read every one of them.
Activate and start
Buy a key on shiplaunchpad.com. It arrives in your receipt email. Then, in Claude Code:
/launchpad:license <your key>
You see Unlocked: launchpad <version> pack installed. Open Claude Code in the repository you want to ship and run:
/launchpad:onboard
launchpad reads the repository, asks the few questions it cannot answer itself, and tells you what it will write
before it writes anything. To look first and change nothing, run /launchpad:status.
A key works on two machines. /launchpad:license deactivate frees its seat on a machine you no longer use. A key
that has been checked once keeps working offline for up to 30 days at a time; then launchpad needs to reach its
license server once.
Updating
Mission Control shows a banner when a new version is out. You click Update to install it, then type/reload-plugins in Claude Code to load it. From a terminal it is two commands:
claude plugin marketplace update launchpad
claude plugin update launchpad@launchpad
launchpad never updates itself. When a release fixes something important, the banner says so.
Mission Control
/launchpad:dashboard
It serves on http://127.0.0.1:4747, on your machine only. It shows every project, its progress, its next step,
and why launchpad made each choice it made.
What launchpad sends
launchpad sends three things to us or our payment provider (the landing page and the privacy page print the same list):
- An update check. This happens at most once a day, and whenever you ask. It sends nothing about you. It reads one public file on our site, the list of releases, the same way a browser does.
- A license check. This happens when you activate your key, about once a day while you use launchpad, and when Claude opens one of its instructions. It sends your key to our license server, which passes it to the payment provider to confirm it, or to the payment provider directly when our server can't be reached. It also sends this computer's name and a short one-way code made from its id the same way when you activate, so you and support can tell which computers use the key. It sends your key, this computer's activation, a one-way code made from this computer's id and the version to our license server. Our license server sends launchpad, and each instruction Claude opens, only to the computer your key is on. Our license server keeps a one-way code made from your key with the version it ran each day, for 400 days, so we can see whether updates arrive. It never sends your code or your files.
- launchpad's own usage analytics. This happens only if you said yes, at the end of setting up a project. It sends anonymous usage analytics about launchpad to our license server. They list the stacks launchpad found and the checklist items that worked. They never contain your code, names or paths. You can turn them off again whenever you like. In Claude Code, ask Claude to turn them off.
What launchpad sends to your own accounts when you ask it to act (GitHub, your host, your stores) is your data going
to your accounts.
What launchpad stores on your computer
The plugin you install is a small loader. launchpad itself arrives as a signed pack in~/.launchpad/pack/<version>/, readable only by you: plain JavaScript, the skills and the templates. launchpad
checks the pack's signature before every run and refuses to run an edited file. An update replaces the pack.
In each repository it writes .launchpad/ (its state, checked in so it travels with the code), a marked block in
your CLAUDE.md (the rest of the file stays as it is), and its workflows in .github/workflows/launchpad-*.yml. It
lists every file it is about to change before it changes it, and it never overwrites a file you edited.
To put back the files it wrote in its last run, ask Claude Code to undo launchpad's last change. Your keys go to your OS keychain, or to an encrypted
file where there is no keychain. They never go to the repository or a .env file.
Windows, Linux and proxies
- Windows and Linux. launchpad works best on macOS today. If you use Windows or Linux, write to support before you
buy, and we'll check that it fits your setup. Keys go into an encrypted file, and launchpad needs a passphrase in the environment Claude
Code starts from:LAUNCHPAD_VAULT_PASSPHRASE. Keep it in your password manager; it cannot be recovered. On Windows
or Linux, iOS and Mac apps build on GitHub's macOS machines; on a Mac, launchpad suggests building on your own Mac. - A corporate proxy. Set
HTTPS_PROXYandNODE_USE_ENV_PROXY=1before you start Claude Code.
Uninstall
Do these in Claude Code, in this order:
If you set Mission Control to start at login, ask Claude to stop it.
Release this computer's seat. This also removes launchpad's files from
~/.launchpad/pack:/launchpad:license deactivateRemove the plugin:
/plugin uninstall launchpad@launchpadRemove the marketplace:
/plugin marketplace remove launchpad
The pipelines launchpad wrote stay in your repositories and keep running; they are yours. ~/.launchpad keeps
launchpad's settings and, on Windows and Linux, your encrypted keys, so delete it only once you no longer need them. On
a Mac your keys stay in Keychain until you remove them there. If the computer is already gone, write to support, and
support frees its seat.
Support
Bugs, questions and license problems: [email protected].
In Claude Code, run /launchpad:doctor and attach the report it prints. It is safe to send, and it answers most questions before they are asked.
If your key would not activate, send what /launchpad:license printed and the last four characters of your key.
Sales and support. Sales are final. If anything goes wrong, write to [email protected] with the report launchpad prints. Support works through the problem with you, fixes what launchpad got wrong, and can free the seat on a machine you no longer use.
If launchpad broke a working deploy, say so in the subject. We answer those messages first. Never send your whole
license key: the last four characters are enough to find a purchase.
Reviews (0)
Sign in to leave a review.
Leave a reviewNo results found