Skip to content

For agencies & MSPs

Every client's servers, one workspace.

Manage every client's servers without a login per client. Keep clients cleanly apart, give each engineer the right access and show clients exactly what changed, with a full audit log.

Book a demo Start for free

An agency workspace with five client projects and 28 servers. Each project shows its server count and your role in it; one project, clinic-portal, has a disk warning.

Clean boundaries

One workspace. No client sees another.

Projects keep each client's fleet apart, and roles decide who on your team can touch it.

A project per client

Servers, services, secrets and alerts live in the client's project. Nothing leaks across, not even a label.

Access per project

Engineers get a role in the projects they work on. Offboarding someone is one click, not a key rotation.

Alerts to the right channel

Each project routes alerts to its own Slack channel, email list or the client's on-call tool.

Read-only access for clients

Invite the client to their project as a Viewer so they can see health and history without touching anything.

Accountability

Show clients exactly what you did.

Every deploy, restart and secret change is in the audit log with who, when and from where. Export one client's month as CSV or JSON and attach it to the invoice.

audit-clinic-portal-2026-10.json 
[
  {
    "at": "2026-10-21T14:02:11Z",
    "actor": "sam@agency.example",
    "action": "service.deploy",
    "target": "clinic-portal/api",
    "detail": { "release": "r88", "image": "api:3.4.1" }
  },
  {
    "at": "2026-10-21T14:09:40Z",
    "actor": "kai@agency.example",
    "action": "secret.update",
    "target": "clinic-portal/production/SMTP_PASSWORD",
    "detail": { "version": 19 }
  }
]

Onboarding

Your standard stack, on a new client in minutes.

  1. 1

    Create the client's project

    Invite the engineers who work on it, and the client if they want a view.

  2. 2

    Install the agent on their servers

    One command per machine, at whichever provider the client uses.

  3. 3

    Apply your baseline

    Alerts, backups and housekeeping jobs from one file you keep in git, the same for every client.

kai@agency 
$ fwoop projects create clinic-portal
$ fwoop apply -f agency-baseline.yaml --project clinic-portal
+ alerts  disk, memory, uptime → slack:#clinic-portal
+ backups postgres nightly → s3://clinic-portal-backups
+ jobs    cleanup-tmp, cert-check
✓ Applied 3 alert rules, 1 backup plan and 2 jobs

Questions from agencies

Can clients see their own servers?

Yes. Invite them to their project with the Viewer role. They see health, deploys and history, and nothing from other projects.

Do client servers need to be at one provider?

No. Each server only needs outbound HTTPS. Clients can keep their own provider accounts and Fwoop manages the machines either way.

Can we pass costs on to clients?

Fwoop shows servers and usage per project, so you can bill clients for what they use. Talk to us about consolidated invoicing for larger agencies.

Which plan do agencies usually pick?

Business, for SSO, roles and the audit log. If you manage more than 50 client servers, talk to us about Enterprise.

Bring your first server online in five minutes.

Start free with three servers. No credit card, no sales call, and your workloads stay on machines you own.

Start for free Book a demo