aidrop DeployRequest a pilot
HOW IT WORKS

A deployment path your company can live with.

Connect Google Workspace once. After that, the people building tools can deploy and share them from the AI coding client they already use.

0
ADMINONE-TIME

Connect Google Workspace and push the connector to your domain.

One admin, one screen, about five minutes. Nothing gets installed on anyone's laptop.

GoogleConnect Google Workspace
Admin consent · one screen
GoogleSign in with Google
Connect GitHub org
Optional
Authorize
Push the connector
acme.com · 214 seats
Deploy to domain
1
EMPLOYEE

They ask Claude Code to deploy it.

The connector is already there, so they write it the way they'd say it out loud.

>  deploy this and give the sales team access
2
AIDROP.IT

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.

>  deploy this and give the sales team access
builtnext.js · postgres
deployedpipeline.acme.aidrop.cloud
shared[email protected] · 14 people
loggedvisible in your registry
Ran from Claude Code. Nothing installed on the laptop.
3
EMPLOYEE

They share it by name.

[email protected], or one person by email. That's the entire permission step — there's nothing else to configure.

4
COLLEAGUE

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.

pipeline.acme.aidrop.cloud
GoogleSign in with Google
acme.com
5
YOU

It's in your list before she opens it.

Name, owner, who has access, what it's attached to — and one switch to revoke.

TOOL
OWNER
LAST OPENED
ACCESS
STATUS
pipeline-tracker
JRJ. Rivera
just now
sales@+14 people
live

Steps 1 through 5 take about a minute and happen without you. Step 0 is the only one you do.

IDENTITY
Google
Google Workspace
your directory, your groups, your MFA
aidrop Deploy
access plane
Your team's tools
pipeline-tracker, qa-triage, +32
sign-in, groups, offboarding
who can open what

One connection. Everything else follows from it.

An admin connects Google Workspace once. From then on aidrop Deploy uses the directory you already maintain — same accounts, same groups, same offboarding. No second user list, no new passwords for your help desk.

People are who Google says they are.
Sign-in is your existing SSO, including the MFA you already enforce.
Groups are the unit of sharing.
Share with [email protected] and a new hire in that group has access on day one.
Offboarding is one place.
Suspend someone in Workspace and access to every tool ends at once.
We never own your user list.
We read the directory. We don't replace it.
pipeline-tracker
Private
Add a person or group…
JRJ. RiveraOwner
sales@RemoveCan use
TLT. LindqvistCan use
Anyone at acme.com can open this
Public access is off. Only an admin can turn it on.
JRJ. Riverarequested 4 minutes ago
pipeline-tracker
wants to attachpostgres1 secret
SALESFORCE_API_KEY••••••••
ApproveDenyView the code diff
SHARING

As simple as sharing a doc. As controlled as you need.

Private by default.
A new tool is visible to its author and nobody else.
Share with a person or a group.
The recipient needs no account with us, no invite to accept, no password to create.
Two roles, not twenty.
Use it, or own it. Permission models nobody understands are permission models nobody configures correctly.
Revoke instantly.
Access ends the moment you remove it, mid-session included.
Public is a separate decision.
Exposing a tool outside the company is off until an admin turns it on, per tool.
Approvals where they matter.
Attaching a secret or going public can require a reviewer — everything else stays instant.
Individual shares can expire.
Group access follows the group; one-off shares can time out on a schedule you set.
CUSTODY

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.

No GitHub licenses required.
Commits carry the real author without consuming a seat.
One direction by default.
We deploy, GitHub mirrors. Two-way sync is opt-in, per tool.
Cancel and keep everything.
The repositories are in your org. They stay there.
ACME-TOOLS
pipeline-trackerprivate
Deployed by aidrop Deploy · authored by J. Rivera
JRJ. RiveraTypeScriptUpdated 2 minutes ago
qa-triageprivate
Deployed by aidrop Deploy · authored by M. Okonkwo
MOM. OkonkwoPythonUpdated 1 hour ago

Have a tool ready? Put it behind Google sign-in this month.

Work email only. We reply with pilot timing.

Private beta for Google Workspace teams. No newsletter.