OpenApps: Poof’s new name, same apps, Bounded underneath

If you already shipped on Poof, nothing is getting turned off. Same URLs, same CLI, same Discord. The name on the door is OpenApps now. Bounded is the extra door: your own agent writes the app, with rules that survive a bad prompt.

The live builder is still poof.new. The note for people who already shipped is bounded.sh/poof. openapps.xyz is the new brand, still a teaser.

What did not move

Draft, mainnet preview, and live deployments keep the URLs they have today. Credits and billing are unchanged. You still prompt, iterate, and publish in the same product. CLI and MCP keep working on those apps. Discord and [email protected] are still support.

If you paid for Poof credits or a membership, Bounded is on them. No form, no promo code. Email from any address, send your Poof wallet and an app name or URL, they size a Bounded account to what you were actually building. The Poof account stays untouched either way.

What Poof still is

Describe a Solana app in English. Poof’s orchestrator builds schema, policy, UI, sample data, and a preview. Iterate in chat. Checkpoints on every deploy. Plan Mode for changes you want to argue with before they hit the environment.

The on-chain twist is a policy engine: business logic in composable policies, not a new Anchor program per app. Plugins cover tokens, Pump-style launchpads, Jupiter swaps, Meteora pools, Metaplex, Phoenix perps, Pyth, ORAO VRF, Workers AI. Hosting is Poof Cloud. Test on Poofnet, then Mainnet Preview (real Solana, limited to 10 wallets), then mainnet. Seeker path: TWA APK around the production URL, bundle id like com.poof.*, no Android Studio.

Sign up with Phantom, Solflare, Backpack, or email (managed wallet, export later). Docs: poof.new/docs. CLI and AI-agent pages are in that tree.

Bounded: your agent, fail-closed writes

Bounded is a full-stack builder and runtime for coding agents. One prompt installs the CLI and skill into the agent you already use. Project files land in your repo. The governed core is policy.json.

• Rules answer who may act. Each action (read / create / update / delete) is a boolean. Denied write is 403 policy_denied. Denied read looks like an empty 200. Omitted actions deny.
• Invariants answer what must hold across a transaction: caps, conservation, tenancy. They are postconditions. Supported invariants are checked by a Z3-based prover before deploy and enforced atomically at runtime, including writes an agent got wrong.

Formal verification covers the guarantees modeled in policy, not arbitrary UI. Bounded web hosting serves static / SPA / prerendered output. It does not run request-time SSR, RSC, or framework API routes. Put that layer elsewhere if you need it.

# Bounded: policy + governed runtime, then a static site on the same app
bounded deploy --create --name my-app --with-source
npm run build
bounded site deploy ./dist --app-id <id> --with-source

# Docs: bounded.sh/docs · llms.txt for agents

People and links

Resources

• Poof docs
• Seeker / dApp Store APK
• Bounded policy, invariants, CLI