Start here

Projects explained

A project is the box everything else lives in. Pick the right type and the rest of the app makes sense.

Everything in DevOps Agent belongs to a project. A project is a box. Inside the box are your servers, your uptime monitors, your integrations and your chats. The project you have selected — shown at the top of the left sidebar — decides what every other screen shows you.

You will also see the word account in places. In this app project and account mean the same thing. (Older screens say "Project / Account".)

Your first project

A new account starts with one project called My servers, so you can go straight to connecting a server. Rename it in Settings → Project. If you delete it, the + button next to the project name makes a new one.

Project types

New projects are Server Only: they hold any Linux server you can log into over SSH — DigitalOcean, Hetzner, Linode, Vultr, OVH, GoDaddy, an AWS EC2 instance, a VPS from anywhere.

  • It asks for a name only. No keys, no region, nothing technical.
  • The menu: Dashboard, Chatbot, Agents, Website uptime, Server metrics, Servers, Databases, MCP, Tasks. Jenkins and Kubernetes are hidden until you turn them on with the gear next to Navigation.

AWS, GCP and Azure projects are marked "Coming soon" and cannot be selected. An AWS project made before that keeps working: Connect AWS.

How to name a project

The name is what you will see in the sidebar and in every dropdown. Good names describe what it is for:

  • Shop — production
  • Shop — staging
  • Client A
  • Internal tools

You can rename a project at any time in Settings → Project. Names must be unique within your workspace.

How many projects should I have?

One project per environment or per client is the usual answer.

  • One website, one server? One project. Done.
  • Production and staging? Two projects, so you cannot accidentally restart the wrong one.
  • An agency with several clients? One project per client, and then use team logins to give each engineer access to only the clients they work on.

A colour label can be attached to each project from the project picker — a cheap way to make "production" visually obvious before you click something.

Switching projects

Click the project name at the top of the sidebar. The picker lists every project you can see, with its type. Choosing one reloads every screen against that project.

If nothing is selected, most screens will tell you to "Select a project to enable sections". That is not an error — pick one and it clears.

Editing and deleting a project

Settings → Project acts on the project currently selected in the sidebar:

  • Rename it.
  • AWS only: change the region, or replace the access keys (for example after rotating them).
  • Delete it. This asks you to confirm, and it removes the servers, monitors and integrations recorded inside it. Your actual servers and your actual AWS resources are not touched — only what DevOps Agent stored about them.

Only Owners and Admins can add, edit or delete projects. See Roles.

Next