Common questions

The place where your team's AI lives. When someone at your company builds a tool, an MCP server, or an app that uses AI with their 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.

Companies whose people already build with a coding agent such as Claude Code, Codex, or Cursor, and want those tools in one place the whole company can open. One person can use it too: a team is optional.

No. Each person signs in once in the browser and their agent takes it from there. spawnpoint runs the app and gives it a secure (HTTPS) web address.

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. 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.

One command sets up whichever coding agents are on a computer. It works with Claude Code, Codex, Cursor, Copilot, and many more:

Then sign in once in the browser for each agent. On a team, use the line from the team page instead: it also adds the team's MCP servers and skills. The supported agents page has the exact step for each agent. Any other MCP client needs only https://app.getspawnpoint.com/mcp.

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.

The team does. An app an agent deploys for the team belongs to the team, not to the person who built it, so every member can open it and any admin can manage it. Admins add and remove members on the team page.

Yes. An MCP server is a small program that agents can ask for things, and a skill is a set of instructions for a task. A team's MCP servers are listed on its team page, and an agent can publish a skill to the team so every member's agent can follow it. The install line on the team page adds both to Claude Code and Codex in one step.

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.

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.

Yes. spawnpoint gives apps open-source AI models to use. When an app needs AI, the agent asks whether to use them, and if you say yes, the app works with no OpenAI or Anthropic account and no key to paste in. The blog post You can spawn AI apps now shows what they can do.

Yes, on Pro and Business. Any app can have its own domain: ask your agent, and it gives you the DNS records to create. HTTPS is set up once spawnpoint confirms them. Every team app can also open under one domain your company owns, such as tracker.apps.yourcompany.com. The spawnpoint link keeps working too.

It sleeps: the machine stops while it is idle, and the next visit wakes it in about half a minute. Redeploying also wakes it. On Pro, up to 5 apps can stay always on instead, so nobody waits.

Yes. Open it in the console and click Terminate, or ask your agent. The app is permanently shut down. On a team, the member who built it or an admin can do this.

Free is for trying an idea on your own: one live app at a time, unlimited sharing, 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.

Pro is a flat monthly subscription: $100 a month for each person who subscribes, with nothing to top up and nothing billed by usage. You start it in the console, and one checkout covers your own apps and up to 2 teams you make. Invoices, receipts, your card, and cancelling are in Stripe's billing portal, which the console opens for you.

Your account goes back to Free's limits, and nothing is deleted. The apps you have keep running, and your agent can still update them. Free runs one live app at a time, so a new app waits until you terminate the ones you have or subscribe again. Always-on apps go back to sleeping when idle, a database larger than 256 MiB turns read-only, and file storage over 500 MiB stops taking new files. Teams you made keep their apps and members, and new apps and invites on them wait until a Pro plan covers them again.

No. The person who makes the team pays, and the people they invite don't. One Pro plan covers up to 2 teams its subscriber makes, each with up to 10 members. A member's personal apps, outside the team, follow their own plan.