Your employees are building small tools with Claude Code. This is where they put them.
A sales lead asks Claude Code for a pipeline tracker. A minute later it's live at pipeline.acme.aidrop.cloud, the fourteen people she shared it with open it with their work Google account, nobody else can, and it appears in one list with everything else anyone has built.
Google Workspace
Claude Code
Cursor
CodexSet it up once. After that, none of it is your work.
Connect Google Workspace and push the connector to your domain.
One admin, one screen, about five minutes. Nothing gets installed on anyone's laptop.
Connect Google WorkspaceSign in with GoogleThey ask Claude Code to deploy it.
The connector is already there, so they write it the way they'd say it out loud.
It comes up with a URL.
Front end, back end, database and cron start together at pipeline.acme.aidrop.cloud. If an API key was sitting in the code, the deploy stops and Claude Code moves it into managed secrets first.
They share it by name.
sales@acme.com, or one person by email. That's the entire permission step — there's nothing else to configure.
She opens the link and signs in with Google.
No account to create, no invite to accept, no password. Anyone who wasn't on the list doesn't get a login form to guess at — they get told no.
Sign in with GoogleIt's in your list before she opens it.
Name, owner, who has access, what it's attached to — and one switch to revoke.
Steps 1 through 5 take about a minute and happen without you. Step 0 is the only one you do.
You can't block this, and blocking isn't the goal. It needs somewhere sanctioned to land.
One connection. Everything else follows from it.
An admin connects Google Workspace once. From then on aidrop.it uses the directory you already maintain — same accounts, same groups, same offboarding. No second user list, no new passwords for your help desk.
sales@acme.com and a new hire in that group has access on day one.It runs inside Claude Code.
aidrop.it ships an MCP connector. You install it once across the domain. After that, whatever your team writes — Next.js, FastAPI, Rails, Streamlit, a static page — goes live from inside the tool they're already working in. We don't generate the code and we don't change how anyone builds.
nothing to installThe login already exists. Nobody writes one.
The tool never sees an unauthenticated request. Everyone who opens the link signs in with Google first, and aidrop.it checks them against the access list before the page loads. Someone who wasn't given access doesn't get a login form to guess at — they get told no.
Connect your GitHub org and every tool lands in a repo you own.
Today this code lives on a laptop. Connect GitHub and each tool becomes a private repository in your organization, updated on every deploy, with the real author attributed. Your Dependabot, your code scanning, your branch protection and your audit log start applying to software that until now had no owner and no history.
Every line on the left is achievable today. That's the point — seven products, seven bills and three permission models, per tool.
One list. Every tool your company has built.
Send to Google SheetsConnect Google WorkspaceSign in with GoogleNothing to install on laptops, no change to how anyone works, nothing at all for the people who just open the tools.
Not a scanner.
We don't hunt shadow apps across your network. We give them a place to live where you can see them by default.
Not an app builder.
Your team keeps Claude Code and keeps their code. We generate nothing.
Not a replacement for your cloud.
When something needs real scale, we help you move it out.
Does this work if we're not on Google Workspace?
Do employees need a GitHub license?
What can they deploy?
Does it work with Cursor or Codex?
What if a tool becomes business-critical?
What does it cost?
Can we restrict who's allowed to deploy?
Is this available today?
Your employees have already started. Give it somewhere to land.
Private beta. We're onboarding the first 20 teams and working with each directly.