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.
14 days free, no card. Pick the region each app runs in, anywhere we can reach.
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.
Any database, including yours
Already using Supabase, MongoDB Atlas, Firebase or the company database? Paste the connection string and you are done. Or ask us for Postgres, MySQL or SQLite and the app gets one, wired in for you.
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.
Bring your database, or let us hand you one
Most teams already have somewhere their data lives. If yours does, set the connection string like any other environment variable and there is nothing else to do. It stays encrypted, and the dashboard shows what an app is connected to without ever showing the credential.
If you do not have one, ask and the app gets its own, with the connection string already in its environment. No console to visit, nothing to copy across.
- Yours. Supabase, MongoDB Atlas, Firebase, Neon, PlanetScale, or the database your company already runs.
- Postgres. Managed by us, in the same region as the app.
- MySQL. Same deal, for the apps and agents that reach for it.
- SQLite. For a single-instance tool. We keep a backup for you and tell you exactly how recent it is.
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.
Unlimited builders. Unlimited users. Pay for the apps people use.
An app only counts if somebody actually opened it this month. Everything else is archived, kept safe and costs nothing.
Start free for 14 days
14 days of Team, no card required. Unlimited builders and users, 10 active apps, sharing on from the first minute. Subscribe when you are ready, in the product.
Already have tools on Lovable, Bolt, Replit or Base44? Run the free scan.
Team
billed monthly
For one company sharing tools internally.
- 10 active apps included, $6 per extra
- Only apps used this month count
- Postgres, MySQL or SQLite per app
- 5 GB storage, 50 GB egress
- 3 always-on apps, the rest sleep when idle
- Email support
Business
billed monthly
When IT needs single sign-on and an audit trail.
- 30 active apps included, $5 per extra
- Single sign-on and audit log with CSV export
- Second managed engine included
- 20 GB storage, 200 GB egress
- 10 always-on apps
- Priority support
Agency
billed monthly
For people building tools on behalf of clients.
- 3 client workspaces, $79 each after that
- 30 active apps pooled, $5 per extra
- Team allowance in every workspace
- Second managed engine included
- Hand a workspace to the client at any time
- Priority support
What counts as an active app
An app is active in a month if it received 10 or more requests from people signed in, or you deployed it. Health checks, uptime pingers, cron jobs, bots and anonymous traffic do not count. Your own use of your own tool does.
Everything else is archived. The code, the database and the settings are kept, the app stops running, and it costs nothing and does not count toward your allowance. Waking one takes a click and under a minute. The dashboard shows the request count for every app, so the bill is never a surprise.
Apps untouched for 90 days are flagged for deletion with 30 days notice, and you can always extend. Archived apps still use storage, so storage still counts.
Fair use, in plain terms
Apps are meant for your own staff and contractors. Public-facing apps are allowed and count against egress. Bundling unrelated tools into one app to stay under the allowance counts as several apps, and we will ask before billing it that way.
Always-on is for tools that need to answer instantly during business hours. An app with no traffic for 14 days goes back to sleeping when idle.
New workspaces pay no overage for the first two billing months. Usage is capped at twice the allowance during that time and shown in the dashboard.
Unit pricing
| Unit | Team | Business | Agency |
|---|---|---|---|
| Base, per workspace | $79 | $199 | $299 for 3 |
| Builders and users | Free, unlimited | Free, unlimited | Free, unlimited |
| Active app beyond included | $6 | $5 | $5 |
| Always-on app beyond included | $7 | $7 | $7 |
| Storage beyond included | $1 per GB | $1 per GB | $1 per GB |
| SQLite storage beyond included | $0.50 per GB | $0.50 per GB | $0.50 per GB |
| Second managed engine | $9 per month | Included | Included |
| Egress beyond included | $0.12 per GB | $0.10 per GB | $0.10 per GB |
| Additional region | $49 | $49 | $49 |
| Additional workspace | n/a | n/a | $79 |
A larger database instance is quoted in the dashboard. Annual billing covers the base price; apps, storage, egress, always-on and regions stay monthly.
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.