Paramify
Customer-operated compliance-documentation and security-plan platform installed with the vendor's platform installer or Helm.
10 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Helm / Kubernetes operator; Kubernetes manifests
Runs in
Documented customer environment
EKS or AKS application containers, PostgreSQL, object storage and workload identity.
- AWS: Customer cloud account
- Azure: Customer cloud account
- Google Cloud: Customer cloud account
- AWS
- Azure
- Google Cloud
Servers / containers
Operated by
Your team
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.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
AWS EKS via PPI ↗ · Source checked 2026-11-19
- Azure: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Azure AKS via Helm ↗ · Source checked 2026-11-19
- Google Cloud: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
# Paramify configuration # # Example install: # helm registry login registry.paramify.com --username paramify@mycompan ↗ · Source checked 2026-11-19
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Helm / Kubernetes operator; Kubernetes manifests |
|---|---|
| Infrastructure | Servers / containers 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. |
| Licensing model | Commercial Only Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. |
| License | Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
4 of 12 fields researched (33%) · 2 documented · 2 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
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.
Paramify self-hosted documented provider login; planned SAML excluded · Source ↗ · Okta configuration ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
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.
Paramify deployment example; review the full linked installation instructions · Deployment artifact ↗ (main (moving branch)) · Reviewed 2026-11-19
Documented · Editor reviewed.
- Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing
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.
Paramify complete production footprint remains unconfirmed · Source ↗ · Reviewed 2026-11-21
Sources checked — unresolved · Editor reviewed.
- License pricing
Not confirmedEvidence and scope for License pricing
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.
Selected self-hosted commercial product; contract confirmation remains necessary · Source ↗ · Reviewed 2026-11-19
Sources checked — unresolved · Editor reviewed.
Show all fields (8 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
- Release snapshot / cadence
- Not researched Supply a public source.
Scope & considerations
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.
Category fit
- Policy & procedure management
- Customer-operated compliance-documentation and security-plan platform installed with the vendor's platform installer or Helm.
Compare within Policy & procedure management
- Documize Self-HostedSelf-hosted knowledge management with structured documents, templates and controlled publication workflows.
- Railway
- eramba (Enterprise Self-Hosted)Source-available commercial GRC software with supplier-assessment and policy workflows.
- AWS
- Azure
- FormKiQ Policy and Procedure Management Directory PublisherManage policies, procedures, and organisational knowledge with scheduled reviews, controlled revisions, approvals, acknowledgements, and retirement history.
- AWS
- Hyland OnBase On-PremiseCustomer-hosted enterprise content and case platform for document-heavy business processes.
- AWS
- Azure
- Google Cloud
- IBM OpenPages on Software HubLicensed governance, risk and third-party-control application installed as a Software Hub cartridge.
- IBM Cloud
- M-Files On-PremisesCustomer-operated document vault and information-governance platform with metadata-driven workflows.
- AWS
- Azure
- Google Cloud
- RegScaleCommercial self-hosted governance and policy platform with provider-specific container and Kubernetes guides.
- AWS
- Azure
- Google Cloud
- SAP Process Control (On-Premise)Licensed SAP internal-control and policy lifecycle management application.
- AWS
- Azure
- Google Cloud
These products address related workflows; read their category-fit notes before comparing scope. See all of Policy & procedure management →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- AWS EKS via PPI ↗docs.paramify.com
- Azure AKS via Helm ↗docs.paramify.com
- # Paramify configuration # # Example install: # helm registry login registry.paramify.com --username paramify@mycompan ↗raw.githubusercontent.com
- GCP GKE Terraform ↗github.com
- Deployment Options ↗docs.paramify.com
- Paramify Policies & SSPs ↗www.paramify.com
- Terms & Conditions ↗www.paramify.com
- Access & Services Agreement ↗www.paramify.com
- Support Commits (`2026-10-29`) ↗github.com
- Legacy Release Notes ↗docs.paramify.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- AWS EKS via PPI ↗ · AWS
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- Azure AKS via Helm ↗ · Azure
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- # Paramify configuration
#
# Example install:
# helm registry login registry.paramify.com --username paramify@mycompan ↗ · Google Cloud
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- AWS EKS via PPI ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked