Coordinate the response, on one map.
Weidenmap puts your response on one live, shared map - needs, incidents, activities, and resources, with the structured detail your sector works in. Built for the NGOs and aid agencies coordinating in the field.
Free for NGOs in early access. One live, shared map - points, lines, and zones.
Built with humanitarian teams - for the people coordinating disaster and crisis response.
- NGOs
- Aid agencies
- Coordination bodies
A guided tour of Weidenmap
Watch how a response team maps needs, incidents, and activities on one live, shared map - with the structured detail their sector works in.
Everything a response needs, on one map
Weidenmap gives aid teams the things coordination actually takes - the full picture, structure your sector defines, a live 4W across agencies, and protection by design.
Map the whole picture
Needs, incidents, distributions, and affected areas - as points, lines, and polygons. Map what’s happening on the ground, not just dots on a map.
Custom fields for every sector
Start from a one-click humanitarian preset or build your own - your org defines the fields it needs (select, text, number, date, yes/no), with controls like a needs-severity slider. Attach photos and documents to any record.
Coordinate across agencies
Run a shared response that multiple agencies join on one live map - the 4W of who’s doing what, where, and when. Each org controls exactly what it contributes, every feature tagged by agency.
Protect the people in your data
Per-feature visibility - private, group, org, response, public - plus Protected-location fuzzing, per-field sensitivity tiers, an audit log, and GDPR tooling. Do-no-harm, on by design.
Built for the realities of response
Each capability is shipping today, and built for the field - structured, live, and shareable at exactly the right level.
Sector-ready in one click
Spin up an org with a humanitarian setup already in place - or start blank and build your own. The preset seeds standard, roll-up-friendly fields so your data lines up across agencies from day one.
- Clusters: WASH, Shelter/NFI, Health, Protection, Food Security, Nutrition, Logistics, CCCM, Education, Early Recovery, ETC
- Standard fields for activity status, needs severity, beneficiary counts, P-codes, and assessment dates
- Seeded as standard fields so data rolls up across agencies - or start from a blank org
Capture it the way your sector works
Every feature has a title and description plus the custom fields your org defines. Admins build the fields once; the capture form and detail panel render them with purpose-built controls - so WASH, Shelter, Health, or Protection each record what they actually need.
- Custom fields: select, multi-select, text, number, date, yes/no
- Purpose-built controls: sector-coded pickers, a needs-severity scale slider, an activity-status stepper
- Photos, documents, and a triaged comment log on any feature
Turn a field photo into structured intel
Opt in, and an attached photo becomes structured data: a concise factual summary, one humanitarian category, and counts of what’s in frame - like “houses on fire 5/20 (25%)”. Results appear live on the feature, beside the photo.
- Factual summary, one humanitarian category, and quantified counts
- Categories like flood, fire, structural damage, displacement camp, infrastructure
- Off by default - admin opt-in per org; images are sent to Anthropic’s Claude only when enabled
One response, many agencies, one map
Spin up a response - a specific disaster - that multiple agencies join. Everyone works one shared map, and each org controls exactly what it contributes by marking features response-visible. The cross-org picture is the live 4W: who’s doing what, where, and when.
- A shared map per response, joined by multiple agencies
- Each org decides exactly what it contributes - nothing is shared by default
- Every contribution tagged by agency; each org’s own location-protection rules travel with its data
One map, always current
Weidenmap is live by default. When a teammate logs a need or resolves an incident, everyone sees it the moment it happens - over WebSockets, with no refresh and no emailed exports.
- Features and comments stream in live
- Updates across the whole team at once
- No stale spreadsheets or screenshots in chat
Every thread becomes a coordination log
Comment on any feature, right next to the place it’s about. Tag each note as an update, need, question, or decision - and mark “need” notes resolved - so a thread turns into a live, filterable coordination log instead of flat chatter. Comments show the author and update live for everyone on the feature.
- Triage each note: update, need, question, or decision
- “Need” notes can be marked resolved - the thread stays a live to-do, not flat chatter
- Internal by default - a note reaches a share link only when a member marks it shared
Share at exactly the right level
Move a feature from private to group to org to response to public as the situation unfolds. Opt-in public maps fuzz sensitive locations, and per-feature share links are login-less and revocable - and photos shared over a link are scrubbed of EXIF/GPS metadata on download.
- Private → group → org → response → public, per feature
- Public maps with location fuzzing for sensitive data
- Revocable, login-less share links; shared photos scrubbed of EXIF/GPS on download
Every agency its own tenant
One account can belong to many organizations and switch between them in a click. Each agency is its own tenant on its own subdomain, with its own members, roles, logo, and accent color.
- Per-org tenant on its own subdomain (acme.weidenmap.com)
- Roles - Admin, Editor, Viewer - plus group membership
- Per-org branding: logo and accent color
Built for sensitive ground truth
Response data is data about vulnerable people. Mark a feature Protected to coarsen its location for everyone outside the owning org, tier each field’s sensitivity so PII stays in-org or among response partners only, and rely on an audit log, GDPR export and erasure, and strict per-tenant access checks. Do-no-harm, on by design.
- Protected features: location coarsened by grid-snapping outside the owning org
- Per-field sensitivity tiers keep beneficiary PII off the public web
- Audit log, GDPR export & erasure, strict per-tenant isolation
Built for humanitarian response
From the first hours of a disaster to ongoing operations. Pick a scenario to see how aid teams put Weidenmap to work.
Disaster response coordination
Put the whole response on one live map - incidents, needs, and the resources moving to meet them.
Field teams log what they find as it happens; coordinators see one current picture instead of a stack of spreadsheets. Everyone works the same map, and each feature is shared at exactly the level the situation calls for.
Needs assessments
Run assessments with the fields your sector uses, and map results where they were collected.
Build a capture form from custom fields - severity, beneficiary counts, sector, dates - and record each assessment as a geolocated feature with photos attached. The map becomes your assessment dataset, exportable and discussable in place.
Distribution & activity tracking
Track who did what, where, and when - distributions, activities, and the areas they covered.
Map distribution sites and activity zones as structured features, update their status live, and keep a clear record of your team’s footprint across the operation - the 4W picture for your organization.
The same platform also fits adjacent field-data work - civic reporting and field research - but humanitarian response is who we build for.
Do no harm, built into the platform
Weidenmap holds data about vulnerable people, so protection is part of the product, not a footnote. Here is exactly how it works - and, just as importantly, where the limits still are.
Strict multi-tenancy
Each agency is its own tenant on its own subdomain. Every request is checked against a verified membership - no cross-tenant access except the explicit, opt-in shared response.
Visibility enforced server-side
Five levels - private, group, org, response, public - checked on every read. Public and cross-org surfaces get sanitized projections with internal ids stripped, never the raw record.
Do-no-harm location controls
Mark a feature Protected and its location is coarsened for everyone outside the owning org. Per-field sensitivity tiers keep PII like beneficiary details in-org, or among response partners only.
Passwordless auth
Magic-link sign-in - no passwords to leak - with HMAC-signed, HttpOnly session cookies and edge rate-limiting on sign-in.
Compliance foundations
A full audit log of security-relevant actions, plus GDPR self-service data export and account deletion - authored content is anonymized, not orphaned.
AI is opt-in
Image analysis is off by default. An image is sent to Anthropic’s Claude only when an admin has enabled it and an editor explicitly runs it.
We also keep a candid list of where the limits still are - because for this work, naming them builds more trust than hiding them.
Fast everywhere, protected by design
Weidenmap runs entirely on Cloudflare’s edge - Workers, D1, R2, and Durable Objects. It’s quick wherever your team works, scales down to zero between operations, and keeps response data protected by default.
Fast everywhere
Served from the edge, close to teams working in the field.
Scales to zero
No idle servers to pay for between responses.
Per-tenant isolation
Strict access checks keep every agency’s data its own.
Do-no-harm by default
Protected-location fuzzing, per-field sensitivity tiers, audit log, and GDPR tooling.
Free for NGOs. Funded by everyone else.
Humanitarian and nonprofit teams use the full product free while we’re in early access. Commercial and large-agency plans fund the platform - so it stays free for the teams who need it.
Questions, answered
What aid teams ask before they trust us with sensitive response data.
Still curious? Ask us anything .
Put your whole response on one map.
See how aid teams coordinate needs, activities, and resources on one live, shared map - structured, protected, and shared at exactly the right level. Free for NGOs in early access.