Rocket

Use it when

You want to go from a product brief, Figma frames, or a UI screenshot to a working web or mobile app—with backend scaffolding and a path to staging/production—without rebuilding every screen by hand.

What it does well

• Build from natural language, Figma import, screenshots, Notion docs, or a Supabase schema—not only a blank prompt
• One-brief generation aimed at a full product surface: UI, feature set, SEO-ready copy, and framework code
• Backend-oriented setup: schemas, auth, API hooks, and connectors (e.g. Supabase, Stripe) in the Build flow
• Ship path: GitHub sync, staging/production, Rocket hosting or custom domain, plus downloadable source
• Team workspaces with role-based access and pooled credits; Solve and Intelligence available beside Build when you need research or competitor signals

Skip it when

• Free is explore-only: about 20 one-time credits—enough to try a small app or a few landings, not heavy production volume
• Capacity snapshot (platform fee, unlimited members): Pro ~100 credits/mo; Rocket plan ~250/mo with deeper Solve/Intelligence; Booster ~1,500/mo. Extra credits can be bought and do not expire—confirm live Pricing
• Large multi-screen apps burn credits fast—budget generation like compute
• You only need UI markup without an app backend (Codia) or a hosted screenshot-to-site builder (Fronty)
• You need a logo/brand-kit studio, or enterprise SSO/data localization on self-serve tiers (those need sales)

Fits your workflow

Import Figma or drop a screenshot/brief into Build → iterate in chat → connect data/auth → sync to GitHub or download source → deploy on Rocket hosting or your domain. Finish architecture and security review in your normal engineering stack. Use Solve first when the problem is still “what to build.”