
# Paramify

Customer-operated compliance-documentation and security-plan platform installed with the vendor's platform installer or Helm.

Canonical page: https://launchinyourcloud.com/directory/paramify/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## Paramify

Customer-operated compliance-documentation and security-plan platform installed with the vendor's platform installer or Helm.

- Listing: https://launchinyourcloud.com/directory/paramify/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Helm / Kubernetes operator; Kubernetes manifests
- Architecture: EKS or AKS application containers, PostgreSQL, object storage and workload identity.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://github.com/paramify/support
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

AWS and Azure guides deploy the actual platform into customer infrastructure. The public access agreement describes SaaS and does not replace the buyer's self-hosted order or licence terms. Compliance-document generation is not an authorization or attestation of the installation. The GKE example includes the actual application Helm install, GCS provider, database, secrets and workload identity alongside its Terraform infrastructure.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

EKS or AKS application containers, PostgreSQL, object storage and workload identity. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- policy-procedure-management: Customer-operated compliance-documentation and security-plan platform installed with the vendor's platform installer or Helm.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.paramify.com/deploy-ppi-eks.html (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.paramify.com/deploy-helm-azure.html (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/paramify/support/main/gcp/values-gke.yaml.example (checked 2026-11-19). 


### Cloud deployment evidence

- AWS EKS via PPI (aws): https://docs.paramify.com/deploy-ppi-eks.html
  EKS or AKS application containers, PostgreSQL, object storage and workload identity. AWS and Azure guides deploy the actual platform into customer infrastructure. The public access agreement describes SaaS and does not replace the buyer's self-hosted order or licence terms. Compliance-document generation is not an authorization or attestation of the installation. The GKE example includes the actual application Helm install, GCS provider, database, secrets and workload identity alongside its Terraform infrastructure.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure AKS via Helm (azure): https://docs.paramify.com/deploy-helm-azure.html
  EKS or AKS application containers, PostgreSQL, object storage and workload identity. AWS and Azure guides deploy the actual platform into customer infrastructure. The public access agreement describes SaaS and does not replace the buyer's self-hosted order or licence terms. Compliance-document generation is not an authorization or attestation of the installation. The GKE example includes the actual application Helm install, GCS provider, database, secrets and workload identity alongside its Terraform infrastructure.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- # Paramify configuration
#
# Example install:
#   helm registry login registry.paramify.com --username paramify@mycompan (gcp): https://raw.githubusercontent.com/paramify/support/main/gcp/values-gke.yaml.example
  EKS or AKS application containers, PostgreSQL, object storage and workload identity. AWS and Azure guides deploy the actual platform into customer infrastructure. The public access agreement describes SaaS and does not replace the buyer's self-hosted order or licence terms. Compliance-document generation is not an authorization or attestation of the installation. The GKE example includes the actual application Helm install, GCS provider, database, secrets and workload identity alongside its Terraform infrastructure.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS EKS via PPI: https://docs.paramify.com/deploy-ppi-eks.html

- Azure AKS via Helm: https://docs.paramify.com/deploy-helm-azure.html

- # Paramify configuration
#
# Example install:
#   helm registry login registry.paramify.com --username paramify@mycompan: https://raw.githubusercontent.com/paramify/support/main/gcp/values-gke.yaml.example

- GCP GKE Terraform: https://github.com/paramify/support/blob/main/gcp/gcp-paramify-gke-infra.tf

- Deployment Options: https://docs.paramify.com/deployment-options.html

- Paramify Policies & SSPs: https://www.paramify.com/

- Terms & Conditions: https://www.paramify.com/legal/terms-and-conditions

- Access & Services Agreement: https://www.paramify.com/legal/access-and-services-agreement

- Support Commits (`2026-10-29`): https://github.com/paramify/support/commits/main.atom

- Legacy Release Notes: https://docs.paramify.com/release-notes.html

### Licensing sources

- https://www.paramify.com/legal/terms-and-conditions

- https://www.paramify.com/legal/access-and-services-agreement

### Infrastructure sources

- https://docs.paramify.com/deploy-ppi-eks.html

- https://docs.paramify.com/deploy-helm-azure.html

- https://raw.githubusercontent.com/paramify/support/main/gcp/values-gke.yaml.example


### Buyer diligence


Research coverage: 4/12 fields (33%); 2 documented, 2 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The vendor explicitly supports Google, Microsoft and Okta login in self-hosted environments, with provider/client setup guides and application-local permissions. The overview still describes SAML as planned; do not treat that date or email magic links as confirmation of current SAML capability. Scope: Paramify self-hosted documented provider login; planned SAML excluded. Source: https://docs.paramify.com/login-options.html (reviewed 2026-11-21). Supporting source: Okta configuration — https://docs.paramify.com/login-okta.html.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The reviewed source supplies deployment configuration for EKS or AKS application containers, PostgreSQL, object storage and workload identity. Set organization-specific secrets, networking, storage and compatible image versions before use. Scope: Paramify deployment example; review the full linked installation instructions. Source: https://github.com/paramify/support/blob/main/gcp/gcp-paramify-gke-infra.tf (reviewed 2026-11-19). Deployment artifact: https://github.com/paramify/support/blob/main/gcp/gcp-paramify-gke-infra.tf. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed installation examples identify Kubernetes, PostgreSQL and object storage, while an example Node heap option configures one process. They do not establish complete production CPU/RAM/storage capacity; document generation workers, database, cluster overhead and HA need workload sizing. Scope: Paramify complete production footprint remains unconfirmed. Source: https://docs.paramify.com/deploy-ppi-eks.html (reviewed 2026-11-21).

- License pricing: Sources checked — unresolved. Deployment requires a Paramify licence and registry credentials, but the public SaaS access agreement does not establish the self-hosted software order, price or support scope. Scope: Selected self-hosted commercial product; contract confirmation remains necessary. Source: https://www.paramify.com/legal/terms-and-conditions (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






