Vibe whole apps into production.
Frontend, API, and data from one Rust crate compiled to wasm32-wasip2 — on a shared runtime with an isolated transactional store, capability security, and transactions that span services.

Developer hub · API reference · boogy.ai

flowchart TB
  client(["Client · browser · agent"])

  subgraph host["Boogy runtime"]
    direction TB
    edge["HTTP edge<br/>auth · ingress · rate limit · CORS"]
    sched["Fair scheduler<br/>per-owner budgets · backpressure"]
    inst["Your service<br/>Rust to wasm32-wasip2"]
    edge --> sched --> inst
  end

  store[("Per-service<br/>transactional store")]
  peer["Other services<br/>(the mesh)"]
  ext["Third-party APIs"]

  client -->|"request"| edge
  inst -->|"REST · JSON-RPC · MCP"| client
  inst -->|"store"| store
  inst -->|"peer::fetch"| peer
  inst -->|"outbound_http"| ext

You write handlers; the runtime gives each service a route subtree, an isolated relational, ACID store, a set of capabilities it must declare, and REST / JSON-RPC / MCP surfaces. Services call each other in-process — and a single transaction can span that whole call tree.

→ Developer hub routes you to the docs, skills, and catalog.

Coding agents — zero install. Connect to Boogy's public, anonymous MCP server at https://boogy.ai/mcp (e.g. claude mcp add boogy https://boogy.ai/mcp). It serves guidance (get_started, get_skill, manifest_reference), host-truth validation (validate_manifest, check_service), and device-flow sign-in (login shows the user a link to click; they sign in and the token returns to the agent — no CLI needed for auth). After login, deploy via the CLI (boogy deploy), the /v1 REST API, or the authenticated admin MCP. Building in a repo you'll revisit? boogy skills install vendors the skills into your project.

_{MIT OR Apache-2.0}