Software development

From commit to production – on your own platform

Build with the same open-source components Cloudless runs on, with a secure software supply chain from the first line of code to the running service – for web services, mobile apps and desktop apps alike.

01

Build with our components

The developer tools are the same components that run the platform – open source, self-hosted and connected

Forgejo

Git repositories, issues, pull requests and a package registry in your own Git service.

Forgejo Actions

CI on your own runners, with GitHub Actions-compatible workflows that build, test and publish on every push.

registry.cloudless.no

Container images, Helm charts, Forgejo actions and Talos extensions from one registry under our control.

OpenBao and External Secrets

Secrets live in a vault and are synced into Kubernetes – never committed to Git.

CloudNativePG and RustFS

Highly available Postgres and S3-compatible object storage for your services.

VictoriaMetrics, VictoriaLogs and Grafana

Metrics, logs and dashboards from day one, with alerts in Matrix chat.

02

A secure software supply chain

Every step from source code to running service is open, auditable and under your control

  1. 01

    Code

    Forgejo

    Reviewed changes in your own Git service

  2. 02

    Build

    Forgejo Actions

    Builds and tests on your own runners, not someone else's cloud

  3. 03

    Store

    registry.cloudless.no

    Images and charts in a registry you control

  4. 04

    Deploy

    Fleet

    GitOps rolls out exactly what is in Git

  5. 05

    Run

    Talos Linux

    Minimal, immutable OS with no SSH and no shell

No unknown sources: every dependency in the stack – Talos extensions, kubelet images, Forgejo actions, runner images and Helm charts – comes from our own registry.

03

From Git repository to Kubernetes

Your Forgejo repositories drive the clusters directly – what is merged is what runs

  1. 01 · Commit

    Merge to Git

    Forgejo

    Configuration and Helm values live in Git, next to the code.

  2. 02 · Sync

    Fleet picks it up

    Fleet

    Fleet watches your Forgejo repositories and picks up every change.

  3. 03 · Roll out

    Every cluster in step

    Kubernetes

    Changes roll out to one cluster or many, grouped by labels.

  4. 04 · Operate

    One control plane

    Rancher

    Cluster health, access and upgrades from one place.

Every change is a commit: you can see who changed what in production – and roll it back with a revert.

04

Mobile and desktop apps too

Build, sign and release mobile and desktop apps with the same pipeline as your services – all the way to the App Store and Google Play

  1. 01

    Build

    Forgejo Actions · Linux and Mac runners

    Mobile and desktop apps build on your own runners – including Mac runners for iOS and macOS – from the same repositories as your services.

  2. 02

    Sign

    Code signing

    Apps are signed in the pipeline, along with the rest of the platform-specific steps.

  3. 03

    Deploy

    Forgejo packages

    Builds and packages land in your own package registry, next to your container images.

  4. 04

    Release

    Forgejo releases

    Release to your users from the same pipeline, with every release traced back to a commit.

  5. 05

    Publish

    App Store · Google Play

    Mobile apps go out to the App Store and Google Play from the same pipeline.

05

Already in production

Not a lab setup – this is how Cloudless delivers software today

5 million+

end users

The platform already serves more than 5 million end users.

Talk to us