---
title: "Platform Ops"
canonical_url: "https://flowfuse.com/handbook/engineering/ops/"
---

> Index of every page on this site: [llms.txt](https://flowfuse.com/llms.txt)

# Platform Ops

- [Observability](https://flowfuse.com/handbook/engineering/ops/observability)
- [Staging Environment](https://flowfuse.com/handbook/engineering/ops/staging)
- [Production Environment](https://flowfuse.com/handbook/engineering/ops/production)
- [Deployment](https://flowfuse.com/handbook/engineering/ops/deployment)
- [Incident Response](https://flowfuse.com/handbook/engineering/ops/incident-response)
- [FlowFuse Dedicated](https://flowfuse.com/handbook/engineering/ops/dedicated)
- [Updating Stacks](https://flowfuse.com/handbook/engineering/ops/production-stack-update)
- [Self Hosted Assistant](https://flowfuse.com/handbook/engineering/ops/self-hosted-assistant)
- [Certifed Nodes](https://flowfuse.com/handbook/engineering/ops/certified-nodes)

## CI/CD

As part of our CI/CD pipeline in our [@flowfuse/flowfuse](https://github.com/FlowFuse/flowfuse/) repository, we perform the following actions when code is merged to the `main` branch:

1. Several backend and UI tests are executed against the code by [this pipeline](https://github.com/FlowFuse/flowfuse/blob/main/.github/workflows/tests.yml)
2. Once all tests complete with success, [FlowFuse npm package](https://www.npmjs.com/package/@flowfuse/flowfuse) is built and published to the npm registry with a `nightly` tag by [this pipeline](https://github.com/FlowFuse/flowfuse/actions/workflows/publish.yml).
3. [FlowFuse npm package](https://www.npmjs.com/package/@flowfuse/flowfuse) is built and published to the npm registry with a `nightly` tag by [this pipeline](https://github.com/FlowFuse/flowfuse/actions/workflows/publish.yml).
4. The same pipeline triggers another action, responsible for [building a container image](https://github.com/FlowFuse/helm/actions/workflows/flowforge-container.yml)
5. Container image build pipeline uses [flowfuse npm package](https://www.npmjs.com/package/@flowfuse/flowfuse) created in step 1 (tagged as `nightly`) to build a fresh container image
6. The resulting image is used to perform deployment on both staging and production environments.

You can read more about our various environments here:

- [Pre Staging](https://flowfuse.com/handbook/engineering/contributing/#test-changes-in-staging) - used for each individual pull request as part of the code review process.
- [Staging](https://flowfuse.com/handbook/engineering/ops/staging) - triggered by merge to `main` branch, used for testing the full application, without fear of damaging the production environment.
- [Production](https://flowfuse.com/handbook/engineering/ops/production) - the live environment that our customers use.

## Sitemap

See the full [sitemap](https://flowfuse.com/sitemap.md) for all pages.
