Canonical Landscape vs KintoHub

Canonical Landscape manages and monitors Ubuntu deployments, including desktops, servers, cloud instances and IoT devices. It can install, update and remove software, apply automated update and security-patch policies, and configure users and groups. For monitoring, it can alert on updates, chart temperature, disk, memory and system-load trends, show running processes and collect custom metrics. It also supports patch-compliance reporting, role-based access control, audit logging, APT repository mirroring and custom package management. Landscape can run as multi-tenant SaaS, as a Canonical-managed single-tenant service, or self-hosted on cloud or on-premises infrastructure, including air-gapped environments. One instance can manage up to 40,000 machines, with larger deployments possible. A scriptable API supports customization and integrations with configuration-management, monitoring and ticketing systems. Self-hosted Landscape and SaaS included with Ubuntu Pro are listed at free. Managed options cost $6,861 a year on supported public-cloud or virtualization environments, or $9,470 a year on bare metal, billed per physical machine. Ubuntu Pro offers a 30-day enterprise trial.

KintoHub is an open source build and deployment platform for building from Git repositories and deploying to Kubernetes. It supports websites, APIs, jobs, and databases. Its documented workflow turns source code into KintoBlocks, groups them into a project, deploys the project, and makes the app accessible through APIs. Users can deploy from public or private GitHub, Bitbucket, and GitLab repositories with a valid Git URL; CI/CD uses GitHub Workflows and a custom GitHub Action. Deployment options include DockerHub images, Dockerfiles, Helm charts, multiple environments, and release rollbacks. The catalog lists MongoDB, MySQL, PostgreSQL, Minio, RabbitMQ, NATS, Redis, Elasticsearch, and InfluxDB. Web app features include custom domains, environment variables, metrics, autoscaling, and support for server-side rendering or always-running servers. The free plan includes three services with 256 MB each, up to 1 GB persistent data, and up to three shared vCPU, with no credit card required. Self-hosting uses Helm on Kubernetes, but requires an external Docker registry.