SolutionsAgencies


Stop juggling a hosting account per client. Run WordPress and app sites on servers you control, give your team the right access, let clients look without touching, and know what every server costs.

Workspaces

Sites

Studio Ardenstudioarden.example
Slow Clayslowclay.shop
Maison Odamaisonoda.com
Porcelain Labporcelainlab.io

Servers

  • fsn-web-01 · Hetzner
  • ams-app-01 · DigitalOcean
  • hel-app-02 · UpCloud

People

  • Lena · Admin
  • Jonas · Developer
  • Mira · Developer

01 · Logins

One login instead of twenty.

No hosting account per client. Keep client sites in your workspace, or join the client’s own workspace and switch between them from the account menu.

02 · Access

No more wp-admin passwords by email.

Everyone on the team has their own role, and WordPress logins are single-use links created on the site page.

03 · Backups

Backups you actually know about.

Not whatever each host happens to keep: your schedule, your bucket, one-click restore for every client site.

04 · Activity

Know who changed what.

Deploys, backups and settings changes land in an activity log, so there’s no guesswork after something breaks.

Three roles out of the box. Change what each one can do if your team works differently.

Admin

You and your partners. Manage everything, including who’s on the team.

Developer

Freelancers and staff who deploy and operate servers, sites, domains and integrations.

Viewer

People who should see sites, uptime and backups without touching anything.

Servers from different providers sit in one list with their monthly cost, including Contabo contract terms. Connect a client’s own account when they should be billed directly.

Servers5 servers · 5 providersMonthly≈ €77
  • fsn-web-01CX33 · Falkenstein€7.79hourly, capped
  • vie-wp-02Cloud VPS 4 · Nuremberg€5.5012-month term
  • ams-app-01Basic 2C/4GB · Amsterdam$24.00hourly, capped
  • hel-app-022xCPU-4GB · Helsinki€20.00hourly, capped
  • fra-db-01VC2 2C/4GB · Frankfurt$24.00hourly, capped

  1. 1Pick the workspace

    Keep the client in your own workspace, or have them create a Nuvlo account and invite you to theirs.

  2. 2Connect the cloud account

    Use your own Hetzner or DigitalOcean account, or the client’s so they’re billed directly.

  3. 3Create the server

    Pick a region near the client’s visitors and a plan from the provider’s list.

  4. 4Add their sites

    WordPress, a Nuxt or Next.js app from Git, or a one-click app, each with its own domain and HTTPS.

How do workspaces work?

Every Nuvlo account has its own workspace. You can keep client sites in yours, or a client can create their own account and invite you, and you switch between workspaces from the account menu.

Can clients see only their own sites?

Yes. Invite the client to your workspace as a Viewer and choose which sites and servers they can see. Or keep their sites in their own workspace: the client creates a Nuvlo account, invites you as Admin or Developer, and you manage it from there.

Can each client pay for their own server?

Yes. Connect the client’s own cloud account and their provider bills them directly.

Can I adjust what each role can do?

Yes. View and manage access can be changed per role for servers, sites, domains, integrations, team and the activity log.

Is there a white-label or reseller program?

Not yet.


Your first server and site are free, with no card and no time limit. Connect a provider token and Nuvlo starts building it.