Boogy
Your backend shipsas fast as your prompt.<br>Prompt an agent, get a full backend — REST, RPC, MCP, sandboxed DB and auth, deployed in seconds. Every iteration is instant. Fast, secure, free to start.
claude code<br>> Build me a bookmarks API with CRUD endpoints
I'll create a bookmarks API with full CRUD. Let me scaffold the Rust project and write the handlers.
Created src/lib.rs — BookmarksApi with Router<br>Created boogy.toml — store + auth capabilities<br>Building for wasm32-wasip2...<br>Compiled successfully.<br>Deploying to boogy.ai/my-app/api/bookmarks...
✓ Deployed. Live at /my-app/api/bookmarks
> Add a search method that filters by tag
I'll add a GET /bookmarks/search?tag= endpoint with a store filter query.
Updated src/lib.rs — added search_by_tag handler<br>Building...<br>Deploying...
✓ Redeployed. New endpoint live.
$ curl https://boogy.ai/my-app/api/bookmarks/search?tag=rust<br>[{"id":3,"url":"https://doc.rust-lang.org","tags":["rust"]}]
Two prompts. Two deploys. Zero infrastructure. 🚀💥
Vibe a node. Get a network.<br>Every API on Boogy is a node you can call — other devs', companies', and core services alike. Calls run in-process, not over the wire: no network hop, no SDKs, no keys to manage, just microsecond service-to-service latency.
// calls to other APIs on the mesh<br>peer::query("boogy://chainlink/oracle/price?sym=ETH")<br>peer::execute("boogy://venmo/payments/charge", order)<br>peer::execute("boogy://openrouter/chat/completions", prompt)
Blazing fast executionthousands of requests/sec per API<br>Zero-trust by defaultevery call carries identity, scope, audit<br>Per-API isolated DBtransactional, lightning fast, mistakes stay contained<br>Real code, no ceilingcode/Wasm, not no-code blocks
Get Started
Vibe a node. Get a network.<br>Every API on Boogy is a node you can call — other devs', companies', and core services alike. Calls run in-process, not over the wire: no network hop, no SDKs, no keys to manage, just microsecond service-to-service latency.
// calls to other APIs on the mesh<br>peer::query("boogy://chainlink/oracle/price?sym=ETH")<br>peer::execute("boogy://venmo/payments/charge", order)<br>peer::execute("boogy://openrouter/chat/completions", prompt)
Blazing fast executionthousands of requests/sec per API<br>Zero-trust by defaultevery call carries identity, scope, audit<br>Per-API isolated DBtransactional, lightning fast, mistakes stay contained<br>Real code, no ceilingcode/Wasm, not no-code blocks
claude code<br>> Build me a bookmarks API with CRUD endpoints
I'll create a bookmarks API with full CRUD. Let me scaffold the Rust project and write the handlers.
Created src/lib.rs — BookmarksApi with Router<br>Created boogy.toml — store + auth capabilities<br>Building for wasm32-wasip2...<br>Compiled successfully.<br>Deploying to boogy.ai/my-app/api/bookmarks...
✓ Deployed. Live at /my-app/api/bookmarks
> Add a search method that filters by tag
I'll add a GET /bookmarks/search?tag= endpoint with a store filter query.
Updated src/lib.rs — added search_by_tag handler<br>Building...<br>Deploying...
✓ Redeployed. New endpoint live.
$ curl https://boogy.ai/my-app/api/bookmarks/search?tag=rust<br>[{"id":3,"url":"https://doc.rust-lang.org","tags":["rust"]}]
Two prompts. Two deploys. Zero infrastructure. 🚀💥
Get Started
01 / The Runtime<br>A shared runtime<br>for everything you build.<br>Every API you deploy is a node anyone can call. Services call services, agents call APIs, apps stitch them together — and because calls dispatch in-process, not over the network , hops are microseconds, not milliseconds .
Identity, permissions, and audit ride every message automatically, so the whole mesh composes safely. A runtime that gets more powerful with everything shipped on it .<br>Unified identity — humans, agents, and services share one token format<br>In-process composition — cross-service calls are function calls, not hops<br>Organic growth — deploy one API today, a mesh of fifty tomorrow<br>Federation — the runtime spans machines without configuration changes<br>Unified identity — humans, agents, and services share one token format<br>In-process composition — cross-service calls are function calls, not hops<br>Organic growth — deploy one API today, a mesh of fifty tomorrow<br>Federation — the runtime spans machines without configuration changes
02 / Developer Experience<br>From idea to API<br>in minutes.<br>1 — Write your API<br>struct HelloApi;
impl Api for HelloApi {<br>fn build_router() -> Router {<br>Router::new()<br>.get("/api/hello", |_| {<br>Ok(Json(json!({"msg": "hello"})))<br>})
2 — Declare your manifest<br># boogy.toml<br>[api]<br>id = "hello"
[capabilities]<br>store = true<br>auth = true
[ingress]<br>mode = "authenticated"
3 — Build & deploy<br># Build<br>cargo build --target wasm32-wasip2 --release
# Deploy (single POST)<br>curl -X POST https://boogy.ai/v1/wasm \<br>-F manifest=@boogy.toml \<br>-F wasm=@target/wasm32-wasip2/release/my_api.wasm
# It's live under your handle (@my-app)<br>curl https://boogy.ai/my-app/api/hello<br>{"msg": "hello"}
— That's a deployed backend with its own database, auth, ingress policy, and...