On-premise overview

The on-premise package runs MassAccess application services in the company's infrastructure. It is intended for teams that need to operate the deployment locally and can provide the required outbound connectivity for licensing, metering, billing, image delivery, and messenger integrations.

InformationDocker Compose includes 17 permanent services: the application, bundled stores, Receiver/RabbitMQ/Agent and a PKI helper. This is one single-node package without a high availability promise. Kubernetes follows its separate Helm lifecycle and storage/transport prerequisites.

Delivery methods

The methods use the same application product but have different artifacts, prerequisites, commands, storage boundaries, and rollback procedures.

Docker Compose

A single package with bundled data services and scripts for installation, health checks, upgrade, and rollback on one Linux server.

Open the Compose installation

Deploy MassAccess on-premise on Kubernetes with Helm

Two independently managed Helm releases for nine application workloads and optional single-node bundled data, with external and mixed placement supported.

Open the Kubernetes and Helm guide

Who this documentation section is for

This section is intended for DevOps engineers and developers who deploy MassAccess in their own infrastructure. It separates Docker Compose and Kubernetes procedures while covering requirements, authorized delivery, installation, exposure, upgrade and rollback, backup and restore, and diagnostics.

On-premise vs SaaS

Characteristic	SaaS	On-premise
Application deployment	Operated by MassAccess	Operated in company infrastructure
Management	massaccess.net dashboard	Local interface
Updates	Automatic, centralized	Operator-controlled: upgrade.sh or Helm lifecycle

Architecture

The on-premise application runs as a Compose stack or as Kubernetes releases in company infrastructure. A customer-managed TLS entry point handles dashboard, API, WebSocket, and webhook traffic; the company also owns monitoring and the underlying platform.

InformationApplication services run in company infrastructure; cloud licensing, signed usage metering, and billing remain required.

Licensing model

The on-premise version uses a MassAccess license created in the cloud control panel. Installation activates the license, and regular signed heartbeat and usage data support licensing, metering, and billing. Without an active license, message sending is unavailable.

For details on creating the key and obtaining the delivery package, see the License, usage metering, and billing section.