Visual Map builder
Any structured Journey.
Shown as a map.
Atlas is a visual map builder for BPM programs. Build curriculum paths, release roadmaps, program dependency maps, and capability journeys — anything with stages and connections — on a clean, interactive canvas using a subway map metaphor that everyone immediately understands.
One-time purchase. Runs locally on your machine or on a server behind your firewall. Your maps, your files. No subscription, no cloud, no IT ticket.
The problem
Complex Journeys deserve
Better than a slide deck
PowerPoint maps nobody can navigate
You build a beautiful slide showing the learning path or program roadmap. It’s static, it’s a PNG, and when things change you start from scratch. Nobody knows which version is current.
Tools that require a design degree
Miro, Visio, and Lucidchart can technically produce a subway-style map. But the time it takes to get something that looks right — and stays editable — is a project in itself.
No shared language for “what comes next”
When you’re planning a BPM capability program, a release roadmap, or a training curriculum, everyone has a different mental model. A visual map gives the team a shared reference — but only if you can build and update it easily.
Maps that don’t show status
A static diagram shows where things are planned to go. It can’t show what’s live, what’s coming, and what’s been retired. Atlas builds that directly into the map.
“Whether I’m mapping a capability curriculum, a program of process improvements, or showing how releases depend on each other — the structure is always the same: nodes connected by paths, with some things active, some planned, some overlapping. Atlas makes that visual in minutes, not hours.”
Roland Woldt
Host, What’s Your Baseline? – EA/BPM Practitioner
*one map. every audience immediately gets it.*
What you can map
One Tool.
Any structured journey.
The subway map metaphor works for anything with stages, dependencies, and multiple
parallel tracks. Here’s what BPM practitioners actually use Atlas for.
learning and development
Capability Curricula
Map your BPM capability program as a learning journey. Each path is a skill track — Foundations, Modelling, Governance, Advanced Topics. Each node is a course or milestone. Transfers show where tracks connect.
“New analysts follow the Foundations track first. When they reach the Swimlanes node, they can transfer to the Governance track or continue to Sub-processes.”
Program management
Release roadmaps
Show how releases, features, or workstreams depend on each other across time. Planning nodes appear dashed. Active nodes are solid. Retired capabilities show as decommissioned — still visible, clearly marked as past.
“Q3 releases depend on the API platform node being complete. The map makes that dependency visible at a glance — no spreadsheet required.”
Enterprise architecture
Implementation Sequence
Map the sequence of a large program — what must happen before what, which workstreams run in parallel, where the decision points and handovers are. Zones group related nodes without cluttering the map.
“The process discovery zone must complete before the modeling zone begins. The governance zone runs in parallel with both. Everyone can see this on one map.”
Capability Maturity
Maturity Progression
Show the journey from initial to optimized across multiple capability dimensions. Each path is a capability area. Each node is a maturity level. The map shows an organization where they are and where they’re going.
“We’re at level 2 on Process Documentation and level 1 on Governance. The map shows the client exactly what the next two years look like.”
Training progress
Onboarding journeys
Design the new hire journey as a structured map — Day 1, Week 1, Month 1, Month 3. Multiple paths for different roles that share some nodes and diverge at others. Every new hire sees the same visual.
“All roles share the first three nodes. After that, analysts go down one path and project managers go down another. It’s immediately clear.”
Consultants
Client Deliverables
Build a visual program map as a deliverable for a client engagement. Export it, print it, present it. Brand the map with the client’s logo and colors. Hand it over at the end of the project as something they can keep using.
“The Atlas map became the one artifact every stakeholder referenced throughout the program. It replaced three different PowerPoints.”
How it works
Three building blocks.
Infinite combinations.
Every Atlas map is built from the same three primitives. Simple to understand, powerful in combination..
Nodes
A node is a stop on the journey — a course, a milestone, a release, a capability level. Regular nodes are circles. Hub nodes are pills for major interchange points. Every node has a label, a status, and an optional link.
Paths
A path connects nodes in a sequence — a skill track, a workstream, a release lane. Each path has its own color and abbreviation pill. Transfer paths (dotted) show connections between tracks where learners or work can switch.
Zones
A zone is a labeled region that groups related nodes — a phase, a domain, a time period, an audience level. Zones don’t affect the paths or nodes inside them; they just make the map easier to read at a glance
Node status
Every node has a status: Active (solid), Planning (dashed, with optional activation date), or Decommissioned (faded, with optional retirement date). The map shows the full picture — past, present, and future.
Features
Built for anyone who needs to show
a complex journey clearly.
interactive canvas
Pan and zoom across your map. Drag nodes freely to lay out your journey exactly as you want it. The grid keeps things aligned without forcing rigid structure. Everything auto-saves as you work.
Paths with full control
Each path gets a name, a color from the WYB palette, and an abbreviation pill that appears at both ends of the path on the canvas. Transfer paths render as dotted lines — the visual shorthand for “you can switch tracks here.”
Node properties panel
Click any node to open its properties panel. Set the label, abbreviation, status, activation or retirement date, and an optional link. Control exactly where the label appears relative to the node — nine positions plus custom angle.
Zones for grouping
Draw a labeled zone around any group of nodes — a phase, a level, a domain, a time period. Zones resize automatically to fit their members, and their labels can be positioned on any edge. Add as many zones as the map needs.
Search across the map
The search bar in the topbar finds nodes and paths as you type, across all projects. Click a result to jump directly to it on the canvas. Useful when a map grows large enough that scrolling to find something takes too long.
Multi-project support
Each Atlas instance supports multiple separate projects — one map per project, each with its own nodes, paths, and zones. Switch between maps using the project selector. Each map is stored as its own file, independently portable.
Node statuses
The map shows where things are.
Not just where they’re going.
Most visual maps only show the plan. Atlas maps show the full picture — what’s
live, what’s coming, and what’s been retired — all on the same canvas, without
cluttering it.
Active
Live, in-use, available. The node renders as a solid circle with full color. This is the default state for anything currently operational.
Renders as a solid circle
Planning
Not yet live but on the roadmap. Renders with a dashed border so it’s clearly distinguishable from active nodes. Set an optional activation date to make the timeline explicit.
Renders dashed with a plus — optional activation date
Decommissioned
Retired or replaced. Still visible on the map so the history is preserved, but rendered faded so it doesn’t compete with active content. Set a retirement date — the fading kicks in once that date passes.
Renders dashed with a minus — optional retirement date triggers timing
Who it’s for
Built for anyone who needs to show
A complex journey clearly.
BPM / Process Managers
L&D / Training Teams
Consultants & Architects
Why local first
Your maps love
Where you decide.
01
No subscription, no per-seat fees
Miro charges per member per month. Lucidchart charges per user. Atlas is $99 once. Use it across your whole team on a shared server, forever.
02
No vendor dependency for your maps
Every map is a JSON file on your disk. Open it, move it, archive it, share it. If you stop using Atlas tomorrow, your maps are still there — readable and portable.
03
Git version history built in
Connect a Git repository and Atlas auto-commits every map change. You get a full history of every edit — useful when a stakeholder asks “what did the Q2 roadmap look like before we changed it?”
04
Team access when you want it
Run Atlas on a shared server and your whole team edits maps through their browser. Three-tier access control means some people can view, some can edit, and only you can touch the admin settings.
Compared to Miro or Lucidchart
Miro’s team plan starts at $8 per member per month — that’s $96 per person per year, forever, for maps that live on Miro’s servers and require an internet connection to view.
Atlas is $99 once. It runs on your machine or your server. The maps are plain JSON files. There’s no monthly invoice, no vendor to negotiate with, and no data in someone else’s cloud.
It doesn’t have AI suggestions or 1,000 templates. It has exactly the features a BPM practitioner needs to build clear, maintainable visual maps — and nothing that gets in the way of doing that quickly.
Pricing
One Price.
No surprises.
Buy Atlas on its own, or as part of a bundle with the other BPM OS tools. Every option
is a one-time purchase — no subscription, no per-seat fees, no renewal.
Atlas
Just the visual map builder
$99
One-Time Purchase
most popular
Practitioner Bundle
Atlas + Groundwork + Playbook
$199
One-Time Purchase
Save $98 vs. buying separately
Full BPM OS Stack
The complete stack – all apps
$299
One-Time Purchase
Save $225 – every current and future app in 2026 included
Using Atlas across multiple client environments? A Consultant License is available. Get in touch.
Common Questions
Things people ask
Before they buy.
Is this only for curriculum maps, or can I use it for other things?
Atlas works for any structured journey that benefits from a visual map — curriculum paths, release roadmaps, program implementation sequences, capability maturity progressions, onboarding journeys. The subway metaphor works whenever you have parallel tracks with stops and connection points between them.
How is this different from Miro or Lucidchart?
Miro and Lucidchart are general-purpose visual tools — you can build anything, but building a structured map requires significant setup time and expertise. Atlas is purpose-built for the BPM practitioner use case: structured journeys, node statuses, transfer paths, and zones are all native features. It’s also a one-time purchase that runs locally, versus a per-seat subscription storing your maps in someone else’s cloud.
Can I share a map with someone who doesn’t have Atlas installed?
If you run Atlas on a shared server, anyone with the URL and the right password can view or edit the map through their browser — no install required. For sharing with people outside your network, you can export the map as a screenshot or print it to PDF from the browser.
Can learners or stakeholders see the map without editing it?
Yes. Set up a Viewer password in the admin panel and share that with your audience. Viewers see the full interactive map — they can pan, zoom, and search — but can’t add, move, or edit anything. Editors can modify the map. Only Admins can touch the settings.
How many maps can I have in one installation?
Unlimited. Each project is a separate map. You can create as many projects as you need — one per client engagement, one per capability domain, one per program. Switch between them using the project selector in the sidebar.
Do I need technical knowledge to set it up?
No. Setup is a double-click on a script — one for Mac, one for Windows, one for Linux. If Node.js isn’t installed, the script installs it. Once it’s running, you open your browser and start building your first map. There’s no command line involved in day-to-day use.
Can I brand it with my organization’s or client’s logo?
Yes. The admin panel has a branding section where you upload a logo, set the topbar color, and adjust the accent colors. Useful for running it inside a client environment as a consultant, or matching your organization’s brand for internal programs.
How does Atlas fit with the other BPM OS tools?
Atlas maps the journey. Playbook documents the standards and knowledge behind each stop on that journey. Course Flow manages the training projects that build the capability. Cadence keeps your week organized while you run all of it. Outline is used for structuring content, and Groundwork is your brainstorming and sorting tool. They run on the same platform launcher and complement each other without overlapping.
Ready to map your journey?
Stop explaining in slides.
Start showing in Atlas.
Every complex program has a visual story. A curriculum, a roadmap, a capability journey — Atlas gives you a way to tell it clearly, keep it current, and make it something people actually use.
Part of the BPM OS from What’s Your Baseline?