Skip to content

Flyte

What it is

Flyte is an open-source, container-native workflow orchestrator built on Kubernetes, specifically designed for machine learning and data processing at scale. As of May 2026, Flyte 2.0 is the current major release, introducing a reimagined Python SDK, native async support, and a dedicated Devbox for local development.

What problem it solves

It solves the challenges of reproducibility, scalability, and maintainability in ML pipelines. Flyte ensures that workflows are versioned, tasks are isolated in containers, and infrastructure (like GPUs) is provisioned dynamically. Flyte 2.0 further simplifies the developer experience by allowing "agentic" workflows to be constructed at runtime using native Python constructs.

Where it fits in the stack

Orchestration / ML Platform. It acts as the backbone for large-scale AI and data platforms, sitting on top of Kubernetes.

Typical use cases

  • Large-Scale ML Training: Orchestrating distributed training jobs across hundreds of GPUs (including NVIDIA H100 support).
  • Agentic Workflows: Using Flyte 2.0's dynamic orchestration to build self-healing AI systems that make decisions at runtime.
  • Data Engineering: Running complex ETL pipelines with strong type safety and task-level caching.
  • Bioinformatics: Processing massive datasets with strict auditability and reproducibility requirements.

Strengths

  • Flyte 2.0 SDK: A more intuitive, Pythonic API that supports asyncio for parallelism and standard try-except for error handling.
  • Strong Typing: Interfaces are strictly typed, catching errors at compile-time (or registration-time) rather than runtime.
  • Dynamic Infrastructure: Fine-grained resource allocation (CPU, Mem, GPU) per task.
  • Reproducibility: Every execution is versioned and reproducible, with built-in task-level caching.
  • Flyte Decks: Interactive visualizations of task outputs (e.g., plots, data summaries) directly in the UI.

Limitations

  • Kubernetes Native: Requires a K8s cluster for full production features, though Flyte 2.0 Devbox significantly improves local testing.
  • Learning Curve: The concept of strongly-typed workflows and registration can be unfamiliar to users used to imperative scripts.
  • Platform Overhead: Managing a full Flyte installation (Admin, Propeller, DataCatalog) requires dedicated DevOps effort.

When to use it

  • You are building production-grade ML pipelines that need to scale to thousands of containers.
  • You require strict reproducibility and auditability of your data and model versions.
  • You want to leverage Kubernetes' resource management for heterogeneous workloads (CPU vs. GPU).

When not to use it

  • For simple, lightweight automation where a single machine or a basic orchestrator (like Hamilton) is sufficient.
  • If you don't have access to or the expertise to manage a Kubernetes cluster.

Licensing and cost

  • Open Source: Yes (Apache License 2.0)
  • Cost: Free self-hosted; paid managed offerings (Union.ai).
  • Self-hostable: Yes

Getting started

Flyte 2.0 Devbox (Local)

The Devbox provides a full Flyte backend and UI on your local machine:

# Install the Flyte 2 CLI
curl -sL https://ctl.flyte.org/install | bash

# Start the Devbox
flyte dev start
Access the UI at http://localhost:3000.

Basic Flyte 2.0 Example

Flyte 2.0 moves away from @workflow in favor of TaskEnvironment:

import flyte

# Define an environment
env = flyte.TaskEnvironment(name="my_env")

@env.task
async def greet(name: str) -> str:
    return f"Hello, {name}!"

@env.task
async def main(name: str) -> str:
    message = await greet(name)
    return message.upper()

if __name__ == "__main__":
    # Local execution
    flyte.init_from_config()
    result = flyte.run(main, name="Flyte 2.0")
    print(result.wait())

CLI examples

The flyte CLI manages tasks, workflows, and executions.

# Register an app (workflow) to the backend
flyte register my_app.py --project my_project --domain development

# Execute a task or workflow on the cluster
flyte run my_app.py main --name "Production Run"

# List executions in a project
flyte list execution --project my_project --domain development

# Fetch logs for a specific execution
flyte get execution <execution_id> --show-logs

API examples

Flyte 2.0 exposes a gRPC and REST API for programmatic interaction.

# Health check via REST
curl -X GET "http://flyte-admin:8088/api/v1/health"

# List projects via API
curl -X GET "http://flyte-admin:8088/api/v1/projects"
  • Union.ai — The enterprise platform powered by Flyte.
  • Argo Workflows — The underlying workflow engine often compared with Flyte.
  • Apache Airflow — For general-purpose batch orchestration.
  • Dagster — For asset-centric data orchestration.
  • NVIDIA — Flyte 2.0 has first-class support for H100 GPUs.
  • Kubernetes — The required runtime for Flyte production clusters.
  • OpenTelemetry — For tracing Flyte 2.0 executions.

Backlog

  • [x] Perform quarterly technical freshness audit. (Completed: 2026-05-31)

Contribution Metadata

  • Last reviewed: 2026-05-31
  • Confidence: high

Sources / References