Private hosting for internal tools built with AI

Your AI-built tools.Team only.

You built something useful with Claude Code or Cursor. Type one command and it is online at a private link. Your coworkers sign in with the work Google or Microsoft account they already have. Nobody else gets in.

Use your work email. We are opening to a few teams at a time.

See how it works

acme.comStaff

Dana Okafor

Signed in

npx teamonly deploy Live at https://expenses.acme.teamonly.appOnly @acme.com accounts can sign in

01The usual way

You built it in an afternoon. Sharing it shouldn’t take a month.

It works on your laptop. Getting it to the five people who need it usually means a list like this.

  • A login system
  • A database somewhere
  • A server to keep running
  • A safe place for passwords and keys
  • A ticket to IT, and a wait
HandledWith one command

Dana built an expense tool that only runs on her laptop. She types one command, npx teamonly deploy, and gets a link: expenses.acme.teamonly.app. Three coworkers, Marco, Priya and Lee, open the link, sign in with their work account, and the same tool opens for each of them.

From one laptop to the whole team: one command, one link, and coworkers sign in with their work accounts.
An operations lead in a small warehouse office smiles at the expense approval tool on her laptop while a coworker in a hi-vis vest leans over her chair to look.

TeamOnly crosses that list off for you.

No servers to rent, no login code to write, no ticket to IT. It is for internal apps only, by design, so the only people who ever see your tool are the people you work with.

02Deploy

One command, one link

When your tool works, you type npx teamonly deploy. A minute later it has its own address that you can paste into Slack, Teams or an email.

A terminal. Someone types npx teamonly deploy. The app is bundled, a database is created and login is set up for acme.com. Then: Live at https://expenses.acme.teamonly.app. Only @acme.com accounts can sign in.

The deploy, start to finish. The link at the end is the one you send your team.
  1. 1

    Add TeamOnly

    npx teamonly init adds instructions your AI reads, so it builds the kind of app that deploys first time.

  2. 2

    Ask for the tool

    In plain English. "Build an expense approval tool" is a fine start.

  3. 3

    Deploy and send the link

    Change something later? Deploy again. Same link.

expensesYour tool.acmeYour company.teamonly.appThe locked door

Every app gets an address like this. Opening it without a company account gets you a sign-in screen and nothing else.

A door marked Staff only stands in front of the expenses app. Sam, signed in as sam@acme.com, is checked at the door and walks in. Next, randomperson@gmail.com and a bot are checked at the same door and turned away. They never reach the app, because the check happens at the door, before the app.

Someone with an @acme.com account walks in. A personal Gmail, a bot or a stranger is stopped at the door, before the app ever loads.
acme.comStaff

Sam Reyes

Signed in
gmail.comGuest

Unknown

Turned away

03Who gets in

Only your company gets in

Coworkers sign in with the work Google or Microsoft account they already have. No new account, no password to share, no extra seats.

Anyone else is turned away at the door, even if they have the link. The check happens before your app runs, so a mistake in your app cannot let a stranger in. A forwarded link is just a very nice sign-in screen.

How company-only login works

04Included

A database, file storage and secrets, already set up

Your tool needs to remember things. On the first deploy it gets its own database and a place for files, with nothing to sign up for.

API keys and passwords go in with npx teamonly secrets set, never in your code. Each app's data stays in that app.

On the first deploy, four parts snap into place around the app like pieces of a kit: a database, file storage, secret keys and company login. There are no setup steps.

On the first deploy, a database, file storage and secrets click into place. Nothing to configure.

Deploy receipt

expenses.acme.teamonly.app

  • Database ready
  • File storage ready
  • Secrets stored
  • Login on

No. 1

Live

05Your AI tool

Made for Claude Code and Cursor

AI tools are good at writing apps and bad at guessing where they will live. TeamOnly gives yours a short set of instructions, so it writes an app that fits: a simple front end, a small API, and our login, database and files already plugged in.

In an AI coding tool, someone types: Build me an expense approval tool for my team. The app's screen takes shape: a list of expenses, each with an Approve button. Then one command, npx teamonly deploy, and the tool is live at expenses.acme.teamonly.app.

A plain-English request becomes an app, and the app becomes a deploy.

06For IT

IT can see every app

People are already building these tools. Here they land in one place your IT team can see.

  • Every app, its owner, who can open it and when it last changed
  • Each app kept apart from the others: data, files, cookies and secrets
  • Sign-in checked before any app code runs

What IT gets, in detail

An app register for acme.com fills in row by row. expenses, owned by dana@acme.com, open to everyone at acme.com, last deployed today at 9:41. inventory, owned by marco@acme.com, open to 6 people, deployed yesterday. lookup, owned by priya@acme.com, open to priya, marco and 3 others, deployed October 21. requests, owned by lee@acme.com, open to everyone at acme.com, deployed October 18. Then marco@acme.com is offboarded and every line that gave him access is struck through.

The app list fills in as people deploy: app, owner, who has access, last deploy.

07Ideas

What people build

Small tools that one team needed and nobody had time to buy. Each one starts as a sentence like these.

  1. 01

    Expense approval

    For finance and every manager

    People upload a receipt, their manager approves or rejects it, and finance sees everything approved this month.

  2. 02

    Inventory tracker

    For the warehouse and the front office

    Track stock by bin. Anyone on the floor can log a count from their phone, and I get a list of what is running low.

  3. 03

    Request form

    For office managers and ops

    A form for equipment requests. It saves who asked, I can mark each one ordered or done, and people can check their status.

Planned pricing

Pricing

Builder $19 a month. Team $249 a month. People who just use your apps: free.

09FAQ

Questions people ask

All questions and answers

Do my coworkers need to make an account?

No. They sign in with the work Google or Microsoft account they already use for email. No new password, no invite to another tool, and people who only use your apps are not seats you pay for. How company login works.

Can someone outside my company open the link?

No. The link opens a sign-in screen, and only accounts on your company email domain get past it. A forwarded link or a personal Gmail account is turned away before your app loads.

Do I need to know how to code?

Not really. You describe the tool to Claude Code or Cursor, and the instructions TeamOnly adds to your project tell it how to build an app that deploys. You will type two commands, and we show you which ones.

Early access

Get on the list.

We are new and not open yet. Leave your work email and you will be one of the first teams to deploy.

Use your work email. We will write when your spot opens.

Want to tell us what you are building? Use the longer waitlist form. Questions go to hello@teamonly.dev, and a person answers.