Skip to content
LyftData Docs (Beta)

Catalog

The Catalog is where you browse reusable building blocks and starters for Deployments and Jobs.

It can include:

  • Local items bundled with the server or created in your workspace.
  • Portal items (licensed) from a shared catalog that you can install and keep up to date.

Catalog item types

Workflows

Workflows are end-to-end graphs (DAGs) composed of blueprints.

Use them when you want a multi-job system. In the Catalog, filter to Workflows and click Plan & register to create a deployment from a selected workflow version.

Perspectives

Perspectives are starter workflow skeletons with intentionally unbound slots.

Use them when you want a standard architecture but still need to choose concrete building blocks for your environment. Perspectives are not deployable as-is: start from a perspective, complete bindings in the Workflows editor, publish, then run Plan & register.

Blueprints

Blueprints are reusable deployment building blocks (modules). They can be used in two ways:

  • Import them into a workflow while authoring, or
  • Click Plan & register to create a deployment directly from a blueprint (useful for “single-module” systems).

Jobs (library jobs)

Jobs are managed job snippets from the catalog. They are useful as known-good single-job starting points.

In the Catalog, clicking Plan & register on a Job takes you to the “new job” flow with the job content prefilled.

Common actions

  • Search + filters: use the tabs (Workflows / Perspectives / Blueprints / Jobs) and filters (Source, Availability, tags) to narrow down choices.
  • Preview: preview graphs for workflows/perspectives/blueprints, and preview job content for library jobs.
  • Details: open the details drawer to see provenance, tags, version, and related items.
  • Plan & register:
    • For workflows/blueprints: starts a new deployment.
    • For perspectives: starts a workflow-authoring flow so you can complete bindings before deployment.
    • For jobs: starts a new job draft in the Jobs UI.

Portal vs local

If your deployment is licensed, you can switch Source → Portal to browse shared catalog content. Portal items may be available as:

  • Portal-only: not installed locally yet.
  • Installed: installed into your server.
  • Update available: a newer version exists in the portal.

Next

  • Learn how workflows are authored and versioned in Workflows.
  • Learn how deployments are planned/applied in Deployment Manager.
  • If you only need a single job, start with Jobs.