Run Kubernetes on Scaleway – without your own platform team.

• Scaleway Kapsule

  Managed Kubernetes with Private Network, Public Gateway and nodes without public IPs.

• Kubernetes & Helm

  Deployments as standard objects, Helm charts from the template library, no proprietary format.

• Managed Postgres & MySQL

  Scaleway RDB with a private endpoint, one database and role per service.

• Scaleway Object Storage

  S3-compatible buckets with their own IAM key and bucket policy per application.

• cert-manager

  Let's Encrypt per host or a managed wildcard certificate for all subdomains.

• Cloudflare DNS

  DNS records created automatically, proxy switchable per host, real client addresses in the cluster.

• Kaniko & GitHub Actions

  Container builds in the cluster or on GitHub’s runners, with the image verified in the registry before rollout.

• ingress-nginx & Envoy Gateway

  Ingress or Gateway API; timeouts, rate limits, basic auth and CORS per service.

Every feature is a deliberate switch. Nothing touches your infrastructure until you approve it.

Anything else? Write to us or book a demo.

• Does Clusterward run in my own Scaleway project?

  Yes. You store an IAM key from your Scaleway project as a provisioning profile; Clusterward verifies it before saving and creates Kapsule clusters, managed databases, the container registry and buckets exclusively in that project. The resources belong to you, appear in your Scaleway console and are billed directly by Scaleway. Clusterward keeps no copy of your data, only the control information.

• What do I need at Scaleway to get started?

  A Scaleway account with a project and an IAM key that is allowed to manage Kapsule, Private Networks, Managed Databases, Object Storage and the container registry. The help in the cockpit lists the exact permission sets, and the test button shows which ones are missing. For domains and certificates, you can optionally add a Cloudflare zone with an API token. That’s all you need – the wizard sets up the rest.

• Can I connect existing Kubernetes clusters?

  Yes. You register an existing Kapsule cluster by importing its kubeconfig. Clusterward checks the credentials with a read-only call before storing them encrypted, and can then create its own restricted identity in the cluster so the admin token isn’t needed permanently. You can add the ingress controller, cert-manager and metrics-server later from the cockpit as needed.

• How does onboarding new customers work?

  In the pipeline designer, you plug together building blocks – database, bucket, domain, environment and workload – in the order your application needs. Values such as the database URL or bucket credentials flow through a variable bus into the workload’s configuration. At start, a preflight checks for collisions, every step can be retried, and an offboarding tears everything down in reverse – with a database dump before every drop. In practice, a run takes less than a minute.

• How is Clusterward different from Qovery or Heroku?

  Qovery abstracts multiple clouds, and Heroku runs the infrastructure itself. Clusterward is tailored to Scaleway and uses Kapsule, Managed Databases and Object Storage directly – without its own abstraction layer and without cloud SDKs. All resources stay in your project in European data centers, and customer onboarding via pipeline is built in rather than bolted on. You keep Kubernetes, Helm and cert-manager as open standards.

• Which applications can I deploy?

  Anything that runs in a container: a Git repository with a Dockerfile is built by Kaniko in the cluster or by GitHub Actions, a ready-made container image comes from the registry, a Helm chart from the template library. Per service, you configure port, resources, scaling, environment variables, domains, volumes and network settings such as timeouts or basic auth – regardless of language or framework.

• How secure are my credentials and data?

  Credentials for clusters, Scaleway and databases are stored with AES-256-GCM encryption, are write-only and never appear in logs or API responses. Every login requires a password and two-factor authentication, roles limit access per area and application, and every change is recorded in the audit log with name and timestamp. Databases are backed up before every deletion, volumes are snapshotted before every removal.

• What happens to my infrastructure if I cancel?

  It keeps running unchanged. Clusterward only removes its registration – clusters, databases, buckets, DNS records and certificates remain in your Scaleway project and can continue to be operated with kubectl, Helm and the Scaleway console. There is no vendor lock-in, because Clusterward brings no runtime of its own but manages standard objects in your cluster.

• What does Scaleway cost on top of Clusterward?

  Clusterward costs €99, €299 or €799 per month – tiered only by the number of your clusters, cancelable monthly. Clusters, nodes, managed databases, Object Storage and load balancers are billed directly by Scaleway at Scaleway’s public prices, with no markup and without going through us. The resources live in your own Scaleway project, and you see every line item on your Scaleway invoice. Clusterward itself runs as SaaS in your own workspace on your own subdomain.

• How do I back up my data?

  Databases via Scaleway backups with download and restore into a new database, volumes via snapshots, applications via any earlier healthy version, and the configuration as a JSON export. All from the cockpit – nothing ever overwrites your data without being asked.

Can’t find your question? Write to us – we usually reply on the same business day.