Penstock

Guide / Plans, privacy and help

Plans and licence

Penstock is free, and what only Penstock does is Pro or Team. One rule decides which one a feature needs.

Free

This page is the reference for what each plan includes. For prices, refunds, VAT and the questions people ask before buying, see Pricing.

Choose a plan

Free

No charge

The editors, checks, deploy, Monitor, export, share and import. Every new machine also starts with 30 days of Pro.

Get Penstock

Pro

USD 9.00 per month

USD 90.00 per year

For your own machine. Adds what only Penstock does: auto layout, flow analysis, code links, test-case runs and more.

Buy Pro

Team

USD 29.00 per seat per month

USD 290.00 per seat per year

Everything in Pro, inside a pipeline as well: the review bot, pull request reports, baselines and SARIF.

Buy Team

The price you pay is the one shown at checkout. You choose monthly or yearly at checkout. A Buy button opens the checkout on Polar's own page. See Security and privacy.

The one rule

Everything that earlier releases had, and everything other tools give away, is free. What only Penstock does is Pro or Team.

A paid feature needs Pro on your own machine and Team inside a pipeline. A pipeline is any run where the environment variable CI is set. There are no exceptions for a single feature or a single flag.

Every machine starts with 30 days of Pro. A pipeline gets no trial. On a fresh install, when the trial has just started, Penstock shows a one-time welcome in its notice banner: Try every Pro feature free for 30 days. It says that the main Free features stay free, with no time limit, and that nothing is lost, and it has a button to the plans. It shows once, in every host and in all 18 languages, and never to someone who already had Penstock, a trial, a licence or a token, after the trial has ended, or in a pipeline.

What each plan gives

PlanWhat it includes
Free

In the editors: the BPMN, DMN and form editors, the properties panels, element templates and the connector browser, scripts in a code editor of your tool, token simulation, the diagram check with the drawing and the bpmnlint rules, deploy, Monitor, export, the hand-drawn look, opening a run that already exists, the visual diagram diff in version control, going from a Camunda 7 delegate to its class or bean, sharing a diagram as one HTML file, and importing from draw.io, Visio, Signavio, Bizagi, Flowable and Camunda Modeler projects.

New in 26.11.0, free with no time limit: the language server (penstock lsp) for editors without a plugin; the element template editor and the "Why not loaded" diagnosis; the connections map; the viewer for CMMN case models; the AI agents of Camunda 8 listing, their Agents tab and checks; a single rename across the project; drift of one environment and deploy --only-changed (Drift, promote and protected environments); evidence verify (Evidence pack); the verdict and counts of an AI receipt; up to 3 saved test cases per decision in the DMN Tests tab and penstock test dmn; showing the active policy; migrate plan (the list of changes the conversion would make) and the first 3 scenarios of migrate verify; the previews of templates generate, migrate agents, agents scenario and incident scenario; and the 18 interface languages.

The Camunda 7 to Camunda 8 analysis and its report are free too.

The command palette and every action in it, the sidebar, the check card and the Problems tab, transaction boundaries, the first-run tour, and the findings in your tool's own Problems window.

On the command line: init, doctor, check (the drawing, rules and form sections), migrate analyze and migrate report, fmt, diff, export, show, deploy, share, import, connectors, license, trust, templates check, lsp, connections, agents, drift (one environment), evidence verify, policy show, refactor rename, update, mcp (the server itself), and edit --schema.

The MCP tools list_diagrams, show_diagram, element_context, check_diagram, search_elements, diff_diagrams, migrate_analyze and export_image, which only read, explain, analyse and draw, on BPMN, DMN and form files.

