Projects and environments

A project groups related applications, databases, and scheduled jobs. Open Workloads in the sidebar to see your projects and services.

Create a project

1. Open Workloads → New project.
2. Enter a Name, such as shop.
3. Choose the Cluster that will run its services. Choose — assign later — if you are still setting up the cluster.
4. Select Create project.

Upvale creates a Production environment with the project. If you left the cluster unassigned, open the project, choose Settings, select a cluster in Environments, and select Assign before deploying.

Your role needs Manage workloads to create projects. See Team and account for permissions.

Use the Workloads screen

The summary shows running services, nodes used, offline services, and degraded services. Use Type, State, and Project filters to narrow the list. Expand a project to see its resources, or open its name to view the project page.

Add Service creates an Application, Database, Scheduled job, or Compose stack. When opened outside a project, the creation flow asks you to choose one. A Compose stack opens the chosen project's Compose editor; it is not a separate resource category.

Use the star beside a project or resource to add it to your favorites for quick access.

Project tabs

The environment selector in the header determines which resources and Compose definition you are viewing. Add Service on this page uses that project and environment.

Environments and clusters

An environment is a scope for resource configuration and deployment, assigned to one cluster. The current dashboard creates Production automatically; it does not yet offer creating extra environments or moving an assigned environment to a different cluster. Use separate projects for production and staging today.

A cluster can run several projects. A project or environment boundary does not automatically isolate network traffic. The services' actual network attachments determine which services can reach one another. See Networking.

The simple deployment path

Choose the native form when you want to manage one service without writing YAML:

• Application: choose an image, set variables, and add a public route if needed.
• Database: choose an engine and storage, or use managed PostgreSQL HA.
• Scheduled job: choose an image and command, test a run, and enable a schedule.

For applications and databases, creating or saving configuration and deploying it are separate actions. The detail page shows the revision ready to deploy. Scheduled jobs have their own run and schedule controls.

Use Compose and native services together

An environment can contain both manually created services and services managed by its Compose definition. There is one Compose definition per environment.

Compose services appear in Resources alongside native services, with a Managed by Compose label. Their configuration belongs to the Compose definition. Use the project's Compose and Deployments tabs to change and deploy them; their individual configuration and deployment controls are restricted.

Compose does not adopt a manually created service just because its name matches a YAML service. A name collision stops the preview. Use a different name or plan a separate migration.

Manually created services are kept when Compose-managed resources are removed. To connect native and Compose services, use a network they both join; do not assume they share a network just because they share a project. See Compose networking.

Remove a project

1. Remove its applications, databases, scheduled jobs, and Compose-managed services first.
2. Open Settings → Danger zone.
3. Type the project name and select Remove project.

Removing a project deletes its project-scoped secrets. Retained volumes and host files are kept. Check Storage and backups before removing anything with data you need.