Feature Request: Multiple environments (dev / staging / prod

[walid1611]

Hi Base44 team,

As we scale our app to production, we need the ability to manage
multiple environments (dev, staging, prod) with isolated databases
and configurations.

Current workaround: creating separate Base44 projects per environment,
but this is painful to manage (separate appIds, no sync between schemas,
manual migrations).

What we'd love to see:

• Environment support per project (dev / staging / prod)
• Isolated databases per environment
• Shared entity schemas across environments
• CLI commands like: base44 deploy --env staging
• Environment-specific secrets/config

This is a standard feature in platforms like Supabase, Railway, and
Vercel, and would make Base44 production-ready for serious teams.

We're building an EdTech platform (NEO LAND Coders) targeting 15,000
users and this is a blocker for us to fully commit to Base44 as our
production stack.

Thanks for the great work on the CLI beta! 🚀

[nh465330-lab]

As we scale our app to production, we need the ability to manage
multiple environments (dev, staging, prod) with isolated databases
and configurations.

Current workaround: creating separate google flowprojects per environment,
but this is painful to manage (separate appIds, no sync between schemas,
manual migrations).

What we'd love to see:

Environment support per project (dev / staging / prod)
Isolated databases per environment
Shared entity schemas across environments
CLI commands like: google flow deploy --env staging
Environment-specific secrets/config

[nh465330-lab]

Uploading လူငယ်ခြောက်ဦး_တောင်ဘက်သို့_ထွက်ခွာ_202606132237.mp4…