---
title: "Use solutions to manage your application lifecycle"
slug: "using-solutions-to-manage-your-application-lifecycle"
updated: 2026-04-29T16:23:52Z
published: 2026-04-29T16:23:52Z
canonical: "help.quickbase.com/using-solutions-to-manage-your-application-lifecycle"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.quickbase.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Use solutions to manage your application lifecycle

Application Lifecycle Management (ALM) is the practice of building, testing, and releasing app changes in a structured, controlled way—without disrupting users.

If you change a live app directly, you might run into problems such as:

- Schema updates that break apps and pipelines
- Connected apps that fall out of sync
- Changes that are hard to track
- Manual and risky recovery work

Quickbase helps you avoid these issues by using:

- Solutions—A container for related apps and pipelines
- Environments—The structure for publishing changes
- Versioning and rollbacks—The ability to restore a previous version

![Illustration of the application lifecycle process from development to production environments.](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/application-lifecycle-process.png)

Together, these features help you:

- Build and test changes safely
- Check your changes before users see them
- Release changes in a predictable way
- Keep related apps and pipelines working together

## Solutions

A solution is the unit of deployment in Quickbase. That means it acts as a container for everything that should move through environments together.

A solution includes:

- Apps
- Pipelines

If several apps and pipelines support one business process, place them in the same solution. This setup helps you keep them aligned as you move changes through environments.

Apps and pipelines can belong to only one solution. This rule prevents conflicts. For example, if the same app belongs to multiple solutions, environments become inconsistent when different teams publish changes.

Learn more about [solutions](/v1/docs/solutions)

## Environments

Environments represent stages of release:

- **Development**—Build and modify schema
- **Testing** (only available in Enterprise plans)—Validate and confirm changes
- **Production**—Live version used by end users

Changes move forward in order:

- Development → Production
- Development → Testing → Production

When you publish a solution, Quickbase applies a full update of that solution to the next environment.

> [!WARNING]
> Important
> 
> If you make manual changes in Production, the next publish from Development overwrites the Production schema. You may permanently lose any changes that were not tracked in Development.

Learn more about [creating environments](/v1/docs/create-environments-in-a-solution)

## Versioning

Solution versioning allows you to create snapshots of an entire solution and restore a previous state when needed. Use versioning to protect major changes, recover from deployment issues, or preserve known-good states.

Learn more about [versioning](/v1/docs/solution-versioning)