Welcome to LaunchVerseQuickstartDashboard OverviewImporting Projects
LaunchVerse ForgeScale-to-ZeroEnvironment Variable VersioningRollbacks & PromotionsPreview Environments
Helix CopilotEphemeral SandboxesAI Log Explainer
The LaunchVerse EdgeCustom Domains & TLSDomain PurchasingTwo-Factor Authentication (TOTP)IP Allowlists
Managed DatabasesDatabase Backups & RestoresLog DrainsObservability
Project GroupsRole-Based Access Control (RBAC)
Student ProgramDeveloper Streaks
AuthenticationProjectsDeploymentsDomainsDatabasesError Codes & Conventions
Changelog
Deployment GuideEnvironment Variables & SecretsTeam ManagementWeb ShellHow Builds Work (Forge)
JavaScript SDKPython SDK
API Reference (Redoc)

Project Groups

As your architecture grows from a single monolithic application into a series of microservices, managing individual projects becomes cumbersome. LaunchVerse solves this with Project Groups.

What are Project Groups?

A Project Group allows you to bundle multiple related LaunchVerse projects together (e.g., a Next.js frontend, a Go backend API, and a Python worker).

By grouping projects, you unlock several powerful organizational features:

    1. Shared Billing: All projects in a group share the same resource quotas and billing metrics.
    2. Unified Observability: View aggregated traffic, bandwidth, and error rates across the entire group.
    3. Bulk Deployments: Trigger a simultaneous redeployment of all microservices in the group with a single click.

Creating a Group

  1. Navigate to your Team Dashboard.
  2. Click on the Groups tab.
  3. Click Create New Group.
  4. Give your group a name (e.g., Production Stack).
  5. Select the existing projects you wish to add to the group.

Bulk Deployments

If you make a breaking change to a shared schema or dependency that affects multiple microservices, you can deploy them all at once.

  1. Navigate to your Project Group.
  2. Click Deploy All.
  3. LaunchVerse will enqueue builds for every project in the group simultaneously via the Forge Builder.

> [!NOTE]

> If one project in a bulk deployment fails to build, LaunchVerse will not automatically rollback the other successful deployments in the group. You must manage cross-project rollbacks manually if strict atomic deployments are required.

Edit this page on GitHub↗