Keel Linux

Home / Appliances

Appliances

45 appliances for Proxmox VE

The stable channel holds 11 applications, each as a signed LXC template and a signed ISO. Release 2026-11-10 published 8 of them. Release 2026-11-11 added MariaDB, Redis and ntfy. 34 more are in development. Every appliance is a mesh-native Proxmox container that can join a private cloud on day one.

Test method

How the images were tested

Each image passed the commissioning test before it was published (decision 0075). The test installs the image on 2 sites, BR1 and BR2.

What the test does

  • It installs the LXC template on BR1 and on BR2 in 2 ways: answered on the console, and described before the boot.
  • It installs the ISO in a virtual machine on BR1 and on BR2.
  • It installs the modes simple, cloud simple and cloud advanced (decision 0076). The primary is on BR1 and the replica is on BR2.
  • It checks the services, the web addresses and the screens of each node.

What a pass needs

  • A pass is green only if every check of the pass is green.
  • No image is published before every pass of the image is green.
  • Each application of release 2026-11-10 has 8 passes: 6 for the template and 2 for the ISO. Its card gives the count of checks.
  • In release 2026-11-11, MariaDB has the same 8 passes. Redis and ntfy have no cloud mode, so each has 6 passes: 4 for the template and 2 for the ISO.
  • The page of each application has the commissioning table and the screens of each pass.

Decision 0075, the commissioning testDecision 0076, the installation mode screens

What the tests do not show

In cloud advanced, the witness was on BR1, so 2 of the 3 etcd members were in one site. The commissioning table gives a count of checks. It does not give failover times or a count of lost writes. The failover tests below give such numbers, but they used earlier builds, not the images of release 2026-11-10.

Evidence: LNMP 19.0-4 and LNPP 19.0-5Evidence: MariaDB pairEvidence: PostgreSQL pairEvidence: Odoo 19.0-11

The images

One card for each appliance

