Projects

A Project defines which parts of an application should share data, secrets, access rules, and operational context. Use one Project for Services that work together, and separate Projects when applications should have clear boundaries.

Last updated July 14, 2026

Group Services by the system they form

The web app that creates orders and the worker that processes them belong in the same Project because they need the same database and secrets. Two unrelated automations usually belong in separate Projects even when the same team owns both.

This grouping changes how the application works. Services in a Project can use the Project's databases, secrets, private network, access settings, and members. See How Tokay is organized for the full relationship between Workspaces, Projects, Services, and code.

Use the Project page to understand the whole app

The Project page brings related operational information together.

• Overview shows each Service and its current status.
• Resources contains databases, query consoles, exports, and password rotation.
• Secrets contains the values shared by Services in the Project.
• Members controls who can operate the Project.
• Usage shows the Project's share of the Workspace server.
• Access controls who can open its web apps.
• Settings contains the name, deployment behavior, and deletion controls.

A Project with one Service appears as a compact card on the dashboard. A Project with several Services expands to show how the application is doing as a group.

Deploy Services independently or together

Each Service has its own deployment history and health checked release. When several Services have updates ready, Deploy All starts them together without turning them into one release. A blocker on one Service does not stop its siblings.

Auto-deploy is also a Project setting. This makes it practical to connect two Projects to the same repository, let staging deploy every push, and require a person to release production.

Names help people navigate the system

Project and Service names can change as the application evolves. Renaming a web app changes the readable part of its URL, with redirects from earlier names, so web app renames are limited to three. See Web apps for the URL behavior.

An empty Project is valid and keeps its settings until you are ready to add Services.