Review diagrams like you review code
Penstock Team adds a review bot to your pull requests, reports with the changes outlined, baselines so the first run is not red, and SARIF for code scanning. It runs in your own pipeline, and there is no service to register with.
Team costs $29 per seat a month or $290 per seat a year. Individuals do not need Team: Pro covers your own machine. Team is for pipelines.
What a team gets
/penstock full review.penstock check fails in a pipeline when the pin does not match or a forced rule is weakened. Policy pack.check --require-receipt to fail a change an agent made without a valid receipt. Evidence pack, AI receipt.The bot is your own pipeline running penstock bot. It supports GitHub, Gitea, Forgejo, GitLab, Azure DevOps and Bitbucket. Azure DevOps and Bitbucket get the review only, without answers to comments. See Pipelines, reports and the bot for each.
How to set it up
- Buy Team, then give the seats to people in Polar's customer portal.
- Run
penstock init --ci githubon a machine that has Team. It writes the bot and SARIF workflows. The other choices aregitea,forgejo,gitlab,bitbucketandazure. - Store the key that
penstock license keyprints as the secretPENSTOCK_LICENSE.
Seats and cost
A seat is for a person who runs Pro features on their own machine. A pipeline uses a Team key and takes no machine's place, and the key only counts when CI is set. Five people who work on diagrams are five seats: five times $29 a month, or five times $290 a year. How seats are given out is on Buying and signing in.
Trust and procurement
What leaves your machine
- Deploy sends the file you deploy, with the profile's credentials, to the engine address you configured. Nothing else.
- The licence check sends the licence, a one-way hash of the machine's id and the host name as a label. Never a diagram.
- There is no telemetry and no crash reporter. Credentials stay in your tool's secret store, never in project files.
- The review bot never runs hooks that a pull request's configuration declares, answers only people who own, belong to or collaborate on the repository, and never on a pull request from a fork.
The complete list is on Security and privacy.
The licence service
What it receives, what it keeps and for how long is set out in the privacy policy. The licence is a signed token that tools check offline. It lasts 30 days and is renewed once a day when the machine is online. If the service cannot be reached, a valid token keeps working, and a pipeline runs as Free.
Security reports
Report a vulnerability privately, as the security policy describes. Penstock has no third-party security audit or certification.
Third-party components and licence
The open-source components Penstock bundles keep their own licences: third-party notices. Penstock itself is under the end user licence.
If the vendor stops
Penstock is made by one person. In practice that means: your diagrams are plain .bpmn, .dmn and .form files in your repository that open in any other editor, and a licence token that has been issued keeps working offline for up to 30 days.
Invoices and purchasing
Polar is the merchant of record. It collects VAT or sales tax where it applies, and issues receipts and invoices. Vendor details are on About and contact. For anything else about buying, write to oleksandr.havrysh5@gmail.com.
Questions
Do we need a Team key for every developer?
No. A developer needs a seat only to run Pro features on their own machine. The pipeline uses one Team key that takes no seat's place.
Can we use Pro on laptops and Team in the pipeline?
Yes. That is the rule: Pro on your own machine, Team inside a pipeline.
Does the bot send our diagrams anywhere?
No. The bot is your own pipeline running penstock bot. There is no service behind it.
Can we try it first?
Every machine starts with 30 days of Pro. A pipeline gets no trial, so Team features in a pipeline need a Team key.