11 cards: the 8 applications of release 2026-11-10, and MariaDB, Redis and ntfy of release 2026-11-11. Each version and link is the image that the stable channel holds now.

  • Stable Signed 19.0-13

    Keel Core

    The base of every Keel appliance.

    Stack. Debian 13, WireGuard, etcd, CrowdSec and the first-boot tools.

    Modes. Simple, cloud simple and cloud advanced. In cloud simple, you promote the replica by hand. In cloud advanced, the replica takes over by itself.

    Status. Stable release 2026-11-10, signed. The commissioning test ran 8 passes on BR1 and BR2: 413 checks, all passed.

    Page of Keel CoreRelease 19.0-13Template 19.0-13ISO 19.0-13

  • Stable Signed 19.0-13

    Keel Web

    The web layer under the web appliances.

    Stack. nginx, the Coraza WAF and Anubis, on Core.

    Modes. Simple, cloud simple and cloud advanced. In cloud simple, you promote the replica by hand. In cloud advanced, the replica takes over by itself.

    Status. Stable release 2026-11-10, signed. The commissioning test ran 8 passes on BR1 and BR2: 482 checks, all passed.

    Page of Keel WebRelease 19.0-13Template 19.0-13ISO 19.0-13

  • Stable Signed 19.0-6

    Keel LNMP

    The base stack for PHP applications.

    Stack. nginx, MariaDB 11.8 and PHP-FPM 8.4, on Web.

    High availability. A MariaDB pair with semi-synchronous replication and a VIP. Cloud advanced adds an etcd of 3 members.

    Modes. Simple, cloud simple and cloud advanced. In cloud simple, you promote the replica by hand. In cloud advanced, the replica takes over by itself.

    Status. Stable release 2026-11-10, signed. The commissioning test ran 8 passes on BR1 and BR2: 590 checks, all passed.

    Page of Keel LNMPRelease 19.0-6Template 19.0-6ISO 19.0-6

  • Stable Signed 19.0-9

    Keel LNPP

    The base stack for Python applications.

    Stack. nginx, PostgreSQL 17 and Python 3 with gunicorn, on Web.

    High availability. A PostgreSQL pair with a read-only standby and a VIP. Cloud advanced adds an etcd of 3 members.

    Modes. Simple, cloud simple and cloud advanced. In cloud simple, you promote the replica by hand. In cloud advanced, the replica takes over by itself.

    Status. Stable release 2026-11-10, signed. The commissioning test ran 8 passes on BR1 and BR2: 510 checks, all passed.

    Page of Keel LNPPRelease 19.0-9Template 19.0-9ISO 19.0-9

  • Stable Signed 19.0-9

    Keel PostgreSQL

    PostgreSQL as an appliance of its own.

    Stack. PostgreSQL 17 on Core.

    High availability. A primary and a read-only standby, synchronous commit and a VIP. Cloud advanced adds an etcd of 3 members.

    Modes. Simple, cloud simple and cloud advanced. In cloud simple, you promote the replica by hand. In cloud advanced, the replica takes over by itself.

    Status. Stable release 2026-11-10, signed. The commissioning test ran 8 passes on BR1 and BR2: 437 checks, all passed.

    Page of Keel PostgreSQLRelease 19.0-9Template 19.0-9ISO 19.0-9

  • Stable Signed 19.0-7

    Keel Laravel

    A base for Laravel applications.

    Stack. Laravel 12 on LNMP: nginx, MariaDB and PHP-FPM 8.4, with Composer, Node.js and npm.

    High availability. The MariaDB pair and the VIP of LNMP.

    Modes. Simple, cloud simple and cloud advanced. In cloud simple, you promote the replica by hand. In cloud advanced, the replica takes over by itself.

    Status. Stable release 2026-11-10, signed. The commissioning test ran 8 passes on BR1 and BR2: 634 checks, all passed.

    Page of Keel LaravelRelease 19.0-7Template 19.0-7ISO 19.0-7

  • Stable Signed 19.0-21

    Keel WordPress

    A WordPress site on a database pair.

    Stack. WordPress 7.1.4 on LNMP: nginx, MariaDB and PHP-FPM 8.4.

    High availability. The MariaDB pair and the VIP of LNMP.

    Modes. Simple, cloud simple and cloud advanced. In cloud simple, you promote the replica by hand. In cloud advanced, the replica takes over by itself.

    Status. Stable release 2026-11-10, signed. The commissioning test ran 8 passes on BR1 and BR2: 532 checks, all passed.

    Page of Keel WordPressRelease 19.0-21Template 19.0-21ISO 19.0-21

  • Stable Signed 19.0-18

    Keel Odoo

    Odoo on a database pair.

    Stack. Odoo 18.0 Community on LNPP: nginx and PostgreSQL 17.

    High availability. The PostgreSQL pair and the VIP of LNPP.

    Modes. Simple, cloud simple and cloud advanced. In cloud simple, you promote the replica by hand. In cloud advanced, the replica takes over by itself.

    Status. Stable release 2026-11-10, signed. The commissioning test ran 8 passes on BR1 and BR2: 595 checks, all passed.

    Page of Keel OdooRelease 19.0-18Template 19.0-18ISO 19.0-18

  • Stable Signed 19.0-12

    Keel MariaDB

    MariaDB as an appliance of its own.

    Stack. MariaDB 11.8 on Core.

    High availability. A primary and a read-only replica, semi-synchronous replication and a VIP. Cloud advanced adds an etcd of 3 members.

    Modes. Simple, cloud simple and cloud advanced. In cloud simple, you promote the replica by hand. In cloud advanced, the replica takes over by itself.

    Status. Stable release 2026-11-11, signed. The commissioning test ran 8 passes on BR1 and BR2: 503 checks, all passed.

    Page of Keel MariaDBRelease 19.0-12Template 19.0-12ISO 19.0-12

  • Stable Signed 19.0-13

    Keel Redis

    Redis for sessions, queues and caches.

    Stack. Redis 8.0 on Core.

    Modes. Simple. This image has no cloud mode.

    Status. Stable release 2026-11-11, signed. The commissioning test ran 6 passes on BR1 and BR2: 182 checks, all passed.

    Page of Keel RedisRelease 19.0-13Template 19.0-13ISO 19.0-13

  • Stable Signed 19.0-6

    Keel ntfy

    The alert server of a site: it sends a message to a phone.

    Stack. ntfy 2.11 on Web.

    Modes. Simple. This image has no cloud mode.

    Status. Stable release 2026-11-11, signed. The commissioning test ran 6 passes on BR1 and BR2: 246 checks, all passed.

    Page of Keel ntfyRelease 19.0-6Template 19.0-6ISO 19.0-6

The 22 images of the stable channel are signed: the template and the ISO of each of the 11 applications.

In development

34 appliances on the roadmap

Each of these will be a mesh-native Proxmox container with the same pair, VIP and etcd support as the current images. They are listed by category, not by release order.

