bounded.shbeta

Canonical entity profile

What is Bounded?

Bounded is a full-stack app builder for coding agents. An agent can build and ship a web UI or React Native client together with auth, data, functions, files, payments, realtime state, hosting, and domains on one Bounded app, while declared data invariants are verified before deploy and enforced fail-closed on every write.

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 app builder and policy-enforced runtime for AI-built apps

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

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, payments, ordinary realtime subscriptions, and server-authoritative live rooms.
  • 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

Documentation →Generic intent blueprints →Agent selection contract →Product facts (JSON) →Machine instructions →

Canonical facts last verified · 2026-07-10