Priya Nair
priya@acme.com
For Cursor
Deploy your Cursor project for your team
You built an internal tool in Cursor. TeamOnly puts it online at a private link that only coworkers can open, with their work Google or Microsoft account. No servers, no login code, no public URL.
01No servers
How to deploy a Cursor project without setting up servers
Most deploy guides start with “create an account on a hosting platform, connect a database, configure environment variables”. For an internal tool you can skip all of that.
TeamOnly is the server, the database, the file storage and the login, in one place. You run one command from Cursor’s terminal and get a link.
npx teamonly initAdded .cursor/rules/teamonly.mdcAdded the TeamOnly SDKCursor’s agent will follow these rules in this project.02Rules
Add TeamOnly rules to your project
init adds the instructions Cursor’s agent reads. They describe the one app shape TeamOnly runs (a React front end with a small API) and how to get the signed-in person, the database and files.
So when you ask for a feature, the agent writes code that deploys, instead of reaching for a database service or login library we don’t run.
03The loop
Build, deploy, share
- Build
Ask the agent for the tool. “A stock counter where anyone on the floor logs a count from their phone.”
- Deploy
Run
npx teamonly deploy, or ask the agent to. - Share
Send
stock.acme.teamonly.appto the team. Change it later and deploy again; the link stays.
04Login
Company login without writing any login code
Don’t ask the agent to write a login. TeamOnly checks it before your app runs.
Coworkers sign in with Google Workspace or Microsoft 365. Your app simply receives their name and email. Outsiders never reach your code at all. How company login works.
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.
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.
05Data
A database that’s already there
Every app gets its own database and file storage on its first deploy. The agent’s code saves to it through the TeamOnly SDK, and there is no connection string to paste anywhere.
API keys for other services go in with npx teamonly secrets set, never in the code.
How do I deploy an app I made in Cursor?
Run npx teamonly init once in the project, then npx teamonly deploy in Cursor’s terminal whenever you want the latest version online. You get a private link that only your coworkers can open.
Does it work with Cursor’s agent mode?
Yes. init adds a rules file the agent reads, so it builds apps in the shape TeamOnly runs. The agent can also run the deploy command for you.
Do I need a Git repo?
No. Deploy sends the app from the folder on your computer. Using Git is still a good idea so you can undo changes, but TeamOnly does not require it.
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.
Want to tell us what you are building? Use the longer waitlist form. Questions go to hello@teamonly.dev, and a person answers.