SaaS product in production

Your SaaS in production. From the very first release.

A cluster with an HA control plane, four Compute nodes, and its own load balancer carries your product. Uploads and assets live in Object Storage, images in the Registry, and you deploy every release straight from GitHub. All in one organization, with one permission model and one bill.

The use case

From launch to your thousandth customer.

Products involved

The launch

Picture a small team that has built a product customers are waiting for. A booking tool, a partner portal, an analytics platform. Instead of spending weeks on infrastructure, the team creates a project on Loopback and starts the cluster “Production”. The HA control plane and the private network come from Loopback, and the four Compute nodes run with the provider and in the location you choose. The load balancer sits in front of the cluster, and your product is live.

Releases without the night shift

A Bundle connects your GitHub repository to the cluster. You deploy every release straight from GitHub, images land in the organization Registry automatically, and the deployment history shows you every version. If something is off, you roll back. Debugging late into the night is no longer part of the release plan, and your team ships features when they are ready.

Files that grow with you

Profile pictures, PDF invoices, exports, and media: everything your users upload lands in S3-compatible Object Storage. Your application speaks the S3 API, and the buckets live in the same project as the cluster and are reachable from it directly. Public buckets for assets, private ones for everything confidential, with access keys and a file browser.

Growing without a rebuild

When ten customers become a thousand, the setup grows with you. Scaling groups with finely tunable auto-scaling give the cluster more Compute when load rises, and one-click upgrades keep Kubernetes current. New colleagues get exactly the access they need through SSO and fine-grained permissions. You pay hourly for what runs and know in advance what the month costs.

The setup

Everything your SaaS needs. On one bill.

This is what a month of this setup looks like. The sample bill shows the dynamic costs, and the Platform-Fee for your organization comes on top.

Sample bill

SaaS product in production

Your SaaS runs on a cluster with an HA control plane and four Compute nodes. Uploads and assets live in Object Storage, and you deploy new releases straight from GitHub.

  • Cluster Production

    HA control plane, 4 Compute with 4 vCPU / 8 GB, 1 load balancer

    253.18€

  • Object Storage

    200 GB, 0.05€ per GB, uploads and assets

    10.00€

  • Registry

    50 GB, 0.05€ per GB, images and charts

    2.50€

  • Bundles

    Deploy straight from GitHub, 1 Bundle at 99€ with Registry included

    99.00€

Total

Sample for this setup, monthly.

364.68€

Amounts are net. Statutory VAT is charged in addition.Dynamic costs are shown per month and billed hourly, based on 720 hours.All amounts are rounded.Prices can be updated dynamically. When you open this page, you see the price that currently applies, and it is non-binding. The binding price is set when you order.

  • Cluster Production

    HA control plane, four Compute nodes with 4 vCPU and 8 GB, and its own load balancer.

  • Object Storage

    200 GB for uploads and assets, S3-compatible and reachable straight from the cluster.

  • Registry

    50 GB for images and Helm charts, organization-wide with Loopback RBAC.

  • Bundles

    Deploy straight from GitHub, with deployment history and rollback.

How you get started

  1. 01

    Create a project

    Organization and project are the shared frame for clusters, buckets, permissions, and billing.

  2. 02

    Start the cluster

    Choose provider and location, assign four Compute nodes, and put the load balancer in front.

  3. 03

    Connect GitHub

    Create a Bundle and deploy straight from GitHub. Images land in the Registry.

  4. 04

    Create buckets

    Object Storage in the same project, public for assets and private for uploads.

Next step

Create a project, start your cluster, and take your first release live straight from GitHub.