Pebble is a home for small software: the tiny internal tools every team needs but nobody ships. An AI agent writes the tool as a plain folder, pebble ship deploys it into its own isolated microVM in under a second, and your teammates use it from a link after signing in with Google.

How is Pebble different from Retool or other internal-tool builders?

Internal-tool builders charge per seat — including viewers — and cap you at what their form builder can express. Pebble runs real code written by your agent in any shape, and pricing never counts the people who just use a tool.

Why not deploy to a normal cloud like Vercel or Cloud Run?

Big clouds are built for software with the public internet as its audience: IAM, Dockerfiles, YAML, DNS, cert config. A tool for eight colleagues doesn't justify that machinery. Pebble hides all of it — ship a folder, get a link, done.

Each tool runs in its own Firecracker microVM — hardware-level isolation, not a shared container. Outbound network is blocked by default; a tool that wants to call an external API must declare it, and you approve the diff at ship time. Access requires Google sign-in, and sharing is explicit: owner, org, or named people.

Small groups — a team, a family, a 10–200 person company. Pebble is small on purpose: a tool with three users is a success here, not a rounding error.

What can I build on Pebble?

Anything small and useful: trackers that replace a spreadsheet, dashboards over team data, scheduled reports that run themselves via cron wake-ups, little LLM-powered utilities. If your agent can write it as a folder with a run.sh, Pebble can run it.

Early access

Big clouds ship apps.
Pebble ships tools.

Your AI assistant writes the little tool your team keeps wishing existed — and ships it live in under a second, straight from the chat or with one command. Colleagues click a link, sign in with Google, and use it — no install, no explanation, no DevOps.

You don't have to be technical Connect your AI assistant to Pebble once — then just ask for the tool and it ships here itself. On claude.ai: Settings → Connectors → add https://shippebble.com/mcp. In Claude Code: claude mcp add --transport http pebble https://shippebble.com/mcp See how it works ↓

~/standup $ pebble ship --name standup
building… deps ok, disk sealed
✓ live in 0.59s
https://shippebble.com/t/standup/

~/standup $

…or the classic way, if the terminal is home to you

0.59 sship → live, measured

2.4 scold start from sleep

1 microVMper tool — real isolation

$0 / seatviewers are always free

The missing category

The most useful software is too small to ship

Every team runs on tiny jobs: the tracker living in a spreadsheet, the report someone assembles by hand each Monday, the script that only works on one person's laptop. Too small for the engineering backlog. Too useful to keep dying in a tab.

AI agents can write that software in minutes now. What's been missing is a place to run it — somewhere org-safe, shareable, and boring to operate. That place is Pebble: a platform built for small software, not scaled-down big software.

How it works

Folder in, link out

STEP 1

Your agent builds it

Tell Claude, Cursor, or ChatGPT what you want. Connected via MCP, your agent fetches Pebble's one-page contract itself — or you paste it in. The tool is a plain folder — no framework, no config maze.

standup/
├── run.sh        # starts the server
├── app.py        # the tool
└── pebble.toml   # optional: cron, egress

STEP 2

Ship it

One command from the folder — or no command at all: connect your AI and just say "ship it". Pebble seals the tool into its own microVM and hands back a URL in under a second.

$ pebble ship --name standup
✓ live in 0.59s
https://shippebble.com/t/standup/

STEP 3

Share it like a doc

Paste the link in chat. Teammates sign in with Google and it just opens. You decide who can use it — everyone in your org, or named people only — from the share panel, or by telling your assistant. The Google-Docs model, for tools.

share “standup”
● anyone at @yourco — can use
● dana@yourco.com — can use

Works inside your AI

Never leave the chat

Connect Pebble to Claude, Cursor, or any AI assistant that supports MCP, and the assistant does everything itself — builds the tool, ships it, shares it, even reads the logs when something's off. You just say what you want.

You Make us a receipt tracker — photo upload, monthly totals — and put it online for the team.

Your assistant Built it and shipped it to Pebble ✓
Live at https://shippebble.com/t/receipts/ — everyone at your company can open it after Google sign-in. Want me to restrict it to just the finance folks?

You Yes — finance only. And make the totals exportable.

Your assistant Done: shared with finance@ only, and v2 with CSV export is live. I kept v1 in history in case you want to roll back.