Infrastructure & network

  • Tayga

    NAT64 gateway for IPv6-only networks

  • PowerDNS

    Authoritative or recursive DNS with PostgreSQL

  • MinIO

    S3-compatible object storage

  • Grafana + Prometheus

    Monitoring, metrics and dashboards

  • Observium

    Network monitoring with autodiscovery

  • Ansible

    Automation and configuration management

  • COTURN

    TURN/STUN relay for NAT traversal

  • File Server

    Samba and NFS file sharing

Identity, security & email

  • Vaultwarden

    Bitwarden-compatible password manager

  • Zitadel

    Identity and access management (IAM)

  • Stalwart + Bulwark

    Mail server with spam and threat filtering

Communication & collaboration

  • Jitsi Meet

    Video conferencing with screen sharing

  • Mattermost

    Team messaging and collaboration

  • SimpleX + Tor

    Private messaging with onion routing

  • Etherpad

    Real-time collaborative text editor

  • FusionPBX

    PBX and VoIP on FreeSWITCH

Fediverse (ActivityPub)

  • Mastodon

    Federated social network

  • PeerTube

    Federated video hosting

  • Loops

    Federated short video sharing

  • PieFed

    Federated link aggregator

CMS, education & wiki

  • Nextcloud

    File sync, calendar and contacts

  • Moodle

    Learning management system

  • MediaWiki

    Wiki engine behind Wikipedia

  • LimeSurvey

    Online survey and questionnaire platform

Analytics & business intelligence

  • Apache Superset

    Data exploration and visualization with Celery

  • Plausible

    Privacy-first web analytics

Development & runtime

  • Forgejo

    Self-hosted Git forge

  • Node.js

    JavaScript and TypeScript runtime

  • Ruby on Rails

    Web framework with PostgreSQL

  • Django

    Python web framework with PostgreSQL

  • Tomcat

    Java web application server

Media, IoT & database

  • Media Server

    Jellyfin media streaming

  • Zigbee2MQTT

    IoT bridge from Zigbee to MQTT

  • CouchDB

    Document database with built-in replication

Get an image

Download, check, create the container

The Templates dialog of the Proxmox web interface does not show Keel templates. Use keel-pve, or download the file from the mirror. The commands are the same as on the page of each application.

With keel-pve

keel-pve gets the signed index of the Keel templates and checks the template against it. Install keel-pve from the Keel archive, suite trixie-testing. Then run these commands on the Proxmox node:

# example: Keel LNMP. Change keel-lnmp for another application.
keel-pve update
keel-pve download local keel-lnmp

With the file

  1. Download the template, its .sha512 and its .sha512.asc from the mirror.
  2. Check the signature.
  3. Check the digest.
  4. Copy the template to /var/lib/vz/template/cache/ on the Proxmox node.
  5. Make the container.
# example: Keel LNMP 19.0-6. Change the names for another image.
M=https://mirror.keellinux.org/images
F=debian-13-keel-lnmp_19.0-6_amd64.tar.zst
curl -fLO $M/$F -O $M/$F.sha512 -O $M/$F.sha512.asc
curl -fLO https://archive.keellinux.org/keel-images-keyring.asc

sqv --keyring keel-images-keyring.asc $F.sha512.asc $F.sha512
sha512sum -c $F.sha512

cp $F /var/lib/vz/template/cache/
pct create 200 local:vztmpl/$F --hostname lnmp \
  --unprivileged 1 --features nesting=1 \
  --net0 name=eth0,bridge=vmbr0,ip6=auto

The .sha512.asc file holds two signatures: one by the archive key and one by the images key. The command uses the images keyring, so sqv prints "Missing key" for the archive key. This is expected. If sqv prints the fingerprint E71DB9C3CA6AC18075395CC3ED3A709C4F3E2F3C, the signature is good.

Start the container and log in on its console as root. The first boot asks its questions there.

The ISO has the same 3 files: change .tar.zst to .iso in the names. Boot the machine from the ISO and install. The first boot of the installed system asks the same questions as the template.

Cloud simple needs 2 nodes of the same appliance. Cloud advanced needs 2 data nodes and a witness. The page of each application has a guide for each mode, with one column for each node. The cloud page describes the modes.

Test an image and tell us

Open an issue or a pull request on git.pop.coop, or on GitHub. A bridge copies issues, comments and pull requests between the two. You can also write in the Proxmox forum thread.

Proxmox forum thread News