Software development
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
The developer tools are the same components that run the platform – open source, self-hosted and connected
Git repositories, issues, pull requests and a package registry in your own Git service.
CI on your own runners, with GitHub Actions-compatible workflows that build, test and publish on every push.
Container images, Helm charts, Forgejo actions and Talos extensions from one registry under our control.
Secrets live in a vault and are synced into Kubernetes – never committed to Git.
Highly available Postgres and S3-compatible object storage for your services.
Metrics, logs and dashboards from day one, with alerts in Matrix chat.
02
Every step from source code to running service is open, auditable and under your control
01
Forgejo
Reviewed changes in your own Git service
02
Forgejo Actions
Builds and tests on your own runners, not someone else's cloud
03
registry.cloudless.no
Images and charts in a registry you control
04
Fleet
GitOps rolls out exactly what is in Git
05
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
Your Forgejo repositories drive the clusters directly – what is merged is what runs
01 · Commit
Forgejo
Configuration and Helm values live in Git, next to the code.
02 · Sync
Fleet
Fleet watches your Forgejo repositories and picks up every change.
03 · Roll out
Kubernetes
Changes roll out to one cluster or many, grouped by labels.
04 · Operate
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
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
01
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.
02
Code signing
Apps are signed in the pipeline, along with the rest of the platform-specific steps.
03
Forgejo packages
Builds and packages land in your own package registry, next to your container images.
04
Forgejo releases
Release to your users from the same pipeline, with every release traced back to a commit.
05
App Store · Google Play
Mobile apps go out to the App Store and Google Play from the same pipeline.
05
Not a lab setup – this is how Cloudless delivers software today