Core Concepts
These are the main concepts used throughout the current product and API.
| Concept | Meaning |
|---|---|
Tenant |
The authenticated workspace boundary used for authorization and product limits. |
Project |
The unit that owns functions, cloud integrations, storage config, and deployment state. |
Function |
A saved Dart function record, usually created in draft state before deployment. |
Trigger |
The execution style selected in the editor. The current trigger catalog is returned by |
Runtime |
The selected Dart SDK version for the function. New drafts can only use versions returned in |
Integration |
The project-scoped cloud identity and storage configuration for Azure, AWS, or GCP. |
Artifact |
An uploaded source file such as |
Deployment |
An async lifecycle row that moves through queued, running, deploying, succeeded, failed, or undeploy states. |
Deployment event |
An append-only event entry that explains what happened during deployment or undeploy. |
How The Pieces Fit Together
-
A user authenticates and lands inside a tenant workspace.
-
The user creates or selects a project.
-
The user uploads artifacts and saves a draft function.
-
The project connects the target cloud provider.
-
The backend validates runtime and artifact contracts.
-
A deployment row is queued and executed by the runner.
-
The frontend polls deployment status and events until a terminal state.
Storage And Runtime Separation
The saved function record and the deployment artifact source are related but not identical:
-
the function record stores authoring metadata
-
uploads stage concrete files in the connected storage provider
-
the deployment request should pass explicit artifact sources instead of assuming the function row is the only source of truth