OurToolsPut the app your team built behind company login.
Someone on your team built something useful with an AI coding tool. Right now it is either on their laptop or on a public URL with a password taped to it. OurTools gives it a real address that only the right people can open.
No credit card. Pick the region each app runs in, anywhere we can reach.
$ ourtools deploy
detected Next.js, building in us-east1
uploaded 412 KB, build 00:47
https://quarterly-planner.ourtools.app
access: workspace, view
$ ourtools share quarterly-planner --user [email protected] --edit
[email protected] can now edit. She will sign in with Google.Three steps, then it is just a link
The whole point is that nobody has to learn a deployment platform to share the thing they built.
Point it at your code
Drag in a folder or a zip, run one command, or let your coding agent deploy for you.
We build and run it
Static sites, Vite, Next.js and single-file Python. The app sleeps when nobody is using it and wakes on the next request.
Choose who gets in
Send the link to one colleague or the whole company. Change your mind later and it takes effect in seconds.
What you get
Everything here exists because a tool built in an afternoon still ends up holding real company data by Friday.
Login is not your problem
Google and Microsoft sign-in is enforced at the edge, before a request ever reaches the app. The code your team wrote does not contain a single line of auth.
Sharing that IT can approve
Private, whole workspace, or a named list of people. View or edit. Every open is written to an audit log your admin can export.
Your region, your rules
Choose where each app runs when you create it, from dozens of regions across North America, Europe, Asia, South America, Africa and Australia.
A database when you want one
Ask for Postgres and the app gets its own database with the connection string already in its environment. No dashboard, no copy and paste.
Versions and a way back
Every deploy is a version. Roll back in one click. A build that fails never replaces the version that works.
One kill switch
An admin page listing every tool in the company, who can reach it, and a button that stops any of them in seconds.
Run it where the data has to live
Pick a region per app, not per account. A team in New York and a team in Frankfurt can each keep their tool close to home, under one workspace and one bill.
- South CarolinaUnited States
us-east1 - OregonUnited States
us-west1 - LondonUnited Kingdom
europe-west2 - NetherlandsNetherlands
europe-west4 - TokyoJapan
asia-northeast1 - SingaporeSingapore
asia-southeast1 - SydneyAustralia
australia-southeast1 - Sao PauloBrazil
southamerica-east1
43 regions in total. Change your mind and redeploy somewhere else.
Built so your security review is short
The reason internal tools end up on public URLs is that doing it properly used to mean writing auth. Here it is a property of the platform, not of the app.
We publish what we do and what we have not built yet. Ask us for the threat model and we will send it.
- Apps have no public address of their own. The only route in is the proxy that checks your identity first.
- The proxy strips any header a caller tries to forge and passes the verified user to your app.
- Environment variables are encrypted before they are stored and are never returned by the API after you write them.
- Deploy, share, access, rollback and kill are all written to an append-only audit log.
- Uploads are size capped and every archive entry is checked for path traversal before it is opened.
- Admins can revoke a person, an app, or a whole workspace without touching the code.
Free for you. Paid when you share it.
Deploying is never gated. You pay the first time you want somebody else to be able to open it.
Team
- Everyone in your workspace
- Unlimited apps and sharing
- Audit log and CSV export
- Managed Postgres per app
- Region choice per app
Agency
- Multiple client workspaces
- One bill for all of them
- Hand a workspace to the client
- Priority support
Tell us what your team built.
We are letting in a small group at a time so we can fix the build failures people actually hit. Send us a line about the tool you want behind login and we will get you in.