Skip to main content

​
What this unlocks

Rushed can now move beyond frontend-only projects when the app needs live product behavior. That includes:
  • sign-in
  • saved data
  • uploads
  • realtime updates
  • server-side logic

​
How backend setup works

When your prompt clearly asks for backend features, Rushed can:
  1. provision a managed backend
  2. connect the generated app to it
  3. store platform-managed values automatically
  4. show the backend dashboard inside the project
You do not need to manually create the backend project first.

​
What shows up in Env Variables

Project settings now include an Env Variables section. There are two main kinds of values:
  • platform-managed values that Rushed adds automatically
  • user-required values that you need to supply for outside services
Platform-managed values are hidden and not editable in the settings UI.

​
When Rushed will ask you for keys

Rushed only interrupts you for values it cannot generate itself. Examples:
  • GOOGLE_CLIENT_ID
  • GOOGLE_CLIENT_SECRET
  • RESEND_API_KEY
  • STRIPE_SECRET_KEY
If those are required, the app will show a setup prompt and tell you exactly which keys are missing.

​
Frontend env naming by framework

Rushed uses framework-appropriate public env names:
  • Next.js uses NEXT_PUBLIC_
  • Vite uses VITE_
  • Astro uses PUBLIC_
That means generated apps stay aligned with the framework they were built for.

​
Best practice

Ask for product behavior, not implementation trivia. Good prompts:
  • Add Google sign-in and save each user’s profile
  • Connect this dashboard to live task data
  • Replace the mock calendar data with real saved events
Less useful prompts:
  • Add some backend stuff
  • Make this more fullstack
The clearer the product need, the cleaner the setup flow.