Multi environments management on App Platform

Hey Stany,

In App Platform, each App acts as an isolated deployment unit, so if you’re looking to run production, staging, and development environments, the recommended approach is to create a separate App for each environment, for example: myapp-dev, myapp-staging, and myapp-prod.

This isn’t just specific to App Platform, it’s actually how most platforms handle multi-environment setups. It gives you clear separation of resources, which becomes really important once your app grows.

Can you share why would you want all apps to run under the same App?

A few reasons why separate Apps per environment are preferred:

• Clean separation of env vars and secrets as you don’t want your dev instance accidentally connecting to a production database.

• Also better security, staging or dev components are often more exposed for testing, so keeping them isolated ensures they don’t impact production.

• The cost should be the same, since each App can be as lightweight as you need (e.g., a static component or a small backend), the pricing ends up being the same whether you split them up or pack everything into one App.

• You also get easier management, individual logs, deploy history, scaling, and rollback controls per environment.

Technically, yes, you can create multiple components inside a single App and wire them up to different branches (like one static site for main, one for develop), but it quickly becomes confusing and harder to reason about, especially with shared resources.

So if you’re planning to keep things clean, scalable, and secure, separate Apps per environment is the way to go.

- Bobby