Skip to main content
Free and Team prices are public. Enterprise is priced per deployment — talk to sales. The same terms apply whether you use OpenWork Cloud or self-host. There are no deployment fees, and support is included in every paid plan.

​
Plans

​
Add-ons

Available on Team and Enterprise, billed per member alongside the plan: Analytics, SCIM, desktop policies, and white-labeling are the Enterprise Features — defined in the subscription terms and reserved for the Enterprise plan (and for evaluations and pilots, so you can test what you would buy). Enterprise white-labeling covers your own internal deployment. External distribution, managed service use, or resale under your branding requires a separate written agreement. Enterprise is an annual contract with a 60-day opt-out, so you can leave early if it does not work for you. Discounts are by seat count and term only.

​
How licensing works

The repository uses a directory-split license, similar to GitLab:
  • Everything outside ee/ is MIT. The desktop app and core platform are open source and free for any use.
  • Everything under ee/ (OpenWork Den, the org control plane) is source-available under the OpenWork EE License. The code is public so your security team can audit exactly what you deploy.
Under the EE License, no subscription is required for:
  1. Production use by organizations with up to 5 users. Enterprise Features (analytics, SCIM, desktop policies, white-labeling) are excluded and require a plan.
  2. Internal evaluation for up to 30 days, at any user count, with all features — extendable in writing.
  3. Development and testing.
Beyond those grants, production use requires a subscription per the subscription terms. Every ee/ release additionally converts to MIT two years after publication. Versions released before the EE License was adopted remain under their original license (FSL-1.1-MIT), and each release is governed by the license text it shipped with — license updates are never retroactive. For the promises we make about how this split is stewarded over time — what can and cannot move between tiers, and how the MIT conversion works — see Stewardship.

​
Evaluating and pilots

You can evaluate self-serve for free for 30 days. The pull-only Docker Compose stack is the quickest way to deploy the control plane in your own environment without cloning or building the repository. Need longer? Evaluation extensions are granted in writing — ask us. For Enterprise, the standard path is the annual contract with its 60-day opt-out — you get the full product and a supported onboarding plan from day one, and can leave in the first two months if it is not a fit. Where a deployment is integration-heavy (SSO, SCIM, self-hosting), we can run a paid 30–60 day pilot at your quoted rate with the pilot fee credited to your first year. Talk to sales.

​
Why the enterprise code is public

Our buyers are security teams. Publishing the enterprise source means you can read every line that runs inside your network before you run it. What a subscription pays for is the right to run it in production at scale, plus a supported, patched release stream and a vendor who is contractually accountable.