SECURITY
The controls live outside the code an agent writes.
Sign-in, group access, secrets and ownership are handled by the platform. The app inherits them when it deploys.
Where does it run?
On our infrastructure, isolated per company.
What's reachable from the internet?
Nothing, unless an admin makes a specific tool public.
Where do secrets live?
Managed storage, injected at runtime, never in the repo, never in generated code. Values are masked in the console and revealing one needs admin approval.
What do you log?
Deploys, access changes, and sign-ins to tools. We don't monitor employees and we don't read tool data.
Who can see the code?
Your GitHub org if you connect it; otherwise the author, the owners, and our build systems.
Compliance?
SOC 2 is in progress and not yet complete. We'd rather say that than imply otherwise.
SECRETS, AS THE CONSOLE SHOWS THEM
3 keys moved out of source code by aidrop Deploy
CONTROL
One list. Every tool your company has built.
Owners, not mysteries.
Who made it, who can open it, when it was last used.
Dormant tools surface themselves.
Nothing runs unnoticed for a year.
Unowned tools are flagged.
The author left; the tool didn't.
The inventory is yours.
Export it to CSV, JSON or a Google Sheet, or pull it from the API.
Rules, not vigilance.
Who may deploy, what needs approval, when access expires — set once in the console.
TOOL DETAIL
WHEN SOMEONE LEAVES
DCD. ChenSuspended in Google Workspace
Access removed automatically12 tools
Needs a new owner3 tools
interview-schedulerM. Okonkwo
offer-letter-draftS. Patel
headcount-planA. Whitfield
Transfer all to…
EXPORT
CSV
JSON
Send to Google SheetsInclude access lists
ExportAlso available via API.
Have a tool ready? Put it behind Google sign-in this month.
Private beta for Google Workspace teams. No newsletter.