Runbook vs Process Street

Process Street describes itself as a "Compliance Operations Platform" [1]. It includes workflow automation, document management and an AI compliance agent. Its features include conditional logic, approvals, form fields, automations and SSO [1]. It suits organisations that want one system for complex, form-driven workflows and are fine with a sales-led buying process.

Runbook is a smaller, narrower tool for recurring team checklists. You write a template (or paste a Markdown checklist), start runs on a schedule or from CI, check items off together, and keep an append-only audit trail. It has published flat prices in CHF, is hosted in the EU and is run from Switzerland. Runbook is new and has far fewer features than Process Street.

Prices and features were checked on 2026-11-04 on the vendors' official pages and may have changed since. Process Street is a trademark of its owner. Runbook is not affiliated with, endorsed by or sponsored by Process Street.

At a glance

The Process Street pricing page shows its features as a checkmark grid, and the text did not reliably show which plan each item belongs to. Confirm per-plan availability with Process Street.

Key differences

Pricing transparency

When we checked, Process Street's pricing page published no prices. Every plan shows "Contact sales" [1]. Its FAQ says the Startup plan is "a significantly reduced price on the Pro Plan for businesses that have less than 15 employees and under $2 million in revenue" [1]. Runbook publishes its prices: CHF 19/month for up to 10 users, or CHF 49/month for up to 30 users. Both are flat per organisation. Because Process Street's prices are not published, we cannot do a like-for-like cost calculation. Ask Process Street for a quote for your team size.

Depth of workflow features

Process Street's plan comparison lists conditional logic, approvals, form fields and rich media, enforced task order, dynamic due dates, role assignments and automations [1]. Runbook has none of conditional logic, form fields (text inputs, file uploads) or approval steps. A Runbook template is a list of sections and items, each required or optional. Items can have notes and simple variables like {{version}}. If your process branches or needs to collect structured data, Process Street does more.

Completion rules and audit trail

Runbook has one strict rule: a run can only be completed when all required items are checked. Every check is written to an append-only event log for that run (who checked what, and when), which you can export as CSV. You can also export all your data as JSON. For teams whose main need is "prove the checklist was done", this narrow scope may be all they need.

CI/CD and API

Runbook has a REST API with bearer tokens (POST /api/v1/runs, GET /api/v1/runs/{id}, GET /api/v1/templates) and a GitHub Action, "Runbook: start checklist run". The Action can wait until the run is completed, so it can gate a deploy. There are also GitLab CI and Forgejo examples. Process Street lists a public API (50 calls/month on Startup) and several automation connectors [1].

Ecosystem, compliance and enterprise needs

Process Street lists SOC 2 Type 2, HIPAA, SAML SSO, SCIM, Active Directory integration, mobile apps and connectors to Zapier, Power Automate, Tray.io and Make [1]. Runbook has no SSO, no mobile app, no integrations marketplace or Zapier connector, and no SOC 2 report of its own. Runbook only has two roles, owner and member.

When to choose Process Street instead

• Your workflows need conditional logic, approvals or form fields, for example collecting data or files during a run.
• You need SSO/SCIM, SOC 2 Type 2 or HIPAA on the vendor side [1].
• You want native mobile apps or connectors to Zapier, Power Automate, Tray.io or Make [1].
• You want AI features or document management in the same tool [1].
• You need more than 30 users, or more granular roles than owner/member.

When Runbook fits better

• Your process is a plain recurring checklist: release, month-end close, server patching, office opening, onboarding steps. You mainly need it done every time, with a record of who did what.
• You want published, flat pricing that doesn't grow with each seat: CHF 19/month covers up to 10 users.
• You want to gate a deploy on a checklist from GitHub Actions, GitLab CI or Forgejo.
• You prefer an EU-hosted, Swiss-run tool with passwordless email sign-in and no trackers.
• You want to start on a free plan without talking to sales.

FAQ

Does Process Street publish its prices?

Not when we checked on 2026-11-04. The official pricing page lists Startup, Pro and Enterprise, and each shows "Contact sales". The FAQ mentions a reduced-price Startup plan for businesses with fewer than 15 employees and under $2 million in revenue, and says cards are charged in USD.

Does Runbook support conditional logic like Process Street?

No. Runbook templates have sections, required and optional items, notes and simple variables, but no branching, form fields or approval steps. Process Street lists conditional logic, approvals and form fields in its plan comparison.

Is there a free trial for either tool?

Process Street says all new accounts start with a 14-day trial of its Pro plan, with no credit card required. Runbook's Team plan has a 14-day free trial with no card, and Runbook also has a permanent Free plan for one user.

Can Runbook block a deployment until a checklist is done?

Yes. The "Runbook: start checklist run" GitHub Action starts a run and can wait until it is completed. Runbook also provides GitLab CI and Forgejo examples that use the REST API.

Is Runbook SOC 2 certified?

No. Runbook is new and does not have a SOC 2 report of its own. It is hosted in the EU and uses passwordless email sign-in. Process Street lists SOC 2 Type 2 on its pricing page.

Sources

1. Process Street pricing page: https://www.process.st/pricing/ (checked 2026-11-04)
2. Runbook: https://runbook.metastic.ch (Runbook's own plans and features, as of 2026-11-04)