One-click connect. Add https://shippebble.com/mcp as a connector in your assistant — a Pebble sign-in pops up, you approve, done. No API keys, no config files.
Your assistant gets real hands. It can fetch the build rules, ship, share with people, tail logs, and restore old versions — the same powers as the command line, driven by conversation.
Guardrails stay on. If a tool wants internet access, the assistant must stop and ask you to approve the exact destinations. Isolation and quotas apply to AI-shipped tools exactly as to everything else.

claude mcp add --transport http pebble https://shippebble.com/mcp

…or on claude.ai: Settings → Connectors → Add custom connector → paste https://shippebble.com/mcp. Full setup guide

Why Pebble

Different offer, not a different flavor

Everything that exists wants your tool to be bigger than it is. Pebble is shaped around the truth that it's small.

Where tools live today	What it costs you	On Pebble
Internal-tool builders (Retool & co.)	Per-seat pricing — viewers included. Ten users of a tiny tracker ≈ $6k/yr. And you build inside their form builder, not with your agent.	Real code, any shape. Viewers free. Your agent writes it; Pebble just runs it.
Big clouds (Vercel, Cloud Run, AWS)	Built for the public internet. IAM, Dockerfiles, YAML, DNS, cert config — machinery an 8-person tool can't justify, exposed to whoever ships it.	All of that is hidden. Ship a folder, get a link. Auth, certs, and isolation are the platform's job.
Somebody's laptop (scripts, notebooks)	Dies when the lid closes. No auth, no sharing, no history — and one day its owner leaves.	Always reachable, never always-on. Tools sleep between uses, wake in 2.4s, keep their data.
Yet another SaaS (one subscription per problem)	Subscription sprawl. Your workflow bent to their product, your data in their hands.	Exactly your workflow. The tool is yours — fork it, version it, restore it.

Security

Safe by architecture, not by policy

Agent-written code should never be an act of faith. Pebble assumes the code might misbehave — and makes that boring.

One microVM per tool

Every tool boots in its own Firecracker micro-virtual-machine — the isolation technology behind AWS Lambda. Hardware-level walls between tools, not shared-container promises.

Network: off by default

A freshly shipped tool can reach nothing. If it wants to call an external API, it must declare the destination — and the human shipping it approves the exact diff. Exfiltration isn't a bug class, it's a permission.

Google sign-in, explicit sharing

Nobody touches a tool without signing in. Owners share like a document — the whole org, or named people. Every request reaches the tool with the verified user's identity attached.

Versions with instant restore

Every ship is a version, and each version snapshots the data beside it. A bad update is a one-command restore — code alone, or code and data together.

Small on purpose

Built for ten people, not ten million

A tool with three users is a success here. The economics work because tools sleep when idle and wake on click — dozens of tools share one small machine without stepping on each other.
No per-seat tax, ever. Charging per viewer punishes exactly the behavior a team tool exists for: being shared.
Made for small groups. A team, a family, a 10–200 person company — one drawer of tools everyone can open, and nothing you have to operate.

FAQ

Fair questions

What exactly is “small software”?

Software whose whole audience you could invite to lunch. It automates one real job for one real group — a tracker, a dashboard, a weekly report. It was never economical to build until agents started writing it, and never had a proper place to run until now.

Do I need to know how to code?

No. Connect Pebble to your AI assistant once (a settings click on claude.ai, one command in Claude Code), describe the tool you want, and the assistant writes it and ships it for you. Prefer doing it by hand? One installed CLI and one command.

How is this different from Retool?

Retool-style builders charge per seat — viewers too — and constrain you to their component library. Pebble runs arbitrary code your agent writes, and never counts the people who merely use a tool. Different economics, different ceiling.

What happens when nobody is using a tool?

It goes to sleep. Its data stays on a persistent disk; the next click — or its own cron schedule — wakes it in about 2.4 seconds. You get always-reachable without paying for always-on.

Can a tool leak our data to the internet?

Not silently. Outbound network is blocked by default at the platform level. A tool must declare every external destination it wants, and the person shipping approves that exact list. Changing the list requires re-approval.

Can my AI assistant use Pebble directly?

Yes — Pebble is an MCP server. Add https://shippebble.com/mcp as a connector in Claude, Cursor, or any MCP-capable assistant, approve the sign-in once, and from then on the assistant can build, ship, share, debug, and roll back tools for you. To see what it can do after connecting, just ask it: "what Pebble tools do you have?"

Is Pebble finished?

It's in early access — the core is live and measured (sub-second ship, 2.4s cold start, isolation, sharing, versions, cron), and it's being piloted with real small groups. If that's you, sign in and try it.

Get started

Ship your first tool today

Using Claude or Cursor? Connect Pebble to your assistant: