PEMACS

DEPLOYMENT & ARCHITECTURE

Run PEMACS where your organisation needs it.

Choose a managed cloud deployment or keep the platform inside customer-controlled infrastructure. PEMACS is designed to make the operational boundary clear.

DEPLOYMENT OPTIONS

One product.
Three operating models.

Deployment changes where the platform runs—not the discipline of the asset record, its permissions or its reporting.

01MANAGED

PEMACS Cloud

A centrally managed environment for organisations that want straightforward access without operating the underlying infrastructure.

  • Secure browser access
  • Managed platform releases
  • Suitable for distributed teams and branches
02CUSTOMER CONTROLLED

On-premise

A containerised deployment installed inside infrastructure provided and governed by the customer.

  • Customer-controlled database and files
  • Local backup and recovery procedures
  • Versioned update and rollback process
03INTERNAL ACCESS

Private local network

An on-premise arrangement that users reach over the customer LAN without making the application publicly accessible.

  • No public application URL required
  • Access governed by customer networking
  • Explicit outbound connections only

A CLEAR OPERATING BOUNDARY

Local operation does not require public exposure.

An on-premise PEMACS installation can remain accessible only within the customer network. Application data, uploaded files, database storage and backups stay under customer control.

Inside the customer environmentApplication, database, files and backups
Approved outbound servicesLicensing, updates, email and selected integrations
Optional public accessCustomer-managed domain, TLS and network policy

ON-PREMISE DELIVERY

A controlled installation and update path.

PEMACS is packaged as versioned containers so an approved release can be installed, backed up, updated and rolled back predictably.

01

Prepare

Confirm the virtual machine, network address, storage, backup location and outbound access.

02

Install

Deploy the approved PEMACS release and create the initial organisation administrator.

03

Validate

Verify health, authentication, permissions, data persistence and customer access.

04

Operate

Use controlled backup, update, support and rollback procedures throughout the deployment.

PLAN THE RIGHT ENVIRONMENT

Discuss your infrastructure, access and data-control requirements.

We will help define the appropriate cloud, on-premise or private-network arrangement.

Request a deployment discussion →