Private, without building a login.
The dashboard or calculator you made to stop doing something by hand. Name the people allowed in and everyone else gets a locked door.
The app was the easy bit.
You built the tool in an afternoon. Then came the actual project: accounts, passwords, password resets, who’s allowed to see what, and the quiet worry that you’ve got it subtly wrong and put company numbers on the open internet.
So don’t build any of it. Tell us which email addresses are allowed and we stop everyone else at the door — before your app is reached at all. Your code doesn’t need a concept of users, and there’s no shared password to end up in a group chat.
People you invite sign in with their own email, the same way you did. Take someone off the list and they’re out immediately.
- user accounts
- password hashing
- password resets
- session cookies
- login pages
- invite emails
- role checks
None of this is yours to build.
Authentication is where a working internal tool usually stalls — it turns an afternoon's work into a second project, and one you can get quietly, dangerously wrong.
- VPN
- IP allowlists
- SSO config
- a shared team password
- password managers
- “don’t share this link”
Access is enforced in front of your app, not inside it — so a page you forgot to protect is still protected.
Small tools that quietly save hours.
None of these need to be public, and none of them justify a real software project. Which is exactly why they never got built before.
Dashboards
Numbers pulled from the systems you already pay for, on one page, updated when someone opens it.
Calculators & quoting tools
The spreadsheet everybody has a slightly different copy of, turned into one page with one answer.
Forms that go somewhere
Intake, requests, checklists — collected in one place instead of in email, and saved properly.
Lookups
A search box over your own data, so nobody has to ask you to find something again.
Rotas & trackers
Who’s on what, this week, without another subscription.
Internal docs
A handbook or runbook that isn’t public, and doesn’t need an account to read.
Before you put company data in it.
How many people can I invite?
As many as you like, to as many tools as you like. Invited people are never metered and never counted — inviting the whole company costs exactly the same as inviting two people. Keeping something private is part of Grow; it isn’t available on Starter.
Do the people I invite need an agenthost account?
They sign in with their email the first time they open the link, and that’s the whole setup. They never see the tools you use to build, and they can’t deploy anything.
How safe is this, really?
The check happens at our edge, before the request reaches your app, so it doesn’t depend on your code being right. Nobody who isn’t on the list gets through, including someone who has the link. It runs over HTTPS, in Europe.
Can some parts be public and some private?
Per app rather than per page — so a public marketing site and a private admin tool are two apps. Your agent can put both in the same project so they stay together.
Can more than one of us change it?
Yes. Add colleagues to the account and they can deploy from their own agent, with a role that says how much they’re allowed to do. Grow doesn’t charge per person, so there’s no reason to share a login.
What if someone leaves?
Ask your agent to take them off. Access ends there and then — no password to change and nothing to remember to rotate.
Put the tool where your team can reach it.
Private from the first deploy, no login screen to build, and no charge for the people you invite.