Patterns for BYO images, monorepos with uv, CI/CD, and multi-team resource management.
Project patterns
The rest of the user guide explains what Flyte can do. This section explains how we recommend you structure real projects.
These are opinionated guides. They represent patterns we’ve seen work well across many teams and production deployments. If you’re starting a new project or scaling an existing one, start here.
Bring your own image (BYOI)
Two patterns for teams that own their Docker images and want Flyte for orchestration without handing over their build pipeline.
Monorepo with uv
How to structure Flyte projects with uv, from single-package setups to multi-team monorepos with shared and independent lockfiles.
CI/CD deployments
How to deploy a Flyte project from CI. Uses GitHub Actions as the reference, but the building blocks (API key,
flyte deploy, commit-pinned versions) translate to any runner.
Resource management and multi-team scaling
Projects, domains, quotas, RBAC, and secrets: the primitives to set up before you have ten teams and a noisy-neighbor problem.