Procedure Platformby MethodMinded
Settings
← Procedure Platform

Deployment and licensing guide

Choose the way your team will run Procedure Platform

Procedure Platform is designed for teams that need clear ownership of procedure content, execution records, and the way the application is operated. This guide explains the hosted and private deployment boundaries currently planned for release.

Hosted workspace

The hosted workspace is the simplest way to evaluate and operate Procedure Platform. The service manages the application runtime and its configured data services for you, while your organization remains responsible for procedure content, access decisions, review decisions, and the information entered into the workspace.

Hosted operation is not a promise of regulated electronic signatures, customer-specific uptime, or zero-downtime changes. Use your organization's required approval, continuity, and information-security processes for work that needs them.

Private appliance

The private appliance profile targets Ubuntu LTS with Docker Compose, local identity and filesystem defaults, and offline-friendly operation. The first customer distribution model is private VMware-first, targeting VMware vSphere and ESXi. Proxmox VE and KVM remain validation targets, not a second support promise.

A private installation gives the operator control of the host, network, storage, backup schedule, and update window. It does not make the operator's procedures automatically safe, approved, compliant, or suitable for every environment.

Trials and licensing

Trials use time-based signed entitlements so an evaluation has a clear start, end, and organization boundary. A successful purchase provides perpetual runtime rights for the licensed release, while minor updates and support are available for the fixed term stated in the entitlement. Major updates require a separate entitlement or purchase when applicable.

The product is not designed to require forced phone-home access for normal private operation. Operators should retain an export of their procedure source and records according to their own continuity and retention requirements.

Backups, updates, and support boundaries

Operators own the backup and restore plan for a private appliance. A usable plan should cover the database, provider-aware media and evidence, configuration, restore credentials, readiness checks, and a rollback or recovery procedure. Test restores before relying on them.

Updates are operator-controlled changes with a planned maintenance window. The application does not silently mutate itself or promise that every update is zero-downtime. Review the installed appliance's operations pages for the release-specific health, backup, and recovery signals.

Support boundaries follow the selected deployment profile and entitlement. Support can help with the shipped application and documented operating path; it does not replace your infrastructure, security, regulatory, safety, or records-management responsibilities.

What this product does not promise

  • It is not a regulated electronic-signature service.
  • It does not certify that a procedure is safe, compliant, or approved.
  • It does not promise customer zero-downtime operation or automatic evidence deletion.
  • It does not promise that every hypervisor, identity system, storage provider, or network topology is supported.