Cloud by Naasson
Clouds and platforms that stay with you
Ready-made platforms for development and business, moves between clouds and servers, cluster federation. We deploy on your infrastructure and hand it over with a history of changes and evidence that it works.
After handover you keep ordinary infrastructure — Kubernetes, GitOps, Terraform, backups, monitoring, documentation. Any engineer can maintain it.
What's inside
Ready-made platforms
Setups for developers and businesses: from one server to a cluster.
Migrations
A plan for moving between clouds and servers, with rollback.
App catalogue
Hundreds of tested self-hosted applications.
Observability
Metrics, logs and traces on your own hardware.
Cluster federation
Several clusters as one environment.
What you get
- Working infrastructure with no lock-in to us
- A repository with configuration and change history
- Backups with a tested restore
- Instructions and a report on the checks
Discuss a task
Describe the task in a couple of lines — by email or Telegram. We will say honestly what we can do and where it makes sense to start.
Articles
All articles in this directionBackups you can actually restore
A backup nobody has restored is a rumour. Where Cloud by Naasson makes restoring easier, and where the work stays yours.
What one purchase includes
Working infrastructure, not a starting point you then have to finish yourself. The contents and the limits.
Domains, certificates and the public-or-not decision
Every application in the catalogue carries metadata on how it authenticates and how it is published. It is not a description: it decides whether the application ends up on the internet.
One binary instead of a platform
Install is one command, update is replacing a file, removal is deleting a file. A platform you have to deploy in order to deploy infrastructure has a chicken-and-egg problem.
Install writes to the repository, not to the cluster
The install command does not mean "install now". It means "record that this should exist". ArgoCD does the installing, and that changes the meaning of every other operation.
An application update is a commit
The chart version is pinned in the repository. So an update shows up in the diff, a rollback is a reverted commit, and "it updated itself" becomes impossible.