Let's imagine that there are two teams at the same bank that are building process automations this quarter. The first is Customer Onboarding which is standing up account opening and document checks. The other is Fraud & Financial Crime who is building something to screen every application before it reaches underwriting.
We have two teams with two mandates. The center of excellence team wants visibility into: which connectors are approved, who has access to deploy, and whether new processes are following security policy. And the delivery teams want autonomy to build without waiting for approvals, and to have insight into what other teams have already built so they aren't reinventing it.
Both of those wants are legitimate. Without a platform built for both, they live in separate places, and that's the actual problem.
However, neither group is fully aware of what the other is doing, so each one risks building its own connector to the same core banking system, solving the same "what happens when the agent isn't sure" problem from scratch. When a director asks how automation is performing across the bank, nobody can answer with one voice; there are departmental answers, in departmental tools, in departmental heads.
This isn't a hypothetical situation. It happens in nearly every organization that succeeds at automation one team at a time. Organizations are building at scale. This might be agentic orchestration, traditional automation, or both. And if you are building at scale, you are going to hit a wall and fast. The moment you have multiple teams building, you need unified visibility and control. The moment you need unified control, you realize your current tools weren't designed for it.
And that is why Camunda built the Camunda Hub.
"Big wins come from reducing organizational friction, not from harnessing technology." — Forrester, Best Practices For Automation Centers Of Excellence (COEs), Craig Le Clair et al., February 2, 2026
Three teams rebuilding the same connector in isolation, versus one organization drawing shared building blocks from a single Camunda Hub catalog.
You don't have to give up governance to gain speed
This is where Camunda Hub actually starts: where agentic orchestration scales with trust. Not by asking the CoE to trade governance for speed, or asking delivery teams to trade speed for governance, but by giving both the same platform, from two different sides.
The organizational side, where the CoE manages from:
- Create team workspaces, manage access, and assign them to deployment environments in minutes
- Maintain a private catalog of approved building blocks and shareable assets
- Monitor cluster health and see what's actually running, across every team, in one view
- Track whether the processes being shipped are delivering the business value they promised
The workspace side, where delivery teams work from:
- Discover, share, and reuse approved assets, connectors, decision tables, templates, so teams build on each other’s work instead of rebuilding it
- Collaborate on process design inside a governed workspace
- Deploy with confidence that the work already follows organizational standards
There is no separate tool for CoE governance and no fragmented asset discovery. There is one platform where a delivery team's design decisions and the CoE's policy are visible to each other, in the same place, at the same time.
Structurally, that means three layers. At the top sits your Organization, the container for governance, environments, and shared catalogs across the whole company. Underneath it, each team gets its own Workspace, a domain-specific space like "Fraud & Financial Crime" or "Customer Onboarding" with its own members, roles, and assigned environments. Inside a workspace, teams build Projects: the process models, decision tables, RPA scripts, forms, and connectors that make automation run, Git-synced and versioned as a single deployable unit.
One structure, three layers: your organization, your teams, and the work they ship.
None of this means starting from zero if you're already on Camunda. Existing Web Modeler projects and process applications migrate into this structure automatically.
If you're already running Camunda, existing Web Modeler projects and process applications migrate into this structure automatically — no manual rebuild required.
The Fraud & Financial Crime team and the Customer Onboarding team each get their own workspace this way. Different members, different roles, different environments if they need them, backed by physical tenants for real data separation, not just logical isolation on shared storage. All of it sitting inside the same organization, subject to the same governance, drawing from the same catalog of approved building blocks. Nobody's stepping on anybody else's work, and nobody's rebuilding what already exists somewhere else. And the CoE isn't taking that on faith, either: the same organization view that shows every workspace also shows every environment, so a governance question gets answered by looking, not by asking around.
Camunda Hub's workspaces grid: six teams across the bank, each with its own members, projects, and environments, all visible from one organization view.
Stop building the same thing twice
Every Organization has one Catalog. This is a shared, governed repository of reusable assets, approved once, discoverable by every other team from then on. In the bank's case, that catalog already holds the pieces that make the fraud and onboarding story work end to end, a KYC identity check, a sanctions and watchlist screen, a fraud risk advisor, a credit bureau pull, a lending policy check. Build it once. Every team that needs the same integration finds it and uses it, instead of rebuilding it from a wiki page or someone's memory of how it worked last time.
Camunda Hub's organization catalog: governed identity, fraud, and lending assets, published once and reused across every team that needs them.
That's the crown, and it deserves more room than one section can give it: how assets get approved, how their lifecycle gets managed centrally, how usage and adoption get monitored across the org. That's the next post in this series.
Available with Camunda 8.10
Hub is built for two kinds of organizations. If you're already running multiple teams, multiple clusters, multiple workspaces, and feeling the fragmentation right now, Hub is where you consolidate it. If you're just getting started, Hub is your foundation from day one, so you never have to reorganize later because you started structured, and you never have to hire someone whose full-time job is stitching your tools together.
Camunda's 8.10 release webinar lands November 4, 2026. Be sure to put this on your calendar.