M&E Platforms
Monitoring and evaluation platforms aggregate programme data, track indicators against targets, and generate donor-compliant reports. These systems serve as the analytical layer for programme management, connecting data collection tools to strategic decision-making through dashboards, visualisations, and automated reporting workflows.
This page covers platforms designed for indicator management, results aggregation, and programme-level analytics. Adjacent categories include data collection tools (field data capture), case management systems (individual-level tracking), and business intelligence platforms (general-purpose analytics). The solutions assessed here focus on M&E-specific functionality: indicator hierarchies, disaggregation frameworks, target tracking, and development-sector reporting standards.
Assessment methodology
Tool assessments derive from official vendor documentation, published API references, release notes, and technical specifications as of 2026-01-11. Feature availability varies by product tier, deployment model, or region. Verify current capabilities directly with vendors during procurement. Community-reported information is excluded; only documented features are assessed.
Requirements taxonomy
This taxonomy defines evaluation criteria for M&E platforms. Requirements are organised by functional area and weighted by priority for mission-driven organisations. Adjust weights based on specific operational context.
Functional requirements
Core capabilities that define what the tool must do.
Indicator management
| ID | Requirement | Description | Assessment criteria | Verification method | Typical priority |
|---|---|---|---|---|---|
| F1.1 | Indicator definition and metadata | Ability to define indicators with full metadata including definition, calculation method, unit of measure, reporting frequency, and data sources. Complete indicator metadata ensures consistent interpretation across teams and reporting periods. | Full: comprehensive metadata fields, custom fields supported. Partial: basic metadata only. None: free-text definitions only. | Review indicator configuration interface; check available metadata fields | Essential |
| F1.2 | Indicator hierarchies | Support for nested indicator structures reflecting results frameworks, logical frameworks, or theories of change. Hierarchies enable aggregation from output to outcome to impact levels. | Full: unlimited nesting, multiple hierarchy types per indicator. Partial: fixed hierarchy levels. None: flat indicator lists only. | Configure multi-level results framework; verify rollup calculations | Essential |
| F1.3 | Disaggregation frameworks | Ability to define and apply disaggregation dimensions (gender, age, geography, vulnerability status) to indicators. Disaggregations must support intersection (e.g., female youth in rural areas). | Full: configurable dimensions, intersectional disaggregation, dimension inheritance. Partial: fixed dimensions, no intersection. None: manual disaggregation only. | Create indicator with multiple disaggregation dimensions; test intersectional reporting | Essential |
| F1.4 | Target setting | Ability to set cumulative and periodic targets with revision history. Targets should support multiple scenarios (conservative, expected, stretch) and automatic milestone calculation. | Full: multi-scenario targets, revision tracking, milestone automation. Partial: single target line only. None: no target management. | Configure annual targets with quarterly milestones; verify revision history | Essential |
| F1.5 | Indicator calculation types | Support for different calculation methods: sum, average, percentage, ratio, count distinct, weighted average, and custom formulas. | Full: all standard types plus custom formulas. Partial: limited calculation types. None: sum only. | Create indicators using each calculation type; verify results | Important |
| F1.6 | Indicator linking | Ability to link indicators across projects, programmes, and portfolios for aggregated reporting without double-counting. | Full: configurable linking rules, deduplication logic. Partial: simple aggregation only. None: manual consolidation required. | Link indicators across two projects; verify aggregated totals | Important |
| F1.7 | Indicator versioning | Track changes to indicator definitions over time with ability to view historical versions and understand how definition changes affect trend analysis. | Full: full version history, change comparison, impact analysis. Partial: version numbers only. None: no versioning. | Modify indicator definition; verify previous versions accessible | Desirable |
Data aggregation
| ID | Requirement | Description | Assessment criteria | Verification method | Typical priority |
|---|---|---|---|---|---|
| F2.1 | Multi-source data ingestion | Ability to import data from multiple collection tools (KoboToolbox, ODK, SurveyCTO, CommCare) and formats (Excel, CSV, JSON, XML). | Full: native integrations with major tools, API import, scheduled sync. Partial: file import only. None: manual entry only. | Configure automated import from two different data sources | Essential |
| F2.2 | Data validation rules | Configurable validation rules that flag anomalies, out-of-range values, and logical inconsistencies before data is aggregated. | Full: rule builder, threshold alerts, cross-field validation. Partial: fixed validation rules. None: no validation. | Create validation rule with threshold; test with anomalous data | Essential |
| F2.3 | Geographic aggregation | Ability to aggregate data across administrative hierarchies (village to district to region to national) with boundary changes over time. | Full: configurable hierarchies, boundary versioning, population weighting. Partial: fixed hierarchy. None: manual geographic grouping. | Aggregate data from village to national level; verify totals | Essential |
| F2.4 | Temporal aggregation | Support for different reporting periods (weekly, monthly, quarterly, annual) with automatic rollup and period comparison. | Full: flexible period definitions, multi-period comparison, fiscal year support. Partial: fixed periods. None: no temporal aggregation. | Configure quarterly reporting with annual rollup; verify calculations | Essential |
| F2.5 | Data source attribution | Track which data points came from which sources for audit purposes and quality assessment. | Full: source metadata preserved, source-level confidence scores. Partial: source tracking without confidence. None: no attribution. | Import data from two sources; verify source attribution in reports | Important |
| F2.6 | Duplicate detection | Identify and manage duplicate records when aggregating data from multiple sources. | Full: configurable matching rules, merge workflows. Partial: flag duplicates only. None: no duplicate detection. | Import overlapping datasets; verify duplicate identification | Important |
| F2.7 | Retroactive corrections | Ability to correct historical data with full audit trail and option to recalculate dependent indicators. | Full: correction workflow, cascade recalculation, audit log. Partial: corrections without recalculation. None: data immutable after entry. | Correct historical value; verify dependent indicators recalculate | Important |
Reporting and visualisation
| ID | Requirement | Description | Assessment criteria | Verification method | Typical priority |
|---|---|---|---|---|---|
| F3.1 | Dashboard creation | Ability to create configurable dashboards with charts, maps, tables, and key performance indicators. Dashboards should support filtering and drill-down. | Full: drag-and-drop builder, interactive filters, drill-down, embedding. Partial: template-based dashboards. None: fixed reports only. | Create dashboard with three visualisation types; test interactivity | Essential |
| F3.2 | Report templates | Pre-built and customisable report templates for common donor formats (USAID, FCDO, EU, UN). | Full: editable templates for major donors, custom template creation. Partial: fixed templates. None: no templates. | Generate reports in two different donor formats | Essential |
| F3.3 | Automated report generation | Schedule automatic report generation and distribution to stakeholders. | Full: scheduled generation, email distribution, multiple formats. Partial: scheduled generation only. None: manual generation. | Schedule weekly report; verify automated delivery | Important |
| F3.4 | Data visualisation types | Support for standard charts (bar, line, pie, area), geographic maps, pivot tables, and specialised development visualisations (progress gauges, target tracking). | Full: 10+ visualisation types including maps. Partial: 5-9 types. None: fewer than 5. | Create visualisations using each available type | Important |
| F3.5 | Export formats | Export data and reports in multiple formats: Excel, PDF, Word, PowerPoint, CSV, JSON. | Full: all listed formats with formatting preserved. Partial: 3-5 formats. None: fewer than 3. | Export same report in each available format | Important |
| F3.6 | Real-time updates | Dashboards and reports reflect current data without manual refresh. | Full: real-time or near-real-time (under 5 minutes). Partial: hourly updates. None: manual refresh required. | Update source data; measure time to dashboard update | Desirable |
| F3.7 | White-labelling | Ability to apply organisation branding to reports and dashboards for external stakeholder presentation. | Full: logo, colours, fonts, custom domains. Partial: logo only. None: no customisation. | Apply custom branding; verify in exported reports | Desirable |
Results framework support
| ID | Requirement | Description | Assessment criteria | Verification method | Typical priority |
|---|---|---|---|---|---|
| F4.1 | Logical framework structure | Support for standard logframe structure: goal, purpose, outputs, activities with indicators at each level. | Full: configurable logframe with assumptions column. Partial: fixed structure. None: no logframe support. | Create complete logframe; verify all standard elements | Essential |
| F4.2 | Theory of change mapping | Visual representation of causal pathways from activities to impact with indicator attachment points. | Full: visual editor, pathway validation, indicator linking. Partial: static ToC display. None: no ToC support. | Create theory of change; attach indicators to pathway nodes | Important |
| F4.3 | Cross-cutting themes | Track cross-cutting indicators (gender, environment, disability inclusion) across all projects and programmes. | Full: cross-cutting category with aggregation. Partial: tagging only. None: no cross-cutting support. | Configure cross-cutting theme; verify portfolio-level reporting | Important |
| F4.4 | Assumption tracking | Document and monitor assumptions underlying the results framework with risk flagging when assumptions fail. | Full: assumption register, monitoring indicators, alerts. Partial: documentation only. None: no assumption tracking. | Create assumptions; configure monitoring triggers | Desirable |
| F4.5 | Multiple framework support | Support different results frameworks (logframe, outcome mapping, developmental evaluation) within same platform. | Full: multiple framework types, configurable structures. Partial: logframe variants only. None: single framework type. | Configure two different framework types | Desirable |
Collaboration and workflow
| ID | Requirement | Description | Assessment criteria | Verification method | Typical priority |
|---|---|---|---|---|---|
| F5.1 | Data entry workflows | Configurable submission and approval workflows for data entry with role-based routing. | Full: multi-stage approval, conditional routing, rejection with comments. Partial: simple submit/approve. None: no workflow. | Configure three-stage approval workflow; test rejection path | Essential |
| F5.2 | Comment and annotation | Ability to add comments to data points, indicators, and reports for collaborative review. | Full: threaded comments, mentions, resolution tracking. Partial: simple comments. None: no commenting. | Add comments to indicator; test notification and resolution | Important |
| F5.3 | Data collection reminders | Automated reminders to data entry staff when reporting deadlines approach. | Full: configurable reminders, escalation, multiple channels. Partial: fixed reminders. None: no reminders. | Configure reminder schedule; verify delivery before deadline | Important |
| F5.4 | Audit trail | Complete history of all data changes, user actions, and system events for compliance and troubleshooting. | Full: comprehensive logging, exportable, searchable. Partial: change log only. None: no audit trail. | Review audit log for recent changes; verify completeness | Essential |
| F5.5 | Partner data collection | Enable implementing partners to enter data directly with appropriate access controls and review workflows. | Full: partner portals, delegated administration, data isolation. Partial: partner accounts without isolation. None: no partner access. | Configure partner access; test data isolation | Important |
Technical requirements
Infrastructure, architecture, and deployment considerations.
Deployment and hosting
| ID | Requirement | Description | Assessment criteria | Verification method | Typical priority |
|---|---|---|---|---|---|
| T1.1 | Self-hosted deployment | Ability to deploy on organisation-controlled infrastructure for data sovereignty, compliance, or cost management. | Full: complete feature parity, documented deployment. Partial: self-hosted with feature limitations. None: SaaS only. | Review deployment documentation; compare feature matrix | Important |
| T1.2 | Cloud deployment regions | Vendor-managed cloud deployment with regional options for data residency requirements. | Full: EU, US, and other regions documented. Partial: single region. None: undisclosed location. | Verify regional availability; check data residency documentation | Important |
| T1.3 | Container deployment | Support for containerised deployment using Docker and Kubernetes. | Full: official images, Helm charts, documented orchestration. Partial: community images only. None: no container support. | Check container registries; review orchestration documentation | Desirable |
| T1.4 | High availability | Support for redundant deployment eliminating single points of failure. | Full: documented HA architecture, automatic failover. Partial: manual failover. None: single-instance only. | Review architecture documentation; check HA configuration options | Context-dependent |
| T1.5 | Offline capability | Ability to function in environments without continuous internet connectivity. | Full: offline data entry with sync. Partial: cached read-only access. None: requires internet. | Test functionality after disconnecting from network | Context-dependent |
Scalability and performance
| ID | Requirement | Description | Assessment criteria | Verification method | Typical priority |
|---|---|---|---|---|---|
| T2.1 | Data volume capacity | Ability to handle large indicator datasets common in national health information systems. | Full: documented capacity for millions of data points. Partial: capacity limits documented. None: no capacity information. | Review performance documentation; check customer references | Important |
| T2.2 | Concurrent user support | Support for multiple simultaneous users without performance degradation. | Full: documented concurrent user limits, performance benchmarks. Partial: general scalability claims. None: no information. | Review scalability documentation | Important |
| T2.3 | Report generation performance | Time to generate complex reports with large datasets. | Full: benchmarks published, under 30 seconds for standard reports. Partial: general performance claims. None: no information. | Test report generation with sample large dataset | Important |
| T2.4 | API rate limits | Documented rate limits for API access with options for higher limits. | Full: documented limits, configurable for enterprise. Partial: fixed limits. None: undocumented. | Review API documentation for rate limit specifications | Important |
Integration architecture
| ID | Requirement | Description | Assessment criteria | Verification method | Typical priority |
|---|---|---|---|---|---|
| T3.1 | REST API | Comprehensive REST API for programmatic access to all platform features. | Full: complete API coverage, OpenAPI specification. Partial: limited API coverage. None: no API. | Review API documentation completeness; compare to UI features | Essential |
| T3.2 | Authentication methods | Support for standard authentication methods for API access. | Document: API keys, OAuth 2.0, service accounts, SSO integration. | Review API authentication documentation | Essential |
| T3.3 | Webhook support | Ability to push event notifications to external systems. | Full: configurable webhooks, retry logic, payload customisation. Partial: limited events. None: polling only. | Review webhook documentation; check event coverage | Important |
| T3.4 | Bulk operations | Support for efficient large-scale data import and export operations. | Full: batch APIs, streaming, async operations. Partial: limited batch size. None: record-by-record only. | Review bulk operation documentation; check limits | Important |
| T3.5 | IATI compliance | Support for International Aid Transparency Initiative data standard. | Full: native IATI export, validation, registry publication. Partial: export only. None: no IATI support. | Generate IATI export; validate against schema | Context-dependent |
| T3.6 | HXL support | Support for Humanitarian Exchange Language tagging for interoperability. | Full: HXL tagging in exports, automatic tag suggestions. Partial: manual tagging only. None: no HXL support. | Check export formats for HXL tag support | Context-dependent |
Security requirements
Security controls and data protection capabilities.
Authentication and access control
| ID | Requirement | Description | Assessment criteria | Verification method | Typical priority |
|---|---|---|---|---|---|
| S1.1 | Multi-factor authentication | Support for MFA on user accounts. | Full: multiple MFA methods (TOTP, WebAuthn), enforced by policy. Partial: single MFA method. None: password only. | Review authentication documentation; test MFA configuration | Essential |
| S1.2 | Single sign-on | Support for federated identity via SAML 2.0 or OIDC. | Full: SAML and OIDC, multiple IdP support. Partial: single protocol or IdP. None: local authentication only. | Review SSO documentation; check supported protocols | Essential |
| S1.3 | Role-based access control | Granular permission system based on organisational roles. | Full: custom roles, field-level permissions, geographic restrictions. Partial: fixed roles. None: all-or-nothing access. | Configure custom role with specific permissions; test enforcement | Essential |
| S1.4 | Row-level security | Restrict data visibility based on user attributes (geography, project, partner). | Full: configurable row-level policies. Partial: project-level isolation only. None: no row-level security. | Configure geographic restriction; verify data visibility | Important |
| S1.5 | Session management | Controls over session duration, concurrent sessions, and forced logout. | Full: configurable timeout, concurrent session limits, remote termination. Partial: fixed timeout. None: no session controls. | Review session configuration options | Important |
Data protection
| ID | Requirement | Description | Assessment criteria | Verification method | Typical priority |
|---|---|---|---|---|---|
| S2.1 | Encryption at rest | Data encrypted when stored in databases and file systems. | Full: AES-256 or equivalent, key management documented. Partial: encryption available but not default. None: no encryption. | Review security documentation for encryption specifications | Essential |
| S2.2 | Encryption in transit | All data transfers encrypted using TLS 1.2 or higher. | Full: TLS 1.3 support, no legacy protocols. Partial: TLS 1.2 only. None: unencrypted options available. | Check SSL configuration; verify protocol versions | Essential |
| S2.3 | Data export controls | Ability to restrict bulk data exports by user role or data classification. | Full: configurable export restrictions by role and data type. Partial: all-or-nothing export permissions. None: no export controls. | Configure export restriction; test enforcement | Important |
| S2.4 | Data retention policies | Configurable data retention with automated deletion. | Full: retention policies by data type, automated enforcement. Partial: manual deletion only. None: no retention controls. | Review retention configuration options | Important |
| S2.5 | Backup and recovery | Regular backups with documented recovery procedures and tested RPO/RTO. | Full: documented backup schedule, tested recovery, RPO/RTO published. Partial: backups without testing. None: customer responsibility. | Review backup documentation; check recovery procedures | Essential |
Compliance
| ID | Requirement | Description | Assessment criteria | Verification method | Typical priority |
|---|---|---|---|---|---|
| S3.1 | Security certifications | Third-party security certifications demonstrating security posture. | Document: ISO 27001, SOC 2, or equivalent certifications with dates. | Request current certification documents | Important |
| S3.2 | GDPR compliance | Compliance with EU General Data Protection Regulation requirements. | Full: DPA available, data subject rights supported, EU hosting option. Partial: partial compliance. None: no GDPR support. | Review GDPR documentation; check DPA availability | Important |
| S3.3 | Penetration testing | Regular security testing by independent parties. | Full: annual testing, findings remediated, summary available. Partial: testing without documentation. None: no testing. | Request penetration test summary | Important |
| S3.4 | Vulnerability disclosure | Published process for reporting security vulnerabilities. | Full: security contact, response timeline, acknowledgment. Partial: contact only. None: no disclosure process. | Check for security.txt or vulnerability policy | Desirable |
Operational requirements
Support, documentation, and organisational sustainability.
Support and documentation
| ID | Requirement | Description | Assessment criteria | Verification method | Typical priority |
|---|---|---|---|---|---|
| O1.1 | Technical documentation | Comprehensive documentation for administrators and developers. | Full: complete admin guides, API reference, deployment docs. Partial: user documentation only. None: minimal documentation. | Review documentation completeness and currency | Essential |
| O1.2 | User documentation | End-user guides and training materials. | Full: user guides, video tutorials, in-app help. Partial: basic user guide. None: no user documentation. | Review user documentation; check for training resources | Essential |
| O1.3 | Support channels | Available channels for technical support. | Document: email, phone, chat, community forum availability and hours. | Review support options; check response time commitments | Important |
| O1.4 | Community resources | Active user community for peer support and knowledge sharing. | Full: active forum, user groups, regular events. Partial: forum only. None: no community. | Check community activity levels | Desirable |
Pricing and licensing
| ID | Requirement | Description | Assessment criteria | Verification method | Typical priority |
|---|---|---|---|---|---|
| O2.1 | Pricing transparency | Clear, publicly available pricing information. | Full: published pricing, calculator available. Partial: pricing on request. None: opaque pricing. | Review pricing page; check for hidden costs | Important |
| O2.2 | Nonprofit pricing | Discounted pricing or free tiers for nonprofit organisations. | Full: significant discount (50%+) or free tier. Partial: modest discount. None: standard pricing only. | Review nonprofit programme details | Important |
| O2.3 | Data portability | Ability to export all data in standard formats for migration. | Full: complete export, standard formats, no additional cost. Partial: export available at cost. None: limited export. | Review data export documentation; check for restrictions | Essential |
| O2.4 | Contract flexibility | Flexible contract terms for organisations with variable funding. | Full: monthly terms, no long-term commitment required. Partial: annual with exit clause. None: multi-year required. | Review contract terms | Important |
Comparison matrices
Rating scale
| Symbol | Meaning | Description |
|---|---|---|
| ● | Full support | Feature fully implemented as documented |
| ◐ | Partial support | Feature available with limitations noted |
| ○ | Minimal support | Basic capability, significant gaps |
| ✗ | Not supported | Feature not available |
| - | Not applicable | Feature not relevant to this tool |
| ? | Unknown | Unable to verify from documentation |
Functional capabilities
| Requirement | DHIS2 | OpenFn | ActivityInfo | DevResults |
|---|---|---|---|---|
| Indicator management | ||||
| F1.1 Indicator definition | ● | - | ● | ● |
| F1.2 Indicator hierarchies | ● | - | ◐ | ● |
| F1.3 Disaggregation frameworks | ● | - | ● | ● |
| F1.4 Target setting | ● | - | ◐ | ● |
| F1.5 Calculation types | ● | - | ● | ● |
| F1.6 Indicator linking | ● | ● | ◐ | ● |
| F1.7 Indicator versioning | ◐ | - | ○ | ◐ |
| Data aggregation | ||||
| F2.1 Multi-source ingestion | ● | ● | ● | ● |
| F2.2 Data validation rules | ● | ◐ | ● | ● |
| F2.3 Geographic aggregation | ● | - | ● | ● |
| F2.4 Temporal aggregation | ● | - | ● | ● |
| F2.5 Source attribution | ● | ● | ◐ | ◐ |
| F2.6 Duplicate detection | ◐ | ◐ | ◐ | ○ |
| F2.7 Retroactive corrections | ● | - | ● | ● |
| Reporting and visualisation | ||||
| F3.1 Dashboard creation | ● | - | ● | ● |
| F3.2 Report templates | ◐ | - | ◐ | ● |
| F3.3 Automated reporting | ◐ | ● | ● | ● |
| F3.4 Visualisation types | ● | - | ● | ● |
| F3.5 Export formats | ● | - | ● | ● |
| F3.6 Real-time updates | ● | ● | ● | ◐ |
| F3.7 White-labelling | ◐ | - | ● | ● |
| Results framework | ||||
| F4.1 Logframe structure | ● | - | ◐ | ● |
| F4.2 Theory of change | ◐ | - | ○ | ● |
| F4.3 Cross-cutting themes | ● | - | ◐ | ● |
| F4.4 Assumption tracking | ○ | - | ○ | ◐ |
| F4.5 Multiple frameworks | ● | - | ○ | ◐ |
| Collaboration | ||||
| F5.1 Data entry workflows | ● | ● | ● | ● |
| F5.2 Comments and annotation | ◐ | - | ● | ● |
| F5.3 Collection reminders | ◐ | ● | ● | ● |
| F5.4 Audit trail | ● | ● | ● | ● |
| F5.5 Partner data collection | ● | - | ● | ● |
Notes on partial ratings:
- DHIS2 F1.7: Version history available for metadata but not full change comparison
- DHIS2 F3.2: Templates exist but require configuration; not pre-built for specific donors
- OpenFn: Not an M&E platform itself but integration layer; ”—” indicates features provided by connected M&E systems
- ActivityInfo F1.2: Supports hierarchies through relational forms but not native indicator tree structure
- ActivityInfo F4.1: Logframe achievable through form design but not purpose-built logframe module
- DevResults F3.6: Updates occur on data entry but dashboards may cache
Technical capabilities
| Requirement | DHIS2 | OpenFn | ActivityInfo | DevResults |
|---|---|---|---|---|
| Deployment | ||||
| T1.1 Self-hosted | ● | ● | ● | ✗ |
| T1.2 Cloud regions | ● | ● | ● | ◐ |
| T1.3 Containers | ● | ● | ✗ | ✗ |
| T1.4 High availability | ● | ● | ● | ● |
| T1.5 Offline capability | ● | ○ | ● | ○ |
| Scalability | ||||
| T2.1 Data volume | ● | ● | ● | ● |
| T2.2 Concurrent users | ● | ● | ● | ● |
| T2.3 Report performance | ● | - | ● | ● |
| T2.4 API rate limits | ● | ● | ● | ● |
| Integration | ||||
| T3.1 REST API | ● | ● | ● | ● |
| T3.2 Authentication | ● | ● | ● | ● |
| T3.3 Webhooks | ● | ● | ● | ◐ |
| T3.4 Bulk operations | ● | ● | ● | ● |
| T3.5 IATI compliance | ● | ◐ | ○ | ● |
| T3.6 HXL support | ● | ◐ | ○ | ○ |
Notes:
- DHIS2 T1.2: DHIS2 can be hosted in any region through self-hosting; managed hosting available through partners
- OpenFn T1.5: OpenFn CLI supports local execution; web platform requires connectivity
- DevResults T1.1: SaaS-only offering; no self-hosted option
- DevResults T1.2: Azure hosting with limited region documentation
Security capabilities
| Requirement | DHIS2 | OpenFn | ActivityInfo | DevResults |
|---|---|---|---|---|
| Authentication | ||||
| S1.1 MFA | ● | ● | ● | ● |
| S1.2 SSO | ● | ● | ● | ● |
| S1.3 RBAC | ● | ● | ● | ● |
| S1.4 Row-level security | ● | - | ● | ● |
| S1.5 Session management | ● | ● | ● | ● |
| Data protection | ||||
| S2.1 Encryption at rest | ● | ● | ● | ● |
| S2.2 Encryption in transit | ● | ● | ● | ● |
| S2.3 Export controls | ● | ◐ | ● | ● |
| S2.4 Retention policies | ◐ | ◐ | ● | ◐ |
| S2.5 Backup and recovery | ● | ● | ● | ● |
| Compliance | ||||
| S3.1 Certifications | ◐ | ○ | ● | ◐ |
| S3.2 GDPR compliance | ● | ● | ● | ● |
| S3.3 Penetration testing | ● | ● | ● | ? |
| S3.4 Vulnerability disclosure | ● | ● | ● | ○ |
Notes:
- DHIS2 S3.1: No formal certification as open source project; individual implementations may be certified
- OpenFn S3.1: Digital Public Good certified; SOC 2 in progress per documentation
- ActivityInfo S3.1: ISO 27001 certified
- DevResults S3.3: Security testing not documented in public materials
Individual tool assessments
DHIS2
Overview
DHIS2 (District Health Information Software 2) is an open-source platform for health information management developed by the HISP Centre at the University of Oslo. Originally designed for aggregate health data in developing countries, DHIS2 has expanded to support general M&E, education, and logistics use cases. The platform powers national health information systems in over 80 countries.
| Attribute | Detail |
|---|---|
| Vendor | HISP Centre, University of Oslo |
| Licence | BSD 3-Clause |
| Current version | 42 (January 2026) |
| First release | 2006 |
| Deployment model | Self-hosted, partner-hosted cloud |
| Pricing model | Free and open source |
Strengths
DHIS2 excels in aggregate data management at scale. The platform handles millions of data points across complex geographic and organisational hierarchies. Native support for disaggregation allows detailed analysis by gender, age, and other dimensions without duplicating indicator definitions. The analytics engine generates pivot tables, charts, and maps from aggregate data with sub-second response times for typical queries.
The data set concept aligns with periodic reporting common in health and development programmes. Data sets define which data elements are collected at which organisational units on which schedule, with configurable validation rules that run during data entry. The approval workflow supports multi-level review processes typical in hierarchical organisations.
Geographic information system capabilities are built into the core platform. Thematic maps display indicator values by administrative boundary, with support for multiple boundary layers and point locations. Map layers can be combined with external base maps and exported for offline use.
The indicator engine supports complex calculations including coverage rates, ratios, and population-weighted averages. Indicators can reference data elements from multiple data sets and include annualisation factors for periodic data. The calculation engine handles missing data according to configurable rules.
Limitations
DHIS2’s health-sector origins create friction for non-health use cases. Terminology throughout the interface uses health concepts (data elements, data sets, organisation units) that require translation for development-sector users. The tracker module for individual-level data adds complexity that aggregate M&E users may not need.
Report customisation requires technical skills. While the dashboard builder is accessible to trained users, creating formatted reports matching donor templates requires the Reports app or external tools. The built-in reporting options focus on data presentation rather than narrative reporting.
The learning curve is significant. Training programmes run several days, and effective use requires understanding of the platform’s conceptual model. Implementation typically requires external technical support, particularly for initial configuration and data migration.
Self-hosting demands infrastructure capacity. Minimum requirements include dedicated server resources, PostgreSQL database administration skills, and ongoing system maintenance. Smaller organisations without technical staff find self-hosting impractical, though managed hosting services address this gap at additional cost.
Deployment architecture
+------------------------------------------------------------------+| DHIS2 ARCHITECTURE |+------------------------------------------------------------------+| || +------------------------+ +------------------------+ || | WEB BROWSER | | ANDROID APP | || | | | | || | - Dashboard viewer | | - Data entry | || | - Data entry | | - Tracker capture | || | - Analytics | | - Offline sync | || +----------+-------------+ +----------+-------------+ || | | || +---------------+---------------+ || | || +--------v--------+ || | | || | DHIS2 CORE | || | (Java/Spring) | || | | || | - Web API | || | - Analytics | || | - Import/Export| || +--------+--------+ || | || +--------v--------+ || | | || | PostgreSQL | || | Database | || | | || +-----------------+ || |+------------------------------------------------------------------+Integration capabilities
DHIS2 provides a comprehensive REST API covering all platform functionality. The API uses JSON format and supports both synchronous operations and asynchronous job-based processing for large datasets. OpenAPI specifications are published for API documentation.
Pre-built integrations exist for common data collection tools including ODK, KoboToolbox, and DHIS2’s own Android applications. The ADX (aggregate data exchange) format enables standardised data exchange with other DHIS2 instances and compatible systems.
Web hooks can trigger external systems when specific events occur, enabling real-time integration with downstream systems. The app platform allows custom applications to be developed and deployed within DHIS2, extending functionality without modifying the core platform.
Documentation and support
Documentation spans user guides, implementer guides, and developer references at docs.dhis2.org. The developer portal at developers.dhis2.org provides API documentation, SDK references, and tutorials for custom development. Documentation quality is high, though volume can be overwhelming for new users.
Community support operates through the DHIS2 Community of Practice (community.dhis2.org), an active forum with responses from both community members and core team. The DHIS2 Academy programme provides structured training in multiple formats and languages.
Commercial support is available through the HISP network of regional organisations providing implementation, training, and hosting services. Support agreements vary by HISP partner.
OpenFn
Overview
OpenFn is a workflow automation and data integration platform designed to connect systems used in development and humanitarian programmes. Rather than serving as an M&E platform itself, OpenFn acts as integration middleware that moves data between M&E platforms, data collection tools, case management systems, and other operational software.
| Attribute | Detail |
|---|---|
| Vendor | Open Function Group |
| Licence | LGPL-3.0 |
| Current version | Lightning v2.14.14 (January 2026) |
| First release | 2014 (v1); 2023 (v2/Lightning) |
| Deployment model | SaaS, self-hosted |
| Pricing model | Free (self-hosted), tiered SaaS |
Strengths
OpenFn solves a specific problem that M&E platforms alone cannot: reliable, automated data flow between disconnected systems. The platform provides pre-built adaptors (connectors) for over 70 systems common in the development sector, including DHIS2, CommCare, Salesforce, ODK, and various ERP systems.
The workflow engine handles complex data transformation logic. Jobs written in JavaScript can filter, map, aggregate, and validate data as it moves between systems. The visual workflow editor in Lightning (v2) makes integration logic accessible to non-programmers while preserving code-level control for developers.
Error handling is robust. Failed jobs are logged with full context, enabling diagnosis and reprocessing. The platform maintains message queues that survive temporary destination system outages, preventing data loss during integration failures.
As a Digital Public Good, OpenFn maintains open governance with an Open Source Steering Committee. The fully open-source licensing (LGPL-3.0) with no “open core” restrictions ensures complete feature availability in self-hosted deployments.
Limitations
OpenFn is not an M&E platform. It does not store indicator data, generate dashboards, or produce reports. Organisations need a separate M&E platform (such as DHIS2, ActivityInfo, or DevResults) as the destination for integrated data.
Workflow development requires some technical skill. While the visual editor reduces the barrier, complex transformations still require JavaScript knowledge. The platform is most effective when implementation includes developer capacity for initial configuration and ongoing maintenance.
Self-hosted deployment requires Elixir/Phoenix framework expertise, which is less common than Python or JavaScript skills. The managed SaaS option addresses this but adds subscription cost.
The adaptor library, while extensive, may not include connectors for all systems an organisation uses. Custom adaptor development is possible but requires JavaScript development capacity.
Integration architecture
+------------------------------------------------------------------+| OPENFN ARCHITECTURE |+------------------------------------------------------------------+| || +----------------+ +----------------+ +----------------+ || | | | | | | || | KoboToolbox | | CommCare | | Custom API | || | (source) | | (source) | | (source) | || +-------+--------+ +-------+--------+ +-------+--------+ || | | | || +-------------------+-------------------+ || | || +--------v--------+ || | | || | TRIGGER | || | (webhook/cron) | || +--------+--------+ || | || +--------v--------+ || | | || | WORKFLOW | || | ENGINE | || | | || | - Transform | || | - Validate | || | - Route | || +--------+--------+ || | || +-------------------+-------------------+ || | | | || +-------v--------+ +-------v--------+ +-------v--------+ || | | | | | | || | DHIS2 | | Salesforce | | Database | || | (destination) | | (destination) | | (destination) | || +----------------+ +----------------+ +----------------+ || |+------------------------------------------------------------------+Documentation and support
Documentation at docs.openfn.org covers platform usage, adaptor development, and deployment. The documentation is well-organised with separate sections for different user roles (implementers, developers, administrators).
Community support operates through a Discourse forum at community.openfn.org. The core team actively participates in community discussions. Commercial support is available through Open Function Group and implementation partners.
ActivityInfo
Overview
ActivityInfo is a commercial platform for humanitarian and development data management, developed by a Netherlands-based company. The platform combines relational database capabilities with built-in analysis and reporting tools, designed for M&E, humanitarian coordination, and case management use cases.
| Attribute | Detail |
|---|---|
| Vendor | ActivityInfo B.V. (Netherlands) |
| Licence | Proprietary |
| Current version | 4.x (continuous deployment) |
| First release | 2009 |
| Deployment model | SaaS, self-managed server |
| Pricing model | Subscription (from €3,700/year) |
Strengths
ActivityInfo’s relational database model provides flexibility that fixed-schema M&E platforms lack. Forms can be linked to create complex data structures, enabling the platform to adapt to varied programme designs without customisation. This flexibility suits organisations managing diverse programmes with different indicator structures.
The mobile data collection app supports offline data entry with automatic synchronisation. The same forms used on the web platform work on mobile devices, eliminating the need for separate data collection tools in many deployments.
Analysis tools are integrated into the platform. Pivot tables, charts, and maps can be created without exporting data to external tools. The report designer supports formatted outputs for donor reporting, with scheduling for automated distribution.
The self-managed server option addresses data sovereignty requirements. Organisations can deploy ActivityInfo on their own infrastructure, including air-gapped networks, with full feature parity to the SaaS version.
Multi-language support spans 18 languages, with interface translations and right-to-left script support for Arabic. Form content can be translated for multilingual data collection.
ISO 27001 certification provides documented security assurance for procurement processes that require third-party security attestation.
Limitations
ActivityInfo’s general-purpose database model requires more initial configuration than purpose-built M&E platforms. Organisations must design their own indicator structures rather than working with pre-built M&E concepts. This flexibility has a setup cost.
The indicator concept differs from traditional M&E platforms. ActivityInfo treats indicators as calculated fields on forms rather than first-class objects with their own metadata. Achieving standard M&E indicator management patterns requires intentional database design.
Pricing places the platform above the budget of smaller organisations. The minimum subscription of €3,700/year excludes organisations with limited IT budgets, though partnership arrangements may reduce costs.
Results framework visualisation (logframes, theories of change) is not a native feature. While these structures can be represented in the database, the platform does not provide purpose-built tools for results framework management.
IATI and HXL support is limited compared to platforms designed specifically for development data interoperability.
Integration capabilities
The REST API provides programmatic access to all platform functionality. Documentation covers authentication, CRUD operations on forms and records, and query operations for data retrieval. An R client library is available for data analysis workflows.
Import capabilities support CSV, Excel, and external API data sources. The API import feature can pull data from external REST APIs on a scheduled basis.
Power Automate (Microsoft) and Make (Integromat) connectors enable integration with enterprise automation platforms.
Documentation and support
Documentation at activityinfo.org/support/docs covers user guides, administration, and API reference. The documentation is organised by topic with search functionality.
Support is provided through email with response times varying by subscription tier. Training webinars and onboarding services are available at additional cost.
DevResults
Overview
DevResults is a commercial M&E platform designed specifically for international development programmes, with particular focus on USAID contractor requirements. The Washington DC-based company has operated since 2009, serving primarily US government-funded development projects.
| Attribute | Detail |
|---|---|
| Vendor | DevResults (USA) |
| Licence | Proprietary |
| Current version | Continuous deployment |
| First release | 2009 |
| Deployment model | SaaS only |
| Pricing model | Subscription (project-based) |
Strengths
DevResults is purpose-built for development M&E, with native concepts matching standard programme management terminology. Indicators, results frameworks, disaggregations, and targets are first-class objects rather than generic database constructs. This reduces configuration time for organisations familiar with standard M&E approaches.
USAID reporting formats are particularly well-supported. The platform generates reports matching USAID Performance Indicator Reference Sheet (PIRS) requirements and other standard donor formats. Organisations reporting to USAID find immediate alignment with contractual requirements.
IATI compliance is native. The platform can export data in IATI format for publication to the IATI Registry, supporting transparency requirements common in donor agreements.
The user interface prioritises M&E workflows. Data entry, indicator management, and reporting follow patterns familiar to M&E officers without requiring technical configuration. Training requirements are lower than for general-purpose platforms.
Dashboard capabilities include interactive visualisations, geographic mapping, and progress tracking against targets. Dashboards can be shared with external stakeholders through published views.
Limitations
The SaaS-only model precludes self-hosting. Organisations with data sovereignty requirements or operating in environments with unreliable internet cannot deploy DevResults on local infrastructure.
Geographic coverage appears optimised for US government contracting contexts. While the platform functions globally, documentation and support resources orient toward USAID and similar bilateral donor requirements rather than UN or multilateral contexts.
Pricing is not publicly disclosed. Organisations must request quotes, making cost comparison difficult. Subscription models are typically project-based, which may create complexity for organisations with many small projects.
API documentation, while available, is less comprehensive than competing platforms. Integration capabilities exist but are less emphasised than core M&E functionality.
The platform does not appear to have published security certifications, though security practices are documented in marketing materials.
Integration capabilities
The REST API supports programmatic access to project data, indicators, and results. API tokens provide authentication for automated access. Documentation at devresults.com/api-help provides endpoint reference.
Pre-built integrations exist for Power BI, Dropbox, Google Drive, and SurveyCTO. The SurveyCTO integration enables direct import of survey data into DevResults data tables.
Bulk import via Excel templates supports initial data loading and periodic data updates.
Documentation and support
Documentation at help.devresults.com provides user guides, tutorials, and API reference. Content is organised as a knowledge base with search functionality.
Support is provided through email (help@devresults.com) with a help desk staffed by developers, per company documentation. Training resources include video tutorials and webinars.
Selection guidance
Decision framework
+------------------------------------------------------------------+| M&E PLATFORM SELECTION |+------------------------------------------------------------------+ | v +-------------------------------+ | Health sector or national | | HMIS requirement? | +---------------+---------------+ | +----------------+----------------+ | | v v YES NO | | v v +-------+-------+ +---------+---------+ | DHIS2 | | Data integration | | Strong health | | primary need? | | data model | +---------+---------+ +---------------+ | +--------------+--------------+ | | v v YES NO | | v v +-------+-------+ +----------+---------+ | OpenFn | | Self-hosting | | + downstream | | required? | | M&E platform | +----------+---------+ +---------------+ | +--------------+--------------+ | | v v YES NO | | v v +-------+-------+ +----------+---------+ | DHIS2 or | | USAID primary | | ActivityInfo | | donor? | | (self-hosted) | +----------+---------+ +---------------+ | +----------------+----------------+ | | v v YES NO | | v v +-------+-------+ +---------+---------+ | DevResults | | ActivityInfo | | Strong USAID | | Flexible database | | alignment | | model | +---------------+ +-------------------+Recommendations by context
Health programmes and national health information systems
Recommended: DHIS2
DHIS2’s design specifically addresses health information management at scale. The data element and indicator framework matches WHO health data standards. Aggregate data handling supports population health monitoring. The Android applications enable offline data collection in health facilities with intermittent connectivity.
DHIS2’s free licensing and large implementer community provide sustainability advantages for government health systems with limited IT budgets. The established HISP network offers localised support in many countries.
Considerations:
- Implementation requires external technical support for initial configuration
- Ongoing administration demands database and Linux system skills
- Learning curve requires multi-day training for effective use
Flexible programme data structures
Recommended: ActivityInfo
ActivityInfo’s relational database model suits organisations whose programmes do not fit standard M&E templates. The ability to design custom data structures accommodates varied programme types within a single platform. Mobile offline capability supports field data collection.
ISO 27001 certification facilitates procurement in contexts requiring security attestation. Self-managed server option addresses data sovereignty requirements.
Considerations:
- Minimum €3,700/year subscription excludes smaller organisations
- Initial database design requires M&E and data modelling expertise
- Less specialised for standard logframe/results framework patterns
USAID-funded development programmes
Recommended: DevResults
DevResults’ purpose-built design for development M&E reduces configuration time. Native PIRS templates and IATI export align with common USAID requirements. The user interface matches M&E officer workflows without technical abstraction.
Considerations:
- SaaS-only precludes self-hosting for data sovereignty
- Pricing not transparent; requires quote request
- Less suitable for health sector or non-USAID contexts
Multi-system integration requirements
Recommended: OpenFn + M&E platform
When data must flow between multiple systems (data collection tools, M&E platforms, case management, finance), OpenFn provides the integration layer. Combine with DHIS2, ActivityInfo, or DevResults for M&E storage and reporting.
OpenFn’s pre-built adaptors reduce integration development time. The visual workflow editor enables non-programmers to understand data flows. Error handling and retry logic ensure reliable data transfer.
Considerations:
- Requires separate M&E platform for storage and reporting
- Integration workflow development requires some technical capacity
- Self-hosting demands Elixir/Phoenix expertise
Organisations with minimal IT capacity
For organisations without dedicated IT staff, the following factors should guide selection:
| Factor | DHIS2 | OpenFn | ActivityInfo | DevResults |
|---|---|---|---|---|
| Self-hosting requirement | Challenging | Challenging | Manageable | N/A (SaaS) |
| SaaS availability | Via partners | Yes | Yes | Yes |
| Training requirements | High | Medium | Medium | Low |
| Ongoing maintenance | Significant | Moderate | Low | Low |
| Implementation support | Community + partners | Company + partners | Company | Company |
Recommendation order for minimal IT capacity:
- DevResults if USAID context and budget allows
- ActivityInfo SaaS if flexible data structures needed
- DHIS2 with managed hosting from HISP partner if health sector
- OpenFn SaaS + simple M&E platform if integration is primary need
Migration considerations
From spreadsheet-based M&E
All four platforms provide Excel import capabilities. Migration planning should include:
- Indicator metadata standardisation (definitions, disaggregations, calculation methods)
- Historical data validation and cleanup before import
- Geographic hierarchy definition matching organisational structure
- User role mapping to platform permission models
Allow 2-4 weeks for data preparation before platform migration.
Between M&E platforms
Data portability varies by platform:
| Platform | Export capability | Migration effort |
|---|---|---|
| DHIS2 | Complete metadata and data export in standard formats | Medium |
| OpenFn | Project configuration export; data in destination systems | Low (for OpenFn itself) |
| ActivityInfo | CSV/Excel export; API for bulk extraction | Medium |
| DevResults | Excel export; API for bulk extraction | Medium |
OpenFn can facilitate migration between platforms by automating data extraction from the source and loading to the destination.
External resources
Official documentation
FOSS tools
| Tool | Documentation | API reference | Source code |
|---|---|---|---|
| DHIS2 | docs.dhis2.org | developers.dhis2.org | github.com/dhis2 |
| OpenFn | docs.openfn.org | docs.openfn.org/adaptors | github.com/OpenFn |
Commercial tools
| Tool | Documentation | API reference | Nonprofit programme |
|---|---|---|---|
| ActivityInfo | activityinfo.org/support/docs | activityinfo.org/support/docs/api | Partnership arrangements available |
| DevResults | help.devresults.com | devresults.com/api-help | Pricing on request |
Relevant standards
| Standard | Description | URL |
|---|---|---|
| IATI | International Aid Transparency Initiative data standard for development cooperation | iatistandard.org |
| HXL | Humanitarian Exchange Language for tagging humanitarian data | hxlstandard.org |
| ADX | Aggregate Data Exchange format for DHIS2 interoperability | dhis2.org |
Related procurement resources
| Resource | Publisher | Description |
|---|---|---|
| Digital Square Global Goods Guidebook | PATH | Assessment of digital health global goods including DHIS2 |
| Digital Public Goods Registry | DPGA | Registry of certified digital public goods including OpenFn |
See also
- Monitoring and Evaluation Platforms - Implementation concepts for M&E systems
- Data Collection Tools - Mobile data collection tool comparison
- Humanitarian Data Interoperability - HXL, IATI, and data exchange standards
- Application Integration - Integration architecture patterns
- Data Pipeline Design - ETL and data flow patterns