Pro
on your machine
  • Auto layout.
  • Variable checks (since 26.10.1): a variable written and never read, a read before any write, a field a worker does not fetch, and the field and name checks of penstock.yaml.
  • Flow analysis, and the decision table check. The form check is lint, so it is free.
  • Pictures of what changed in the visual diagram diff, from penstock diff --images.
  • Modelling conventions from penstock.yaml.
  • Converting Camunda 7 to Camunda 8: the preview, penstock migrate convert and the job worker skeletons.
  • Scenarios: test cases on a local engine, step by step.
  • Debug a process at breakpoints on a local or test engine.
  • The AI chat, with the agent of your choice. Anyone sees the input; sending a message needs Pro, and Penstock offers it at that moment.
  • The link between diagrams and code: code links. From a step to its worker and back, usages, hints above the code, variables and error codes across both, tests run from the diagram, coverage on it, the debugger's position on the diagram, linked repositories, and Check Workers.
  • In the command line: layout, check --only flow, scenarios list, junit, scenarios run, scenarios generate, code, templates generate, docs, diff --images, edit, report, check baselines, and findings as SARIF or GitHub annotations.
  • The review bot, when you run it on your machine.
  • New in 26.11.0: evidence build (the policy and environments sections of the pack are Team); promote and drift --against (comparing two environments); penstock policy commands that write (init, add-rule, pin, verify, sync); check --require-receipt, the full AI receipt and auto-repair; migrate verify beyond its first 3 scenarios; test dmn with more than 3 cases per decision, JUnit output and --min-rule-coverage; templates generate from an API description beyond its first 3 operations; migrate agents --write, agents scenario (agents scenario --write) and the Migrate to the 8.10 template and Make scenario buttons; connections --env --against; refactor bulk and refactor extract; saving and running an incident scenario, Fix end to end and Propose a fix; the heat map and replay in Monitor.
  • The MCP tools analyze_flow, list_scenarios, check_code_links, edit_diagram, create_diagram, layout_diagram and run_scenarios, and the gap and overlap check of check_diagram on a DMN decision table. Each needs the same plan as its command line twin.
Team
in a pipeline

Everything in Pro, inside a pipeline. That includes the review bot in pull and merge requests, the pull request report, check baselines, and findings as SARIF or GitHub annotations in the code review. Every paid command in a pipeline needs Team. Enforcing a policy pack in a pipeline, and approval records for a protected environment, are part of Team.

Not sure what a page needs? The tag under its title says. Free means free. Pro means a paid feature.

What you see when you reach a paid feature

Nothing else in the editor changes. When you reach for a paid feature you do not have, Penstock explains what it does and offers to buy it or to sign in, at that moment.

A terminal running penstock scenarios run on a machine without a licence. It says Process test runs are part of Penstock Pro, and gives two commands: penstock license buy and penstock license login
What a paid command prints in a terminal without a licence.

Paying

Payments are handled by Polar, the reseller and merchant of record. Polar also takes care of VAT and invoices. You can cancel at any time from the link in the receipt. After you pay, Penstock notices by itself and sends a sign-in code to the address that paid. There is no key to copy. One key covers three machines, and you can cancel at any time. Team is priced for each seat, and its seats are given out in Polar's customer portal. See Buying and signing in.

How the licence is checked

The licence is a signed token, not a flag. A small licence service turns Polar's answer into a token signed with a key only it holds, and the plugin, the command line and the editor carry the public half and check the signature themselves, offline. A file edited by hand, a redirected address or a server pretending to be the licence service cannot make a machine Pro.

What is on the machine is the token and nothing else: no key, no tier, no date you could edit. penstock license says which licence this machine has and where it comes from, and during the trial it says the trial is on and until when, instead of saying there is no licence. See Buying and signing in.

Free Pro for students, teachers and open-source maintainers

Students, teachers and open-source maintainers can get Pro for free. Penstock shows it in three places, and only when the application address is set: the licence dialog, the message that explains a paid feature, and the output of penstock license. While no address is set, nothing about it is shown anywhere. See Buying and signing in.

Common problems

A feature that worked yesterday now asks me to buy Pro.
Your 30-day trial has ended, or your licence was released or ended. Run penstock license to see which licence this machine has.
It works on my laptop but the pipeline says it needs Team.
That is the rule: a pipeline needs Team for every paid feature. penstock init --ci writes a pipeline for the licence on the machine that ran it, so its first run does not fail on something nobody bought.
Which plan do I need for the review bot?
Team in a pipeline. Pro is enough to run it on your own machine.