Free · Multi-tenant · Your own workspace
Visual SOPs for the way your org actually works
Map your organization, embed SOPs where they're owned, and ship
audit-ready ops. Free self-serve workspace, verified email, 2FA on
new devices.
Create workspace
·
Sign in
Three steps from blank canvas to running ops
-
Map your org. Drag, drop, and connect teams on an
interactive canvas. Departments, teams, roles — reparent anything,
auto-layout with one click.
-
Attach SOPs. Every node owns its own kanban board.
Phases become columns, steps become cards. Drag between phases.
Version every change.
-
Ship audit-ready ops. RBAC tied to the tree, full
audit log, 2FA on new devices, per-workspace tenant isolation.
Nothing leaks between customers.
Record a browser workflow into a draft SOP
The SOPFlow Chrome recorder captures clicks, form inputs, page
navigations, and screenshots between an explicit Start and Stop,
then turns the recording into an editable Standard Operating
Procedure draft inside your workspace. Passwords and credit-card
fields are masked at the source — they never leave the browser
in plaintext. Edit the draft inline, then import the steps into
any SOP's kanban phase.
Read the launch post{" "}
for setup, privacy guarantees, and a walkthrough of the AI
two-pass pipeline.
Ops your team can actually follow
Not another doc wiki. SOPFlow puts standard procedures where they
belong: attached to the team that owns them.
-
Org chart with embedded SOPs. Drag-to-reparent
nodes on an interactive canvas. Each node carries its own
kanban-style standard operating procedures.
-
Version-controlled procedures. Copy-on-write
versioning, draft → review → approved → active state machine,
audit trail on every change.
-
Permissions tied to the tree. Users are anchored
to a node. They can edit their own subtree, never above. Admins
approve every new account.
Kanban SOPs
Procedures as cards, not paragraphs
Phases become columns. Steps become cards. Drag steps between
phases. Assign roles. Track decision points. Every change is
versioned and auditable.
- Drag-and-drop reordering with optimistic updates
- Step types: action, decision, approval, subprocess, reference
- Markdown descriptions with full step editor
- File attachments on every step (PDF, images, video)
Compliance-ready
See what's drifting before audit time
Track every status transition, every approval, every edit. SOPs
flag themselves when overdue for review. Full-text search across
procedures and steps.
- Active vs draft vs retired counts at a glance
- "Due for review" surfaced from configurable review periods
- tsvector full-text search across SOPs and steps
Built for teams that get audited
-
Role-based access. Users anchored to a node; can
edit their subtree, never above. Admins manage their own workspace.
-
Full audit log. Every SOP transition, node move,
user approval, and role change recorded with actor and timestamp.
-
Email verify and 2FA. Verified email required to
activate. Six-digit email code on every new device; 30-day trusted
sessions.
-
Tenant isolation. Each workspace lives in its own
organization_id namespace. Zero cross-tenant data leakage, enforced
at the query layer.
Start free. Upgrade when you outgrow it.
Every plan includes the full SOPFlow workspace — org charts, kanban
SOPs, version history, multi-tenant isolation, and email-verified
accounts. Paid tiers unlock higher limits, larger uploads, and
premium support.
| Plan |
Price |
Users |
Charts |
Nodes |
SOPs |
Upload / file |
Total storage |
| Free |
$0 / mo |
3 |
1 |
25 |
5 |
10 MB |
100 MB |
| Starter |
$29 / mo |
10 |
3 |
150 |
25 |
25 MB |
2 GB |
| Pro (most popular) |
$99 / mo |
50 |
15 |
1,000 |
250 |
100 MB |
20 GB |
| Enterprise |
$499 / mo |
Unlimited |
Unlimited |
Unlimited |
Unlimited |
1 GB |
200 GB |
Questions about a custom plan? Email
admin@sopflow.io.
SOP management for every industry
SOPFlow works wherever documented, repeatable processes matter most.
-
Manufacturing SOP software. Map your production
floor as an org chart, attach SOPs to each cell or shift team,
version every process change, and stay audit-ready for ISO 9001
document control requirements.
-
Healthcare SOP management. Document clinical
and administrative procedures by department. Role-based access
ensures only authorized staff can approve changes. Full audit log
on every edit.
-
Restaurant SOP software. Standardize kitchen,
front-of-house, and opening/closing procedures across locations.
Each location is a node; each station owns its SOPs.
-
Construction SOP management. Attach safety
procedures, site checklists, and subcontractor SOPs to the project
org structure. Version control catches every change before it
reaches the crew.
-
Logistics and warehouse procedure management.
Document fulfillment, receiving, and shipping procedures by
warehouse zone. Kanban phases match your actual workflow stages.
SOPFlow vs. other SOP tools
Unlike Trainual, SweetProcess, Process Street, or Scribe, SOPFlow
is the only SOP creation tool built around your org chart. Here's
how it stacks up:
-
SOPFlow vs. Trainual. Trainual uses a flat
content library. SOPFlow attaches SOPs to org nodes — permissions
follow the hierarchy, not a folder structure. Ideal for teams
where different departments own different procedures.
-
SOPFlow vs. Process Street. Process Street runs
checklists. SOPFlow manages the source-of-truth procedures behind
those checklists — with version control, approval workflows, and
an audit log built in.
-
SOPFlow vs. Notion for SOPs. Notion is a
general-purpose wiki with no org structure, no state machine, and
no compliance audit log. SOPFlow is purpose-built for documented
operations.
-
SOPFlow vs. Google Docs for SOPs. Google Docs
has no version approval workflow, no org permissions, and no
audit trail. SOPFlow's draft → review → approved → active state
machine makes compliance straightforward.
Learn more: SOPFlow vs. Trainual ·
SOPFlow vs. Process Street ·
SOPFlow vs. SweetProcess ·
SOPFlow vs. Notion
What is an SOP and why does your team need one?
A standard operating procedure (SOP) is a
documented, step-by-step process that employees follow to complete
a routine task consistently. Well-written SOPs reduce errors, speed
onboarding, and make your operations auditable — essential for
ISO 9001 compliance, healthcare accreditation, or any regulatory
review.
How to create a standard operating procedure
- Identify the process and who owns it in your org structure.
- Break the process into phases (preparation, execution, review).
- Write each step as a discrete action with a clear outcome.
- Assign the SOP to the team node that owns it.
- Send it through a review → approval cycle before making it active.
- Set a review period so the SOP surfaces automatically when it's overdue.
SOP version control best practices
Every SOP should move through a state machine: draft → review →
approved → active. A copy-on-write versioning model means old
versions are preserved for audit purposes while teams work on
updates. SOPFlow handles this automatically.
How to organize SOPs by department
The most effective way to organize standard operating procedures is
by the team that owns them — not by topic or alphabetical order.
When SOPs live on org chart nodes, the right people find them
immediately, and permissions follow the hierarchy.
Frequently asked
- Who is SOPFlow for?
-
Ops, engineering, compliance, and people teams that need runbooks
and procedures to live where the work actually happens — attached
to the teams and roles that own them, not buried in a wiki. If
your org chart has more than a dozen people, SOPFlow probably
helps.
- Is my data isolated from other workspaces?
-
Yes. Each workspace is a fully isolated tenant with its own
organization_id. Every database query — reads and writes — is
scoped to the caller's organization at the query layer. No
cross-tenant data can be returned, even if a bug in application
code tried to leak it.
- Who can see what inside my workspace?
-
Role-based access, tied to the tree. Every user is anchored to an
org node and can edit their own subtree but not above it. Admins
can manage the whole workspace. Full audit log on every change.
- Does SOPFlow cost anything?
-
SOPFlow is free during launch — create a workspace, invite your
team, use every feature. We'll introduce paid plans later, and
anyone already on the platform will get a long grandfather period
with advance notice.
- Can I invite my team?
-
Yes. After you create your workspace, head to Admin → Users to
invite teammates. You can set their role (admin / editor /
viewer) and anchor them to a specific org node so their
permissions match their actual scope.
- Can I self-host SOPFlow?
-
Not yet — self-host is on the roadmap. The API and DB schema are
designed to run anywhere that supports Postgres + Node, and we'll
publish a Docker Compose stack once the core feature set
stabilizes.
Create your workspace
Sign up free. Your account is isolated — nobody else can see your
charts, SOPs, or team members. Verify your email, invite teammates,
and you're mapping procedures in minutes.
- Instant private workspace (no approval wait)
- Email-verified accounts with 2FA on new devices
- Per-user RBAC scoped to your team subtree
- Invite unlimited teammates
Create workspace
·
See pricing