VegaFlow

VegaFlow coordinates workspace-scoped data movement. A saved connection describes how VegaFlow reaches a system, a cluster supplies execution capacity, and a QuickFlow combines source, destination, selection, and execution settings. Each execution creates a run; recurring execution is controlled by a schedule.

Connector definition → Connection ┐
                                  ├→ QuickFlow → Run history
Execution settings → Cluster ─────┘           └→ Schedule

Core resources

Resource	Responsibility
Connector	Declares the configuration schema for a source or destination type
Connection	Stores validated, workspace-scoped connector configuration and secret references
Cluster	Defines execution sizing and lifecycle behavior
QuickFlow	Selects connections, data, schema behavior, and the execution cluster
Run	Records one requested QuickFlow execution and its lifecycle
Schedule	Starts future runs according to a managed schedule state

Scope and permissions

Every customer VegaFlow route includes org_id and workspace_id. Permissions exist at collection and resource-instance levels for connections, clusters, and QuickFlows. A user may be allowed to run an existing QuickFlow without being allowed to edit its connection or cluster.

Supported path

The current saved-connection model supports Postgres. Connector discovery and property endpoints expose the configuration accepted by the service; do not assume an unlisted connector is available for saved connections. Start with the VegaFlow quickstart, then use the detailed guides for connections, clusters, QuickFlows, and runs and schedules.