Twenty clients, twenty stacks, one team. Clusterward rolls out applications from Git, creates a database and domain with a click and gives every client and every freelancer exactly the access they need.
For agencies, Clusterward is the cockpit that holds all client projects on Scaleway Kubernetes. Each project is an application with environments, services and builds; applications can be organized into groups, for example per client. A client or freelancer gets a role with an application scope and sees only their own projects. Deployments come from Git, the database and domain are created on the service page, and environment variables are stored encrypted in the cockpit. One cluster carries many projects in separate namespaces; anyone who needs isolation gets a dedicated cluster in a dedicated Scaleway project.
Application with repository, build and environments such as staging and production.
Developers operate, the client views, the freelancer sees only their project.
Create the database on the service page, enter the domain, and the certificate follows on its own.
Deployment from Git with a health check, restart on configuration changes.
The client gets read access to their project and alerts in their own channel.
The operations work that is otherwise scattered across Hetzner boxes, Vercel accounts and a folder of kubeconfigs.
The applications overview organizes projects into groups, for example per client, with health status and last deployment per service. Order and membership apply to the whole team.
Roles assign one level per area; the application scope limits a user to their own projects. A client sees their project, a freelancer deploys only theirs. Every action in the audit log.
Branch, Dockerfile and image belong to the build. Builds run in the cluster without a Docker daemon or with GitHub Actions on GitHub runners, and the tag is verified before the rollout.
On the service page, the database is created with a role and password in one step, and the host gets a record and certificate. Connection details ready to copy in the cockpit.
Recurring sets of variables as a template, copied into the project on creation. Multi-line values such as keys stay intact.
One channel per client: failed deployments, unhealthy pods and expiring certificates land in the right Slack or Teams channel, once per event.
A new WordPress client site is created from four fields: its own database, a disk with daily snapshots, a cron job and a certificate. Until setup is complete, a password protects the installer.
Managed Kubernetes in EU data centers, costs billed directly by Scaleway.
Image builds without a build server, either in the cluster or on GitHub.
PostgreSQL or MySQL, connected privately, one database per service.
Records created automatically at Cloudflare or Scaleway DNS, certificates per host or as a wildcard.
A role assigns one level per area, plus the list of projects that have been shared.
| Person | Role | Sees and can |
|---|---|---|
| Project lead | Manage applications | All projects, invite users, delete |
| Developer | Operate applications | Deploy their projects, change variables, read logs |
| Freelancer | Operate applications, one project | Only the shared project |
| Client | View applications, one project | Status, deployments and logs of their project |
| Operations | Administrator | Clusters, databases, DNS, everything |
How a project gets from commit to cluster is explained under Deployments. Roles, application scope and the audit log are described in Security & access.
If you equip clients with the same stack every time, such as a CMS per client, describe it once as a pipeline; see Tenant pipelines. What it costs is listed under Pricing: two clusters from €99 per month, unlimited projects and users.
WordPress from the app catalog walks through creating a WordPress site from the app catalog; the post WordPress on Kubernetes: seven traps between the chart and the first page covers the pitfalls of doing it yourself.
Git, container image or Helm chart – rolled out with a health check.
Go to DeploymentsRoles, mandatory 2FA, audit log and IP allowlist.
Go to Security & accessCustomer onboarding from building blocks, live in under a minute.
Go to Tenant pipelinesNo. One cluster carries many projects in separate namespaces; most agencies run one cluster for all their smaller clients and dedicated clusters only where a client requires isolation or their own Scaleway project. A dedicated cluster is created with the provisioning profile of the client’s project.
Can’t find your question? Write to us – we usually reply on the same business day.
Ask a questionWe create one of your projects, roll it out from Git and set up access for the client and your team.
