Skip to main content

Licensing & Distribution

OpenProdkt offers two ways to buy and run the product, and keeps billing and access management simple for each.

Plans​

  • Cloud: A hosted subscription. Sign up, pay online, and start using your organization right away. Upgrades, payment methods, invoices, and cancellation are all self-service.
  • Enterprise: A licensed deployment for organizations that run OpenProdkt in their own environment. Access is governed by a contract and a license, with support for both connected and offline environments.

How access is managed​

Every plan resolves to the same simple question for every request: is this action allowed, denied, or does it require approval?

  • Your plan determines what features, limits, and modules are available to your organization.
  • Every request is still checked against your policies and permissions, regardless of plan.
  • Enterprise licenses can be renewed automatically when connected, or updated manually in offline environments — either way, your team doesn't need to change how the product is used.

Getting started​

  • Cloud customers can sign up and start immediately from the Quickstart.
  • Enterprise customers should talk to their OpenProdkt account team to arrange a license and deployment.

Customer-managed services​

Self-hosted Enterprise deployments connect to services operated in the customer's environment. These services are not included in the application package by default:

  • The relational database stores governance records, including decisions and audit history.
  • An S3-compatible object store holds supporting delivery artifacts. A customer-managed MinIO Community or other compatible service can be configured, provided it supports the S3 operations OpenProdkt uses. MinIO Community is licensed under AGPLv3 and is distributed from source; OpenProdkt does not bundle it. Customers choosing MinIO are responsible for selecting a distribution and meeting its license and maintenance requirements.
  • An SMTP service relays product notifications. Configure OpenProdkt to use the customer's SMTP relay for production email delivery.

Mailpit is MIT-licensed and can be useful for local development or integration testing. It captures messages by default rather than delivering them to recipients. Although Mailpit supports explicit SMTP relay configuration, it is a testing tool, not the recommended production mail relay. Keep its SMTP and web interfaces restricted to trusted networks.

Transparent proxy delivery​

Enterprise customers can place the OpenProdkt transparent proxy in front of existing HTTP and gRPC services. The proxy is delivered as a container image through your account team. Docker Compose is the supported way to run it today, for evaluation and on-premises deployments. Other orchestration options are planned. For setup and configuration, see Transparent Proxy.

The proxy requires the proxy.enabled entitlement. When it is absent, /v1/proxy/evaluate returns 403 and every proxied request is blocked.

The proxy does not read or store request bodies and does not hold a request while approval is pending. Blocked requests receive an immediate denial, and the transparent proxy retry flow describes how the original request is resubmitted after approval.

Principle​

Your plan defines what you can use. The product enforces it consistently, wherever it runs.