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".)

Two kinds of project

When you press the + button next to the project name, you choose a type. You cannot change the type later, so it is worth getting right.

Server Only

Choose this if you rent servers from a hosting company — DigitalOcean, Hetzner, Linode, Vultr, OVH, GoDaddy, a VPS from anywhere — and you do not have an Amazon Web Services account, or you do not want to connect it.

  • It asks for a name only. No keys, no region, nothing technical.
  • The menu has six items: Servers, Chatbot, Uptime, Jenkins, Grafana, MCP.
  • It opens on the Servers page, which is where you will spend your time.

This is the right answer for most people. If you are not sure, choose this.

AWS

Choose this if you have an Amazon Web Services account and want your bill, your security findings, your storage and your servers in one place.

It asks for three things — an access key, a secret key and a region — and the menu grows to fifteen items. Getting those keys, and the permissions they need, is its own guide: Connect AWS.

GCP (Google Cloud) is marked "Coming soon" and cannot be selected.

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 / account 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