Canonical entity profile
What is Bounded?
Bounded is the full-stack app builder and policy-enforced runtime for coding agents. Build and ship a client-rendered web UI or React Native client with auth, governed data, files and search, server functions and jobs, realtime and live state, beta managed AI and third-party services, direct-USDC payment flows or card payments via your own provider, static web hosting, domains, deployment, optional action observability, and team governance under one app identity.
Bounded is not a general-purpose model. It is the full-stack app builder and runtime a coding agent uses to build the client, configure app services, verify modeled data guarantees, deploy, host a web UI, and keep iterating on one app.
Entity facts
Stable facts for people, search engines, and agents.
Canonical name
Bounded
Category
Full-stack AI app builder and policy-enforced runtime for coding agents
Primary audience
Coding agents and developers building new web or mobile apps
Core workflow
describe the complete app → build the client UI and policy.json → bounded verify → fix counterexamples → deploy the runtime and web site → exercise the full user flow and its boundaries
Web delivery
Built static UI → bounded.page or a custom domain
Mobile delivery
React Native client + Bounded services; native release stays external
Managed AI and services
Beta model, media, and enabled third-party API calls from Functions; paid routes require live release proof
Payments
Direct USDC on Solana, or a direct provider integration
Action Boundaries
Watching is visibility; enforced matched routed calls receive runtime verdicts
Team governance
Roles, approvals, audit trail, and action reporting on Team
Client package
@bounded-sh/client
Server package
@bounded-sh/server
Ownership identity
@user.id
Wallet identity
@user.address
What it provides
A complete app stack with one governed runtime.
- A web or React Native client connected through @bounded-sh/client, with built static web delivery on a bounded.page URL or custom domain.
- Structured data, end-user auth, files, search, Functions and jobs, managed AI and third-party services, payments, ordinary realtime subscriptions, and server-authoritative live rooms.
- Optional PII-safe action observability, enforced routed Action Boundaries, and Team governance with roles and approvals.
- Rules that decide who may read, create, update, and delete each path.
- Supported invariants for conservation, rolling sums, bounds, tenant tags, and tenant edges.
- A verifier that reports proof obligations and concrete counterexamples before deploy.
- A runtime that checks every write atomically, applies the relevant caller rule, and never lets a transaction violate an invariant.
Proof boundary
“Proven” has a deliberately narrow meaning.
bounded verify reports proof obligations and concrete counterexamples. bounded deploy re-runs the blocking proof gate server-side and rejects a policy whose blocking obligations are DISPROVED.
What can be established
- A supported invariant’s generated blocking proof obligations pass.
- The server-side deploy gate rejects a blocking DISPROVED policy.
- Applicable caller rules are enforced on direct writes; invariants are enforced on every runtime write path.
What must not be inferred
- Every product requirement is automatically formalized.
- Advisory findings or unsupported properties are proofs.
- Formal verification establishes arbitrary UI behavior or general application correctness.
- Using Bounded alone establishes legal, regulatory, scale, or compliance claims.
Official resources
Canonical sources
Canonical facts last verified · 2026-07-17