Every app your team builds, in one place
The team page lists every app, who built it, and when it last changed. Apps belong to the team, so they keep running when the person who built them is away.
The launchpad for your AI-enabled business.
Build with your coding agent and say “deploy this.” Tools for your team and apps for your customers go online in minutes, private until you share them.
Works with the agents your team already uses, and many more
- Claude Code
- Codex
- Cursor
- GitHub Copilot
Build it with AI. Launch it here.
Deploy by asking
Say “deploy this” to Claude Code, Codex, Cursor, or Copilot, and a minute or two later the agent hands back a link. Ask again after a change and the same link shows the new version. If an update fails, spawnpoint puts the last version back.
Apps for your customers
Launch apps that your customers or clients use, and charge for them. Keep a client's app private to that client's company, or make it public for anyone with the link.
Payments with Stripe
Your agent can add Stripe checkout and subscriptions to an app. The Stripe keys go in the app's encrypted settings, and spawnpoint refuses to deploy an app that has a key written into its code.
Open-source AI models
An app that uses AI can run on open-source models such as gpt-oss through spawnpoint, with no OpenAI or Anthropic account. Free includes $5 a month. Pro has no monthly limit and no usage bill.
Records and files that stay
When an app needs to keep records or files, the agent adds a database or file storage, and spawnpoint runs it. Both stay through every update.
Your data stays yours
We do not use your code, files, or prompts to train AI models. Data is encrypted at rest, and our data processing agreement is published. The security page says where each part runs.
A space for your team
A team owns its apps, skills, and MCP servers. Coworkers join by invite or with their company email, and one install line gives every member's agent the team's tools.
Your own domain
Put an app on a domain you own, with HTTPS, or give the whole team one, so every app opens at an address like tracker.apps.acme.com. Included in Pro.
People who answer
Email support@getspawnpoint.com and the people who build spawnpoint reply. On Business, an engineer works with your company to build its first apps.
Your company builds with AI. Give it a home.
Your team’s dashboards, trackers, and MCP servers shouldn’t live on individual laptops. Bring them together in spawnpoint, where the whole team can find and use what’s been built.
Your apps, on your company's domain
Add a domain your company owns once, and every team app opens under it, like tracker.apps.acme.com. Nothing to set up for each app. Included in Pro.
Skills and MCP servers, shared with the team
Publish a skill or put an MCP server online for the team, and one install line adds them to every member's Claude Code or Codex.
One line per person. One sentence per app.
-
Start a team
Sign in with your work email, name the team, and start Pro. Invite coworkers by email, or let anyone with an @yourcompany.com address join with no invitations to send. They don't pay: the person who starts Pro does.
-
Everyone asks their agent to install it
One message sets up each coding agent on their computer: Claude Code, Codex, Cursor, Copilot, and more. To add the team's MCP servers and skills too, send the agent the install line from your team page.
Install spawnpoint for yourself: https://getspawnpoint.com/install -
Say “deploy this”
Each agent signs in once in the browser. From then on, a minute or two after you ask, it hands back a link that everyone on the team can open. Say it again after a change and the same link shows the new version.
Free to try an idea. Pro is $100 a month for you and up to 2 teams.
Common questions
What is spawnpoint?
The launchpad for your AI-enabled business. When you or someone at your company builds a tool, an app for customers, an MCP server, or an app that uses AI with a coding agent, spawnpoint puts it online with a private link. On a team, the app belongs to the company, and every member can open it. Nobody sets up or manages a server.
Who is it for?
Businesses whose people build with a coding agent such as Claude Code, Codex, or Cursor: companies that want their tools in one place the whole company can open, and founders, consultants, and agencies who launch apps for their customers. One person can use it too: a team is optional.
How does a team work?
Someone on Pro makes the team on the Team tab of the console. An admin invites people by email, or turns on domain join so that anyone who signs in with the same email domain joins it. Members do not need a plan of their own: the Pro plan of the person who made the team covers it, for up to 10 members. When a member connects an agent, they pick whether it deploys for them alone or for the team. Team apps show up on the team page with who built each one. A team app belongs to the team, not to the person who built it, so every member can open it and any admin can manage it.
What can our agents build?
Any small web app: a page or a site, an app that keeps data (an inventory tracker, a lunch order form, a photo gallery), an app that uses AI, or an MCP server your team's agents share. The agent picks what the app needs, including a database or file storage, and spawnpoint provides it. An app that uses AI can run on open-source models through spawnpoint, with no OpenAI or Anthropic key. Apps made with frameworks such as Next.js, Remix, Astro, and SvelteKit work, and so do apps in other languages: an app that comes with a Dockerfile is built on its own machine.
Who can see what we deploy?
Your team, and nobody else until you say so. A team app opens for every member, and a personal app for its builder alone. Share an app with specific people by email, or with everyone at a domain like @acme.com (they verify with a one-time code, no account needed), or make it public for anyone with the link. Agents can do all of this, and so can the console.
Can an app take payments?
Yes. Your agent can add Stripe to an app: a checkout page, subscriptions, and the messages Stripe sends back when a payment goes through. The Stripe keys go in the app's settings, which are encrypted, and never in its code: spawnpoint refuses to deploy an app with a Stripe key written into it. An app that receives Stripe's messages must be public, because Stripe cannot sign in to a private app.
Is it safe to deploy code an agent wrote?
spawnpoint refuses an app with a recognizable API key (AWS, Stripe, OpenAI, Anthropic, GitHub, and others) written into its code, and the plugin's security audit checks an app before it ships: leaked keys, files that should not upload, debug mode, and admin pages with no login. Every app with a server runs on its own isolated machine. On a team, only the member who built an app, or an admin, can delete it or its data.
How much does it cost?
Free is for trying an idea on your own: one live app at a time, sharing with up to 50 people per app, and $5 a month of AI usage on open models. Pro is $100 a month: unlimited apps, up to 2 teams with up to 10 members each, and 5 apps that never sleep. Only the person who makes a team pays: the members they invite don't. Business adds an engineer who helps build your first apps. Pro is a flat monthly subscription with nothing to top up, managed or cancelled in the console. The pricing page compares the plans.
“spawnpoint made deployment incredibly easy for us during the hackathon. We were able to go from building with coding agents to having a live, shareable app without spending time setting up deployment infrastructure ourselves. It let us stay focused on the product and ship much faster.”
Launch the next thing your business builds.
Start a team, send your coworkers one line, and the next app anyone builds is online, private, and ready for the people it is for.
