Your agent builds the app. Bounded runs it.

Bounded is the full-stack app builder and runtime for oApps: the apps your coding agent builds and ships. UI, auth, data, server functions, AI, payments, realtime, and hosting on one deploy. Everything you would build on Supabase or Convex, made for the agent era.

One prompt sets up Bounded in Codex, Claude Code, or your agent

Book a demo

Your AI-built app needs more than code.

It needs a real interface, data and files, login, server-side functions, AI and service calls, realtime updates, payments, and a real URL. It needs rules it cannot break once real users and agents start writing to it. Your agent gets all of it on one app through a connected build and deploy workflow.

  • FrontendBuild the web or React Native interface and connect it with @bounded-sh/client.
  • Data & filesSave users, teams, tasks, messages, files, searchable content, balances, and app state.
  • AuthDecide who can see and do what: users, sessions, roles, guests, OAuth, email OTP.
  • RealtimeLive queries that update the moment a write lands.
  • FunctionsServer-side TypeScript with secrets, scheduled jobs, hooks, webhooks, and service calls.
  • HostingA real URL: static UI hosting, custom domains, dashboard, CLI, and SDKs.
  • PaymentsAccept money, track balances, enforce budgets, and move value through rules.
  • Live stateFast room state for presence, cursors, server ticks, and multiplayer views.
  • AI servicesModels and managed third-party APIs, called from server-side functions on a budget.
  • BoundariesData rules are enforced on every write. Routed agent actions can be watched, approved, or enforced.

Realtime, at full speed.

A collaborative canvas and a live arena, running off the same store: live queries, presence, server-authoritative ticks.

workspace · doc reviewlive queries · presence
arena · lightcyclesserver ticks · RAM-speed

One store underneath. Every query live, every room server-authoritative.

AI, payments, and integrations on the same app.

Connect card payments with a login, accept direct USDC, and use the models and integrations enabled for the app. Provider credentials stay out of client code; cost-bearing work keeps explicit limits.

PaymentsUse beta Bounded Pay for Stripe Connect card checkout, or accept USDC directly to your wallet.
AI modelsCall beta managed models from server-side functions without a provider key in client code; verify each paid route before production.
IntegrationsInvoke enabled third-party tools by name. Credentials stay in managed service configuration; define action limits explicitly.

Reduce provider setup. Keep explicit boundaries.

Safe changes move. Dangerous actions fail closed.

Your rules are declared in policy, checked against every possible request before deploy, and enforced fail-closed at runtime. Tests check what you thought of. Proofs check what you didn’t.

Reminders don’t stop anything. Promoted data boundaries and matched routed actions are enforced at their documented runtime seams.

How it works.

You build in Claude Code or Codex, like always. Bounded runs the app: frontend, backend, and the rules that keep it safe.

01 Paste the prompt, describe your app

Copy the setup prompt into your agent and say what you want. It builds the app and Bounded deploys it, frontend and backend, at its own URL.

[pasted the Bounded setup prompt]
an expense splitter for the ski trip. balances must always net to zero
Built it · blocking policy checks passed · deployed → ski-trip.bounded.page

02 It’s live, with its boundaries in place

The app ships with the rules you stated already enforced. Review them, adjust them, or add more by prompting.

ski-trip.bounded.pagelive
  • mirapaid the cabin+$62.50
  • theoowes−$41.20
  • samowes−$21.30
group net$0.00 ✓
  • balances always net to zero
  • only members of the trip can add expenses

03 Iterate without fear

Keep prompting changes. You choose the mode: let edits evolve the boundaries, or lock them so no future change can weaken them. While they hold, runtime writes cannot cross the declared data boundaries.

add receipt photos to each expense
Deployed · blocking checks passed · live in 96s
seed demo data where the group nets +$40
REFUSEDcrosses boundary net_zero

Create your own →

for agents

Give agents limits so you can give them work.

Route the consequential actions through Bounded. Every action is recorded, checked against your boundaries, and either allowed, routed for approval, or declined before it fires.

  • refunds
  • credits
  • payouts
  • deletes
  • exports
  • role changes
  • model calls
  • × unlimited authority
Bring us one action

Cross the boundary.

One prompt installs the CLI and points your agent at the machine docs (llms.txt).