Skip to main content
Build with Ultralytics Platform·Why Platform·Lesson 1/10
Lessonintermediate

Why Ultralytics Platform

What Platform is, what it isn't, and the lifecycle it covers.

Ultralytics Platform exists because shipping a computer vision model has six painful steps and most teams glue together six tools to do them. Platform gives you one place to source data, label it, train, deploy, and monitor — with the same model formats and code you already use locally — collapsing the entire MLOps lifecycle into a single browser tab.

Outcome

Decide which Platform features fit your project and which steps you'll keep on your own infrastructure.

Fast Track
If you already know your way around, here's the short version.
  1. Data sourcing → Discovery.

  2. Labeling → auto-annotation + review.

  3. Training → managed cloud GPU runs.

  4. Deployment → managed endpoints.

  5. Monitoring → built-in dashboards and drift signals.

Hands-on

The lifecycle

Every production CV system goes through the same lifecycle. Ultralytics Platform aims to be the place that handles all of it:

graph LR
    A[Source data] --> B[Annotate]
    B --> C[Curate / split]
    C --> D[Train]
    D --> E[Validate]
    E --> F{Good enough?}
    F -- no --> A
    F -- yes --> G[Deploy]
    G --> H[Monitor]
    H -- drift --> A

Most teams have a tool (or a script, or a Notion doc) for each step. Each transition between tools is a handoff that loses context — which images were sampled? which labels are stale? which checkpoint is in production? Platform's value is the transitions, not any single step.

What Platform handles well

  • Data sourcing. Built-in image / video discovery, deduplication, and tagging — see the data management overview.
  • Annotation at scale. Auto-annotation with Ultralytics YOLO models, plus a UI for human review.
  • Cloud and local training. Cloud GPU runs without provisioning anything, plus local run logging when you train on your own infrastructure.
  • Experiment tracking. Every run is logged automatically; comparison is built in alongside integrations like Comet and MLflow.
  • Managed deployment. One-click endpoints with regional placement.
  • Monitoring. Latency, detection volumes, and data drift signals out of the box.

What you'll still want to own

  • Custom data pipelines. If your data comes from a proprietary system (DICOM, OEM cameras), you'll integrate it yourself.
  • Custom postprocessing. Counting / heatmap / business-logic pipelines (course 3) usually live in your service, not on Platform — many of these patterns ship as Ultralytics Solutions.
  • Compliance-locked workloads. If you can't send data outside a specific region, see lesson 9 on regions and the data privacy glossary entry.

The right way to think about Platform is the default home base for the lifecycle — and an explicit decision about which one or two steps you handle yourself. The Platform quickstart is the shortest path from this model to the UI, and the active learning loop it enables is what makes the second iteration cheaper than the first.

How it relates to the open-source ultralytics package

Platform and the OSS package use the same model formats and the same Python API. A model trained on Platform is a normal .pt you can download, run with from ultralytics import YOLO, and export the same way you would locally.

Platform is not a separate framework. It's a managed home for the workflows you'd otherwise glue together.

That means everything you learned in courses 1–3 carries over directly. Platform just removes the infrastructure that surrounds the model.

Pricing model (as of 2026)

Platform has a free tier sufficient for most learning and small projects. Paid tiers scale with:

  • GPU training hours.
  • Active deployment hours.
  • Stored data + dataset versions.

For this course, the free tier is enough. Production teams should benchmark their actual workload before committing.

Try It

Sketch your project's lifecycle and label which steps you'd run on Platform vs your own infrastructure. The result is the operational shape of the next 8 weeks of work.

Done When
You've finished the lesson when all of these are true.
  • You can name the six lifecycle steps Platform covers.

  • You've decided which step you're starting with for your project.

  • You've created an Ultralytics Platform account and logged in.

What's next

Now we'll start at the top of the lifecycle — finding raw data with Discovery.