A Service is a runnable unit inside an Environment.

dFlow supports multiple service types (for example app, database, and docker workloads) so you can model both your application tier and supporting data tier in one place.

Choosing a type

• App services: HTTP workloads built from Git or similar sources.
• Database services: managed data templates appropriate to your plan.
• Docker services: bring your own image when you need full container control.

Deployments

Each service receives Deployments that capture a concrete revision: build output, configuration, and rollout state. Operations like rollback and redeploy work at this layer.

Relationship

Services live inside an Environment. The environment’s Application is the wider product boundary. Each service’s history is tracked through Deployments.

See also

• How dFlow is structured: end-to-end mental model.
• Services overview and Create a service: section guides.
• Service settings: environment variables and references.
• Deployments overview: operations when published.
• Logs: build and runtime output.