Build internal tools with Claude Code, Codex, Cursor, and other coding agents. Deploy them behind your company login.

Share the tools you vibe-code like you share a Google Doc.

claude mcp add wirl -- npx -y @wirl/mcp

Run this once. Unless this computer is already signed in with npx wirl login, the first time your agent needs your wirl account it shows you a link and a code: approve the code in your browser. No agent yet? Join the waitlist.

How it works

Your people build the tool with the agent they already use. Wirl hosts it behind your company login, and IT can see all of it.

  1. Ask your agent

    Anyone describes the tool they need to Claude Code, Codex or Cursor, and the agent builds it.

  2. Tell it to deploy

    Wirl hosts it at its own link. Keys go into a vault in the browser, never into the code.

  3. Your company opens it

    Coworkers sign in with the Google work account they already have. Nobody outside gets in.

For the people who build

Ship the tool today, not after a ticket.

  • No servers, DNS or login code to set up.
  • Company-only from the first deploy.
  • Keys in a vault, never in the code or the chat.
  • A deploy that fails in its first half hour rolls itself back.
  • Anyone who can open it can pull the code and ship a change.
For the people who run IT

Every internal app, in one place.

  • Every app that is running, who built it, and with which agent.
  • What each app connects to, and who can open it.
  • A log of every call an app makes, by host.
  • Nothing to configure per app: company-only is the default.

Right now, internal tools live wherever they can.

  • On someone's personal Vercel account, with a Stripe key pasted in.
  • On the intern's laptop, until the intern leaves.
  • In a pull request, waiting for an engineer to find time.
  • On a public URL that was never meant to be public.

Nobody has the list, and nobody knows which of them can read customer data.

  • Someone's personal Vercel
  • The intern's laptop
  • A PR waiting on an engineer
  • Public by accident

Wirl is a secure cloud for vibe-coded internal tools.

Your people deploy from the agent they already use. Each tool gets a company-only link, its keys stay in a vault, and IT sees every app in one place: who built it, what it connects to, and who can open it.

Your company's Google sign-in, on every app.

One work Google sign-in and your whole company is in. The first person creates its space.

Sign in with GoogleChoose an accountto continue to supplier-paymentsPriya Nairpriya@acme.coTom Abaratom@acme.coUse another accountNo invites

Company-only by default.

The builder can narrow it to named people, or open it up.

acme--supplier-payments.wirl.runOnly peopleat acme.cocan open this.alex@gmail.comWho can opensupplier-payments?Everyone at acme.co+209Only these peopleAnyone with the link

Keys go into a vault.

A person types each key into their own browser, straight into Wirl's vault. Never into the code, never through the agent.

pay.tsnew Stripe(env.STRIPE_KEY)// no key in hereapp.wirl.devKeys · supplier-paymentsSTRIPE_KEYSave to vaultAGENTNEVERSEES ITSaved to vault

Bad deploys undo themselves.

A deploy that fails in its first half hour goes back to the last healthy version, and the log says so.

v3Supplier paymentsv4Supplier payments5005 failures in 12 minROLLED BACKLive
09:41 wirl rolled supplier-payments back to v3

Share the link or the code.

Anyone who can open an app can pull its source, change it, and ship it again.

$ npx wirl pull supplier-payments

Same thing on your laptop. npx wirl dev gives you the same identity headers and API access locally as in production.

acme--supplier-payments.wirl.runPriyaCopy linkCopied!Tom's laptop$ npx wirl pull supplier-payments✓ pulled v4$ npx wirl devv5Supplier paymentsExport CSV

Admins get the complete view.

Every internal app on one screen.

  • Who built it, and with which agent.
  • What data it connects to.
  • Who can open it.
  • When it was last used.
  • Every call it makes, logged by host.

Questions people ask.

What is Wirl?

A place to host the internal tools your people build, behind your company's Google sign-in by default.

Does it work with AI coding agents?

Yes. Claude Code, Codex, Cursor, anything that speaks MCP.

Who can open an app?

Everyone at your company, unless the builder narrows it to named people or makes it public.

What does the log record?

Who deployed, shared, opened, was refused, changed a key, or was removed, and what each app called, by host. Never request contents, never a key.

Is it a Vercel replacement?

For internal tools, yes. Vercel is still for the site you show the world.

When can I use it?

Private beta now. Connect your agent and deploy something, or leave your email.

Let your people build.

Private beta. Leave your email and we'll get you in.

Private beta. No spam, no drip campaign.