Brod

Use cases

Internal apps teams run on Brod

Three small tools of the kind a coding agent can build in an afternoon, and what it takes to put each one in front of the right people.

Three worked examples

These pages are for someone who already has an app working on their laptop, built with Claude Code, Cursor, Codex or another agent, and now needs to give it to a team without opening it to everyone.

Each one walks through a real shape of tool: who uses it, which parts of Brod it leans on, a prompt you can give your agent, and a short piece of server code.

What they have in common

  • Deployed over MCP

    The agent deploys the app to Brod over MCP and gets back a private HTTPS address.

  • One sign-in

    People sign in once to the workspace. The app reads who they are and their role from request headers, so it has no login page or user table.

  • Own data

    Each app with server code gets its own SQLite database, key-value store and file storage. No app can reach another's.

  • Sharing needs a person

    Opening an app to more people waits for a person to confirm. An agent cannot do it alone.

  • Versions and rollback

    Every deploy is a numbered version, updates go to staging first, and rollback takes effect on the next request.

If your app is not one of these, the internal tools overview covers what Brod gives every app and what it does not run.

Your AI already built the app. Put it in your team's hands.