for · regions & collaborations

One view across all your municipalities. One language for the region.

Multi-tenant, role-based, screenable per municipality — no trade-off between overview and privacy.

section b

What regions and umbrellas struggle with

Regions and collaborative networks sit structurally in the middle. Municipalities each work in their own rhythm and systems. The region must monitor policy directions, bundle signals, and find a shared language — without violating member autonomy.

The consequence: umbrellas often suffer from paperwork. Reports arrive slowly, in incompatible formats, and miss the moment when governance would have been useful.

section c

What Murmur does here

In its form for urban dynamics & stakeholders — the platform we call UrbanStakes. One engine, focused on the regional challenge.

01

Multi-tenant from the foundation

Each participating municipality has its own tenant — own data, own access rights, own taxonomy. The region sees what the individual municipalities choose to share; no more, no less.

02

Cross-municipal patterns

What's happening in municipality A, you see against B and C. Signal comparison across the region delivers insights no single municipality can see alone. Privacy-aware: aggregates with k-anonymity where sensitive.

03

Shared taxonomy, flexible application

The region develops a taxonomy (themes, actors, policy lines) together with municipalities. Each municipality can add its own nuances. Changes propagate via governance, not via broadcast.

04

Report automation

Quarterly reports to the board: automatically generated from curated signals. No more cutting and pasting from disparate systems.

section d

Concrete use cases

Use case 1 — Public health region

A signal about new risk groups (for example vulnerable target populations) must land with the right municipal executor. UrbanStakes links the signal to the thematic taxonomy, identifies the relevant tenant, and delivers a briefing for the regional director.

Use case 2 — Safety region

Media and social chatter around an incident in one municipality; comparable earlier incidents in neighbouring municipalities; involved stakeholders region-wide. UrbanStakes delivers an event dossier for the regional coordinator.

Use case 3 — Welfare umbrella / RES region

Policy motions on the same theme in multiple councils. UrbanStakes detects the convergence, bundles the differences, and delivers a briefing for regional council consultation.

section e

Architecture highlights

For IT and information managers who know what multi-tenant means.

  • Multi-tenant

    Tenant isolation per municipality, cross-tenant only via explicit opt-in aggregates.

  • Role-based

    Director, policymaker, analyst — each with their own access level.

  • Shielding

    Municipalities can screen specific files or themes from regional view.

  • Audit logs

    Per tenant, own retention period per contract.

Shielding in practice

How does it work concretely?

Example 1 — A municipality can exclude specific files (for example youth-care casework) from regional view. The region then sees only the existence of the file with a count, not the content.

Example 2 — A theme that is politically sensitive (e.g. enforcement priorities) can stay within the tenant; only after explicit opt-in by the municipality does it enter the regional view.

Example 3 — A complaint file with personal data (L2) is never shared, even on aggregate level, when k-anonymity cannot be guaranteed. The region sees no signal, unless the municipality chooses manual anonymisation.

Full detail: see Trust Center.

section f

Discuss the regional edition

We happily work with regions and umbrellas that want to shape a first multi-tenant deployment.

Discuss the regional edition