Skip to main content
In this lesson, you’ll learn how to deploy a robust, production-grade Backstage instance. We’ll walk through three critical tasks:
  1. Configure PostgreSQL as your primary database instead of the default in-memory store (which is only suitable for local development).
  2. Enable user authentication to ensure that only authorized users can access your Backstage instance.
  3. Containerize Backstage with Docker for consistent, repeatable deployments across environments.
By default, Backstage uses an in-memory database meant for testing and development. For production, a managed PostgreSQL instance provides durability, scalability, and backup capabilities.
The image is a section introduction for "Setting Up Backstage for Production," featuring three steps: using a Postgres database, implementing authentication, and deploying with Docker.
Throughout this guide, you’ll also discover best practices for safely upgrading your Backstage instance whenever a new version is released, minimizing downtime and ensuring data integrity.

Watch Video