Deployment & control

A home inside
your network.

One self-hosted appliance. A desktop browser console. A clear path from installation to daily operations.

The native appliance

Inside your own
infrastructure.

The native installer targets Debian 13 amd64 and verifies a signed release bundle. Keep the database and application data on separate mounts, and configure an off-box backup copy. Confirm the installation media with your deployment owner.

Read the installation guide
Capacity planning

Plan for your
actual workload.

Size the VM for your device count, polling cadence, stored files, and retention needs. No measured production capacity or devices-per-VM guarantee is published here.

Keep database storage, application data, and backup capacity in the plan. Measure the actual workload during evaluation before choosing production resources.

Operational control

Keep the essentials
close to home.

HTTPS access for staff. Locally managed configuration and credentials. Encrypted backup sets, signed releases, and readiness checks for upgrades.

Optional Microsoft sign-in, SMTP, webhooks, and site collectors connect only the services you choose to configure.

Explore configuration
Inside your district

Cenovel appliance

Staff reach the console over HTTPS. The local appliance connects the estate, monitoring, and operational records.

Conceptual workflow
Cenovel applianceConnected context
Staff browsersHTTPS access
Managed equipmentSSH / SNMPv3 reads
Off-box backupConfigured destination
Conceptual connections · optional services configured separately
Common questions

Before you deploy.

Does Cenovel need the internet?

Inventory and core records are served by the local appliance. Optional Entra ID sign-in, SMTP, webhooks, and off-box backups need connectivity to the services you configure. The console records performance diagnostics locally.

Where does Cenovel run?

The native installer targets Debian 13 amd64 on a customer-managed appliance or VM and verifies signed .cenovel release bundles.

Can we use Docker or another hypervisor?

These customer instructions cover the native appliance inside your own infrastructure. The repository also contains a Compose development setup; it is not a hosted service.

How do remote sites connect?

An optional site collector can serve networks that the appliance cannot route to. Collector reads are limited to configured management networks and credentials. Device reads can use SSH with Device CLI profiles or SNMPv3 authPriv where configured.

What should we prepare before installation?

Plan a console DNS name, management port group, VM resources, separate database and application data mounts, TLS trust, and an off-box backup destination. The installation guide walks through the steps.

Plan the appliance with us.