Zero Infrastructure Overhead

A build starts with the versioned front-end foundation, loaded fonts, design tokens, chain-data helpers and one wallet component. The agent receives design guidance and chooses a palette suited to the request. Explicit user design choices steer those defaults.

The sandbox keeps generated code away from the host application. Its root filesystem is read-only and Linux capabilities are dropped; the project workspace is writable. Compiler and analyzer containers run without a network. The agent container uses Docker networking for model requests and other network tools.

The real provider key stays behind a credential proxy. The agent uses a scoped temporary credential, and generated user code receives no upstream model key. A saved hosted key is encrypted in storage; operators with the server and encryption material can access it. The connection form explains that custody before you save it.

Generated signing apps use the shared EVM wallet component. It discovers compatible injected providers, including Phantom, while WalletConnect depends on the platform's Reown configuration. Available providers and wallet chain support determine what the user can connect. The user approves their own app transactions in their wallet.

• Model connections and wallet behavior

The hosted builder can deploy its selected contract to Robinhood Chain testnet and record the address and transaction. It then attempts Blockscout source verification, builds the front end and publishes the resulting files at an apps.fletch.now address. Publication changes the served files atomically and records the HTTP check.

A failed edit preserves the previous published version. Files and the build record remain available for inspection. Mainnet availability, custom domains and checkout have separate status on the limits and roadmap pages.

• Deployment and payment availability
• Planned hosting and deployment options