Humanitarian & Global Health
Bring disaster response, outbreak response, immunization, WASH and field operations into a shared geographic context.
Geospatial operational intelligence
See what’s changing around the places that matter to you.
Combine global risk signals with your own locations and operational data. Understand exposure, changing conditions, and where attention may be needed next.
Your locations. The surrounding context.
A clearer basis for the next decision.
Operational area / illustrative
Your sitesHazard contextBoundary
Selected location
Site A
Field locationOperation Viability Experimental
CAUTIONHazard impact detected
Investigate local conditions. Review current field information before acting.
Hazard contextReview exposure
Security & accessCheck coverage
Source datesVerify recency
Context, connected
Hazards · Conflict · Population · Weather · Outbreaks · Infrastructure · Earth observation
01 / Start with your world
Global signals + your operational dataYour locations give
the signals meaning.
Start with the places that matter to you.
Bring your sites, boundaries and operational attributes into one workspace. Connect the conditions around them to the work you need to do.
FacilitiesWarehousesInfrastructureProject sitesField locationsCommunities
How it worksFrom a location to a decision
- 01
Bring your places
Upload sites and administrative boundaries. Include the attributes that matter to your operation.
CSV / Excel / GeoJSON / Shapefile - 02
Add the context
Select an area, review connected feeds, and load optional population, security and infrastructure context.
Connected feeds + uploaded evidence - 03
Assess and brief
Review exposure and experimental decision views. Check the evidence and export a briefing for your team.
Map / Assessment / Briefing
02 / See the whole portfolio
One place, multiple risksKnow where to
look next.
Understand risk across an entire portfolio.
Compare detected impacts and batch viability recommendations. Investigate locations requiring attention, with hazards, security and infrastructure as context.
Your locationsSelect a site to locate it →
Illustrative impact-based batch results. No detected impact does not establish safety.
Operational area / illustrative
Your sitesHazard contextBoundary
From a portfolio to a place. Select a location to see it in context. Export a system-level decision brief for review.
Experimental The Prioritization Board ranks facilities and actions within selected administrative areas. Uploaded boundaries and an area selection are required.
Operation Viability Experimental
Can we
operate here?
Assess one location or an entire portfolio.
Review site recommendations using available disaster impacts, security and operational context. Batch assessment uses a more limited, impact-based view.
These are planning recommendations for human review. Confirm current field conditions before acting.
GO
Review readiness
Confirm the conditions needed for your operation.
CAUTION
Investigate constraints
Understand the drivers and what needs follow-up.
DELAY
Review timing
Consider constraints, timing and alternatives.
NOGO
Reassess before proceeding
Review the recommendation with your operational team.
03 / Follow the evidence
Context behind the assessmentA score is a starting point.
Ask what’s behind it.
Hazard decision views show contributing drivers, sources and limitations. Outbreak Response retains observation dates and source provenance in briefings and evidence exports.
Sources & datesDistinguish a reporting date from retrieval time.
Drivers & missing signalsReview contributing evidence and coverage gaps.
Assumptions & limitationsCheck what an assessment can and cannot establish.
Evidence detail varies by workflow. Mapped infrastructure does not confirm current access or operating capacity.
Evidence reviewIllustrative checklist
Site A / Review contextCAUTION
Hazard impact detected
Hazard context Source check
Review the source report, its reporting date and the location of detected impacts. No source observations are loaded in this illustration.
Security & infrastructure Coverage check
Review uploaded security-event dates and the coverage of optional infrastructure layers. A mapped road does not establish current access.
What needs follow-up Field check
Investigate local conditions. Confirm local conditions and missing evidence with your team before deciding.
Operational briefingIllustrative
Site A
Hazard impact detected
Review promptInvestigate local conditions.
Context · Drivers · Follow-up
From data to briefing
Give your team
a shared starting point.
Use AI-assisted analysis and situation reports to interpret workspace context. Export decision briefs, or use Outbreak Response for dated, source-linked briefings.
Experimental Forecasts and Operational Outlook offer planning scenarios and drivers to review. They do not establish what will happen next.
Explore the workspaceBuilt around the work
Example applicationsDifferent missions.
A shared need for context.
For teams whose work depends on physical places, from field operations to distributed infrastructure.
Government & Civil Protection
Review hazards, exposed locations and infrastructure across selected operational areas.
Infrastructure & Field Operations
Assess conditions around physical sites, projects and field locations.
Logistics & Distributed Operations
Review location exposure and available road, bridge, fuel and airport context to investigate access constraints.
Enterprise Risk
Compare location-based exposure across an uploaded portfolio and identify sites for further review.
Applications of existing platform tools, not separate industry products or customer claims.
Our starting point
Built in complex operating environments.
Aidstack originated from the need to bring fragmented disaster, health, population, security and operational data together for teams working in complex environments.
Outbreak response in practice
Connect reported case indicators with population denominators, uploaded movement connections, workspace security and facility context, and dated response indicators.
Where are conditions changing? Where is response evidence missing? These are prompts for investigation; movement does not establish transmission.
Workspace apps
Open workspace One platform. Focused workflows.
Build on the core intelligence platform with focused workflows. The App Hub brings specialized tools into your map workspace, using the boundaries and context each app needs.
Immunization planning
Turn settlement data into a session plan with explicit coverage gaps and resource assumptions.
Explore this workflow
- Import CSV or Excel, or use workspace sites.
- Assign session dates, teams and delivery modes; record delivered counts.
- Estimate doses, stock gaps, team-days and team budgets.
- Save scenarios, export a planning workbook and restore JSON backups.
Requires uploaded administrative boundaries.
Outbreak Response
Bring reported indicators, geographic context and response decisions into a dated, source-linked briefing.
Explore this workflow
- Upload aggregate CSV, Excel or JSON data, or connect the DRC public-source preset.
- Compare trends and explore areas, mobility connections, mining and security context.
- Track response indicators and actions with owners, resources and due dates.
- Save snapshots; export HTML, Markdown, evidence JSON and SVG visuals, or print to PDF.
Start with tables and trends; add boundaries for maps.
Add tools as your workflow grows
Open Apps on the map to install and launch an included app. Use Add app to upload a compatible app ZIP and review its requested access before installation. An example app is available in the hub.
Apps, saved plans and snapshots stay in this browser and workspace. Disabling an app retains its saved plans.
Data & evidence
Multiple sources.
One geographic context.
Combine connected feeds with your own data and optional layers. Each source has its own coverage, dates and limitations.
GDACSAPI feed
Disaster alerts and impact geometry. Availability and update timing depend on the source.
WHO Disease Outbreak NewsAPI feed
Published outbreak reports mapped where reported locations can be resolved; not a case surveillance feed.
ACLEDUploaded data
Upload conflict-event exports. Coverage and recency depend on the file you provide.
Your locations & boundariesUploaded data
CSV or Excel sites, shapefile ZIP or GeoJSON boundaries, and relevant operational attributes.
OpenStreetMapOptional API layer
Load infrastructure categories for selected administrative areas. Mapped features do not confirm current access or capacity.
WorldPopOptional · Earth Engine
Population and age-sex context for uploaded administrative areas; requires a configured Earth Engine service.
Google Earth EngineOptional context layers
Flood, drought, accessibility, nighttime lights and Sentinel imagery/radar context. Change comparisons and hazard decision views remain experimental.
Open-MeteoForecast API
Weather forecast context where requested. Forecasts and cached responses have their own time windows.
A few practical questions
Before you explore.
Start with your geography.
Build the context from there.
What should I upload first?
Start with a CSV or Excel file containing name, latitude and longitude. Add operational attributes as extra columns. Upload administrative boundaries as a shapefile ZIP or GeoJSON to use area-scoped enrichment and prioritization.
Is Aidstack only for humanitarian teams?
No. Its origins are in humanitarian and global-health workflows, but the core platform works with user-provided locations. The broader applications above use those same mapping and assessment tools; they are not separate industry products.
Can I assess many sites together?
Yes. Batch Operation Viability returns per-site recommendations and a combined readiness view based on available impact data. It is more limited than a detailed individual assessment. Large uploads depend on browser, service and model limits; no tested capacity guarantee is offered here.
Does AI predict what will happen or decide for me?
No. AI helps interpret workspace context and draft analysis. Forecast, Operational Outlook, Operation Viability and prioritization views are experimental planning aids. Review missing evidence, assumptions and current field information before acting.
Are all data layers live?
No. GDACS and WHO reports are retrieved through APIs; ACLED and your own files are uploads. Population, infrastructure and earth-observation layers are optional. Source dates, coverage and refresh behavior vary.
What can I share with my team?
Export individual or system-level decision briefs as HTML and use browser printing for PDF. Outbreak Response also exports source-linked HTML and Markdown briefings, evidence JSON and SVG visuals. Immunization planning exports a workbook. Evidence detail varies by workflow.
A clearer view starts here
Your locations already exist.
The context around them
keeps changing.
Bring your sites and operational data into one workspace and understand the conditions developing around them.