Projects
The Projects list, one project's page (Overview, Deployments, Logs, Analytics, Settings) and the everyday actions: redeploy, restart, pause, roll back and delete.
A project is your code from one git repository and branch, built and running at its own address. To create one, see Deploy your first project.
The Projects list
Projects in the sidebar shows four figures (Live, Failing, Deploys this week, Waiting for you) and the table of projects you can see. Filter with All projects, Live, Failing or Stopped, and by Status, Type and Team. Above the table, Favourites and Mine keep the projects you care about at hand.
Each row's menu has Open project, Deployments, Build logs, Runtime logs, Settings, Visit (opens the live address) and Copy address. Projects > Groups collects projects into groups with their own page.
One project's page
The header shows the project's status, its production address and the buttons Visit, Build logs and Redeploy. More actions has Restart, Pause, Resume, Instant rollback, Tickets (when your organisation connects a task tracker) and Delete project.
The page has five tabs.
Overview
Figures for Uptime, Memory (how much of its limit it uses now), Alerts firing and AI spend; Recent deployments ("Open one for its build log, or to roll back to it"); About this project; Resources attached (databases, caches, files, keys); and its Team. Below that, the history of changes to the project.
Deployments
Three views: Deployments (every deploy with status, commit, who started it and when), Versions (each successful build you can return to) and QA runs (automatic checks, where your platform runs them).
Open a deployment to see its Build steps, the full Build log, the Source (commit hash and image tag) and the buttons Roll back to this, Redeploy and Remove container.
Logs
View | What |
|---|---|
Build logs | Every line of each build |
Runtime logs | What the running container prints |
Job runs | Runs of the jobs that use this project's code |
Requests | Calls to the project's address |
Alerts | Alerts that fired for the project; Acknowledge or Resolve them here |
Every log line carries a reference you can quote to support.
Analytics
Memory, restarts, storage, and AI spend of the project's own AI key in the current budget period, over a period you pick.
Settings
Project settings come in eight groups; see Project settings.
Everyday actions
Action | What happens |
|---|---|
Redeploy | Builds the branch head again (or reuses the image if nothing changed) and swaps the container with no downtime: the old one keeps serving until the new one is ready |
Restart | Restarts the running container with its current settings, secrets and environment |
Pause | It stops answering requests but keeps its state; Resume brings it back at once, without a rebuild |
Instant rollback | Puts the previous version back in front of the address |
Roll back to this (on a deployment) | Runs that exact version again |
Delete project | It stops and disappears from your projects. Its databases and files are detached and kept, so support can restore it. Your git repository is never touched. |
Production-gated projects
On a production platform, a project can be marked Prod-gated: deploys must then pass your organisation's release rules (for example an approval). The badge shows in the header. Owners and team admins set it; turning it off needs an Owner.