Show HN: TeamOnly, a place IT can approve for vibe-coded internal apps

Private hosting for internal tools built with AI

You built something useful with Claude Code or Cursor. Type one command and it is online at a private link that only your coworkers can open, with their work Google or Microsoft account or a code sent to their work email. We take care of the security. You don’t write any of it.

See how it works

No card needed for the trial. Then from $19 a month. You can deploy a few minutes after you start.

expenses.acme.teamonly.app

Staff only

Expenses

Signed in

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

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

Work accountSigned in

PSPriya

Work accountSigned in

LKLee

Work accountSigned in

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.

Replay

From one laptop to the whole team: one command, one link, and coworkers sign in with their work accounts.

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.

That includes the security. Sign-in, company-only access, who can open each app, keeping each app’s data separate and keeping your apps out of search engines: we handle all of it, and you write none of it.

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.

$npx teamonly deploy✔Bundled your app✔Database created✔Login set up for acme.com ✔Live at https://expenses.acme.teamonly.appOnly @acme.com accounts can sign in

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.

Replay

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

1Add TeamOnly

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

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

Change something later? Deploy again. Same link.

In Claude Code or Cursor, type “deploy this on TeamOnly”. It sets up the app, asks for your work email and the code we send you, and offers a 14-day free trial if your company isn’t signed up yet.

expensesYour tool.acmeYour company.teamonly.appThe locked door

Every step, from your laptop to your team

Signed in

?randomperson@gmail.comTurned away

a bot, no loginTurned away

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.

Replay

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

Coworkers sign in with the work account they already have: Google, Microsoft, or a code sent to their work email. 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.

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

A database

File storage

Secret keys

Company login

No setup

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.

Replay

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

Deploy receipt

Database ready

File storage ready

Secrets stored

Login on

No. 1

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.

Build me an expense approval tool for my team

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.

Replay

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

Share a Claude Code app with your teamClaude reads the skill file, writes the app, and can run the deploy for you.

Deploy a Cursor project for your teamThe same instructions, as rules Cursor’s agent follows.

Built it somewhere else?How to share any AI-built app with just your team, with every option compared.

06For IT

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

Access removed from 2 apps

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.

Replay

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

07Ideas

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

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

No. They sign in with the work Google or Microsoft account they already use, or with a code sent to their work 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.

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.

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.

Use your work email. We write rarely, and only when there is news worth sending.

Questions go to hello@teamonly.dev, and a person answers.

Valid for your company email domain only.