Tell your agent to ship it

Patchy is a private cloud for your company. Anyone on your team asks their AI agent for a tool, and the agent builds it and publishes it to your cloud in one step. It opens with your company login, sees only what that person is allowed to see, and can be undone any time.

Start a pilotSee what it looks like

Works with the agent your team already uses. No servers to set up, no keys to hand out.

What your cloud looks like after a month.

Build what your team actually needs, not what a vendor guessed. Each tool has an owner, a name, a version, and a choice of who can see it: just you, your team, or the whole company.

Acme’s cloudone company, one login
  • Maya, sales
  • Maya’s agent
  • Rae, support
  • Rae’s agent
  • Dev, ops
  • Dev’s agent

An agent works as the person it belongs to. It can’t see or do more than they can.

Sales

Deal aging flag
v4Sales teamdetails
Flight watch
v1Sales teamdetails

Support

Escalation queue
v3whole companydetails
refusedExport every customer

Tried to read records its owner can’t see. Patchy said no, whoever clicked approve.

Ops

Onboarding tracker
v2whole companydetails
Dev’s vendor list
v9only Devdetails
Patchy, underneathwho you are, what you may see, what changed, and undo. The same for every tool.

Start with one tool. A personal one costs nothing to try; the good ones get shared with a team, then the company.

Everyone builds. Same door.

Whether a person writes the tool themselves or asks their agent to, it goes through the same one-step publish, and Patchy checks the same things every time.

  • A person and their agentMost of your team. They say what they need in plain words; the agent builds it on their laptop and publishes it as them.
  • A person who codesSame command, from their own machine or from CI. Every publish records which person and which machine it came from.
$ patchy publish
  • Checks that the tool only reaches what its owner is allowed to reach
  • Refuses anything that reaches further, no matter who approves
  • Shows the change to a person before it goes live
  • Keeps every version, with who published it and from where

Things your team never has to think about.

It’s real infrastructure. It just isn’t your job to run it.

  • a server somewhere

    Where it runs

    Patchy runs the tool while someone has it open and stops when nobody does. There is nothing to provision or keep alive.

  • another login

    Who can open it

    Your company login, the one people already have. Share a link and it just opens.

  • API keys in a spreadsheet

    Connecting your systems

    Your CRM, email, and database are connected once by an admin. Tools use them without ever seeing a key.

  • “who changed this?”

    Versions and undo

    Every publish is kept with its author. Undo is one move, and the record of what happened stays.

Patchy says no when it should.

The rules hold for a person and for their agent, and approval never overrides them. This is what makes it safe to let everyone build.

A tool tries toWhat happens
Read customers its user can’t see
refusedThe user is told plainly that this is their access, not the tool being broken.
Look something up in Salesforce or Gmail
loggedGoes through Patchy, as the person using the tool, and is written down: which tool, which system, which person.
Store a password or key
impossibleKeys live inside Patchy and are never handed to a tool. There is nothing for a tool to leak.
Change someone else’s tool
refusedOnly the owner can publish, undo, or change who sees it. An admin can hand a tool to a new owner, and that is recorded.
Ship a change
keptEvery publish is saved as a version with its author. Undo brings back the previous one; the history stays.

“Couldn’t we just vibe-code this ourselves?” Sure. You’ll get an app that demos well, beside your real systems, with its own login, a copy of your data, and a key somebody pasted in. Building the tool was never the hard part. Giving it your data without handing over the keys is.

Bring your messiest workflow.

We’re onboarding a small first group of pilot teams, working directly with the founders. A call to see if we fit, then we stand up your company’s cloud and help your team publish the first tools. Expect hands-on help, fast fixes, and the occasional bug. It’s early.

Email us about a pilot

You’re a fit if

  • A workflow your team actually runs lives in spreadsheets and DMs
  • People on your team already work with AI agents
  • You want a say in what this becomes