Services

A service is a deployable process in one environment. Web applications, backend APIs, workers, bots, and scheduled processes should be separate services when they have different commands, scaling, or public-network needs.

Add a service

From the project canvas, select Add Service, then choose:

• GitHub Repository for source connected through the GitHub App;
• Upload folder for an authenticated local source archive;
• Container image for an existing image;
• Templates for a managed multi-service template; or
• Database for a supported managed datastore.

Autodisc creates the service in the environment shown in the breadcrumb.

Service panel

Select a service node on the canvas to open its panel.

Deployments

Shows current and historical deployment attempts. Open an item for source, builder/runtime class, timestamps, health outcome, and bounded build output.

Logs

Shows live runtime output and retained history when available. Logs may include application data, so avoid writing secrets in your application.

Metrics

Shows CPU and memory behavior relative to the configured service limits. Template capabilities vary when a node represents more than one runtime.

Files

Use this only where the service exposes a supported mutable or persistent filesystem. Files inside immutable image containers are temporary and reset on redeploy.

Networking

Manage generated domains, custom domains, TCP publication, and the private service endpoint. See Networking.

Details

Inspect source and runtime configuration, then redeploy, stop, or delete the service if your role permits it.

Dependencies

depends_on expresses startup and plan ordering; it does not replace application-level connection retries. Applications should tolerate a database or sibling service becoming temporarily unavailable.

Use private endpoints and injected bindings for service-to-service traffic. Do not hardcode a generated hostname, provider resource ID, or database password into source.

Health and ports

A public web service must listen on the configured port and on an address reachable from the container network, typically 0.0.0.0. Health endpoints should return quickly without performing destructive or expensive work.