Skip to main content
Our pricing is public, like the rest of our handbook. The same prices 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 (each with a 30-day free trial) are listed at openworklabs.com/pricing.

​
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 — this matches the Free plan.
  2. Internal evaluation for up to 90 days, at any user count.
  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).

​
Evaluating and pilots

You can evaluate self-serve for free for 90 days — clone the repo, deploy in your own environment, and test at any scale. If you want a supported pilot instead (a dedicated engineering contact, deployment guidance, and response targets), 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.