Skip to content
Public beta

The place where your team's AI lives

Everything your team builds with AI, online in one place your whole company can open.

Works with the agents your team already uses

Your company builds with AI. None of it has a home.

Across the company, people build dashboards, trackers, and MCP servers with their coding agents. Each one runs on the laptop of the person who built it, so it stops when that laptop closes, and nobody else can open it.

One line per person. One sentence per app.

  1. Start a team

    Sign in with your work email and name the team. Coworkers who sign in with the same @yourcompany.com address join it, with no invitations to send.

  2. Everyone runs one line

    It sets up each coding agent on their computer: Claude Code, Codex, Cursor, Copilot, and more. The line from your team page also adds the team's MCP servers and skills.

    curl -fsSL https://getspawnpoint.com/install | bash
  3. Say "deploy this"

    Each agent signs in once in the browser. After that, 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.

A team is your company's account. Everything its members build lives there.

One page for every app

The team page lists every app, who built it, and when it last changed, plus the MCP servers your agents can connect to. An MCP server is a small program agents can ask for things, like your CRM's numbers.

Shared files

The team space holds what every app and agent should know: this week's priorities, a customer list, a launch brief. Apps can read it and cannot change it.

Shared skills

A skill is a set of instructions for a task, like how the team writes its weekly report. One member's agent publishes it, and every member's agent can follow it.

One line sets up a new member

The team page gives each member an install line that adds the team's MCP servers and skills to their Claude Code or Codex. Each line works once, for 15 minutes.

One domain for the team

On the Team plan, team apps can also open under a domain your company owns, such as tracker.apps.yourcompany.com.

Admins run the team

Admins invite and remove people, manage the plan, and can delete any team app. A member can delete only what they built.

Everything an app needs, added by your agent.

Nothing to configure up front. When the app your agent builds needs something, your agent asks spawnpoint for it.

Its own address

Every project gets its own secure HTTPS link, on infrastructure we run for you. A page or a site is online within seconds.

The link stays the same

Deploy again and the same link shows the new version. If an update fails, the old version keeps running.

A database and file storage

A to-do app gets a Postgres database; a gallery gets a bucket. Your agent adds them when the app needs them. How it works

AI without a key

Apps can use open-source models running on spawnpoint's own servers: chat, summaries, images in, quick decisions. No provider account to make. Read more

Your own domain

Ask your agent to add it. It hands you the DNS records to create, and HTTPS is set up once they land. The spawnpoint link keeps working too.

Private to your company, until you say otherwise.

Your team opens it, nobody else

A team app opens for every member, and a personal one for its builder alone. Nothing goes public by accident, and nothing is found by guessing a URL.

Share past the team when you choose

Share an app with one person by email, or with everyone at a domain like @acme.com. They open it with a code sent to their inbox, and they never make an account.

No keys in the code

spawnpoint refuses an app or a skill with an API key written into it (AWS, Stripe, OpenAI, Anthropic, GitHub, and others). Every app runs on its own isolated machine.

Admins decide who is in

Admins add and remove people on the team page, and each change reaches that person's agents on their next request.

Free to start. $99 a month for a team of 10.

The free plan has no time limit, and you do not need a card to start.

Free
$0forever

For trying it with a few coworkers

  • One live app at a time
  • A team of up to 3
  • Unlimited sharing
  • A 512 MiB database
Start free
Business
Let's talk

Forward-deployed engineering for your org

  • A dedicated forward-deployed engineer
  • Full customization for your organization
  • Private infrastructure and SSO
  • Hands-on onboarding and support
Talk to us

Building on your own? Pro is $50 a month for one person: unlimited apps, and 3 that never sleep. Every plan is a flat monthly subscription with nothing to top up, managed or cancelled in the console. Idle apps sleep, so a quiet app costs nothing extra.

Common questions

What is spawnpoint?

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.

Who is it for?

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.

How does a team work?

Someone signs in with a work email and makes the team on the Team tab of the console. Anyone who later signs in with the same email domain joins it, or an admin invites people by email instead. 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.

Who owns what the team builds?

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.

Do people need to know how to deploy?

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.

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. Apps made with frameworks such as Next.js, Remix, Astro, and SvelteKit work too: spawnpoint runs the build and start scripts in the app's package.json. An app with a Dockerfile is built into a container on its machine, so compiled languages work too.

Can our agents share MCP servers and skills?

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.

Can our apps use AI without an API key?

Yes. spawnpoint runs open-source AI models itself. 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.

How does an agent connect?

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

curl -fsSL https://getspawnpoint.com/install | bash

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.

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.

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 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 covers one live app at a time and a team of up to 3. Team is $99 a month for up to 10 members, unlimited apps, and 10 apps that never sleep. Pro is $50 a month for one person. Business adds an engineer who helps build your first apps. Every plan is a flat monthly subscription with nothing to top up, managed or cancelled in the console.

Can we use our own domain?

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

What happens when nobody is using an app?

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 the Team plan, up to 10 apps can stay always on instead (3 on Pro), so nobody waits.

Can we take an app down?

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.

Give the tools your team builds one place to live.

Start a team, send your coworkers one line, and the next tool anyone builds is one the whole company can open.