Connect
Sign up to receive our monthly newsletter.
Inquiries
Have a question? Contact us here.
Job Opportunities
Learn about job openings.
Digital Public Goods Alliance - 2026
Sign up to receive our monthly newsletter.
Have a question? Contact us here.
Learn about job openings.
AgriOS is an open-source, subscription-free ERP designed for African agri-SMEs. It integrates business operations with traceability to improve efficiency, ensure compliance, and unlock access to finance.
Owner
Advance Insight
Type
API, database, web
Licence
LGPL-3.0, MPL-2.0
Last evaluated
08.09.2026
Origin country
Netherlands
contact
bernard@advanceinsight.devRelease date
-
DPG since
08.09.2026
The following repositories were submitted by the solution and included in our evaluation. Any repositories, add-ons, features not included in here were not reviewed by us.
N/A
N/A
Swahili, French
Regen Organics, 10000 smallholder farmers Siongiroi Dairy Farmers Cooperative Society Limited, 2003 smallholder farmers Toothpick Project, Toothpick Co. Ltd., 13400 smallholder farmers Kumbatia Seafoo…
* This information is self-reported and updated annually
SDG 1: No Poverty: By enabling smallholder-facing SMEs to access finance and premium markets, AgriOS improves the economic resilience of the rural economy. SDG 2: Zero Hunger: The platform boosts food security by formalising supply chains, reducing waste through better inventory management, and supporting the production of high-quality produce. SDG 8: Decent Work and Economic Growth: AgriOS facilitates the formalisation of the agricultural sector and creates high-value local jobs for independent service providers. SDG 9: Industry, Innovation and Infrastructure: It serves as a scalable Digital Public Infrastructure (DPI) that bridges the digital divide for resource-constrained SMEs.
No mandatory proprietary dependencies
Yes
Principles for Digital Development, Privacy by Design
PII data is collected and stored but NOT distributed.
AgriOS ensures data privacy and security through a multi-layered approach that combines the robust technical security of the Odoo framework with specific workflows designed for consent management and data sovereignty. 1. Privacy by Design: Free, Prior and Informed Consent (FPIC) To prevent the adverse impact of unauthorised data collection, AgriOS integrates Free, Prior and Informed Consent (FPIC) into the data entry workflow. Before sensitive Farmer Profiling or Farm Mapping data can be finalised, the system requires the operator to upload verifiable evidence that the farmer has consented to the data collection. This ensures that the Data Subject is aware of and has agreed to the processing of their PII. 2. Storage Security: Role-Based Access Control (RBAC) Built on the Odoo Community platform, AgriOS inherits enterprise-grade security protocols. Access to PII is strictly governed by Role-Based Access Control (RBAC): Granular Permissions: Access is restricted by user role. For example, a Warehouse Manager may view Inventory and Sales records but is technically restricted from accessing sensitive Farmer Contracts or Accounting payouts. Secure Infrastructure: As a self-hosted solution, the data resides on infrastructure controlled by the user organisation, ensuring data sovereignty and preventing third-party data mining. 3. Distribution Safety: Anonymisation for Finance To prevent privacy risks during data sharing, the Capital Facilitation Model is designed to process personal credit data internally but output it as an anonymised data package. This allows users to share credit-relevant operational metrics with external lenders (like Vula) to secure financing without exposing the raw PII of their farmers to multiple third parties unnecessarily. 4. Data Integrity: Audit Trails & Immutable Records To ensure data integrity and prevent manipulation (which could lead to regulatory non-compliance under EUDR), the system maintains a timestamped audit trail of all critical actions. This includes logging changes to Farm Mapping polygons and risk mitigation efforts. Furthermore, the roadmap includes integration with the AgStack Asset Registry to create unique, permanent "public geoIDs" for land plots, ensuring an immutable link between the physical asset and its digital record.
Content is collected stored and distributed.
(1) Policies for identifying inappropriate and illegal content As a self-hosted Enterprise Resource Planning (ERP) system, AgriOS empowers the User Organisation (the Agri-SME or Cooperative) to act as the primary moderator of its own content. The solution supports this through: Internal Governance Policies: AgriOS is operationalising the ISO 18716 standard, enabling organisations to define and upload their own governance structures, by-laws, and codes of conduct directly into the Farmer Management Module. This establishes the internal policy framework for what constitutes acceptable content and behaviour within the organisation. HR & Ethics Policies: The HR Module includes a repository for storing and version-controlling HR policies and procedures. This allows the organisation to formally define policies regarding harassment, fraud, and appropriate use of the system by staff. Regulatory Compliance Standards: The system embeds external legal standards as policy baselines. For example, the EUDR Compliance Suite automatically flags content (produce/land plots) that violates European Union Regulation 2023/1115 regarding deforestation as "non-compliant" (effectively illegal for export purposes). (2) Mechanisms/features for detecting, moderating, reporting, and removing inappropriate/illegal content AgriOS provides robust technical mechanisms to enforce these policies: Automated Detection (EUDR): The system features an automated "deforestation check" that screens uploaded geospatial content against satellite data and cut-off dates. If a land plot overlaps with a protected area or deforestation event, the system detects this "illegal" content and flags the associated product as high-risk on the compliance dashboard. Moderation via Access Control: To prevent the upload of inappropriate content, the system uses strict Role-Based Access Control (RBAC). Only authorised staff (e.g., HR Managers, Compliance Officers) have the "Write" permissions necessary to upload legal documents, HR records, or land titles, acting as a preventative moderation layer. Reporting & Grievance Workflows: The system includes a structured workflow to manage mitigation actions and risk assessments. This serves as a reporting mechanism where staff can log identified risks (social, environmental, or governance) and track the resolution process. Removal & Correction: Administrators retain full rights to remove or archive erroneous or fraudulent records. However, to ensure accountability, the system maintains a timestamped audit trail of all changes and mitigation efforts, ensuring that the removal of content is transparent and traceable.
Yes
(1) Policies and Processes for Protection (Code of Conduct) For the Open-Source Community (Contributors): AgriOS, as a project, adopts a standard Contributor Code of Conduct (e.g., the Contributor Covenant). This policy explicitly prohibits harassment and outlines the enforcement process for reporting and addressing abuse within the repository, issue trackers, and community channels. Community maintainers have the authority to block or ban contributors who violate these standards to ensure a safe collaborative environment. For End-Users (SME Staff): Within the ERP software itself, protection is managed through Internal Governance and Role-Based Access Control (RBAC): HR Policy Enforcement: The HR Module allows the user organisation to publish and store internal policies, including "Codes of Conduct" and "Anti-Harassment Policies," making them accessible to all staff users. System Auditing: The system maintains a timestamped audit trail, ensuring that any abusive interactions (e.g., inappropriate comments in the 'chatter' or task notes) are permanently recorded and attributable to a specific user ID, enabling management to take evidence-based disciplinary action. (2) Processes addressing the Safety and Security of Underage Users Primary Context (Child Labour Prevention): AgriOS is a B2B enterprise tool and is not marketed to or intended for direct use by children. However, the system actively protects the safety of minors in the agricultural supply chain. The EUDR Compliance Suite and Farmer Management Module include specific fields to verify compliance with Local Labor and Human Rights Laws. This allows organisations to strictly monitor their supply chains for Child Labour risks and store verifiable evidence of compliance, ensuring the safety of minors in the broader ecosystem. Contributor Context: To the extent that a minor may contribute to the open-source code, their safety is ensured through the Anonymity of the open-source contribution process (where real identities are not required for code submission) and the strict enforcement of the Community Code of Conduct described above, which creates a zero-tolerance environment for harassment. https://documentation.agrios.org/contributing/code_of_conduct.html
2026-09-08 03:16:12
Ricardo Torres (L2 Reviewer) submitted their review of AgriOS (152) and found it to be a DPG
2026-09-08 03:16:12
System unmarked AgriOS (13424) as a nominee
2026-09-08 03:15:36
Ricardo Torres (L2 Reviewer) passed 8. Standards & Best Practices for AgriOS (13424)
2026-09-08 03:15:09
Ricardo Torres (L2 Reviewer) passed 2. Open Licensing for AgriOS (13424)
2026-09-08 03:14:59
Ricardo Torres (L2 Reviewer) edited 2. Open Licensing for AgriOS (13424)
2026-09-08 03:14:08
Ricardo Torres (L2 Reviewer) passed General Information for AgriOS (13424)
2026-09-08 03:13:24
Ricardo Torres (L2 Reviewer) pulled AgriOS (13424) under review
2026-06-17 17:20:22
Bolaji Ayodeji (L1 Reviewer) submitted their review of AgriOS (13424)
2026-06-17 17:20:13
Bolaji Ayodeji (L1 Reviewer) passed 8. Standards & Best Practices for AgriOS (13424)
2026-06-17 17:20:12
Bolaji Ayodeji (L1 Reviewer) edited 8. Standards & Best Practices for AgriOS (13424)
2026-06-17 17:18:50
Bolaji Ayodeji (L1 Reviewer) passed 2. Open Licensing for AgriOS (13424)
2026-06-17 17:18:48
Bolaji Ayodeji (L1 Reviewer) edited 2. Open Licensing for AgriOS (13424)
2026-06-17 17:17:54
Bolaji Ayodeji (L1 Reviewer) passed General Information for AgriOS (13424)
2026-06-17 17:15:33
Bolaji Ayodeji (L1 Reviewer) pulled AgriOS (13424) under review
2026-06-01 14:39:09
New tag (Clarifications) added to application
2026-06-01 14:39:09
Application clarifications submitted, Application move to L1 for review again
2026-05-05 03:27:26
Ricardo Torres (L2 Reviewer) requested clarifications for AgriOS (13424)
2026-05-05 03:27:25
System marked AgriOS (13424) as a nominee
2026-05-05 03:27:16
Ricardo Torres (L2 Reviewer) require clarification on General Information for AgriOS (13424)
2026-05-05 03:25:44
Ricardo Torres (L2 Reviewer) passed Scale of Solution for AgriOS (13424)
2026-05-05 03:25:42
Ricardo Torres (L2 Reviewer) passed 9C. Protection from Harassment for AgriOS (13424)
2026-05-05 03:25:36
Ricardo Torres (L2 Reviewer) passed 9B. Inappropriate & Illegal Content for AgriOS (13424)
2026-05-05 03:25:31
Ricardo Torres (L2 Reviewer) passed 9A. Data Privacy & Security for AgriOS (13424)
2026-05-05 03:25:28
Ricardo Torres (L2 Reviewer) require clarification on 8. Standards & Best Practices for AgriOS (13424)
2026-05-05 03:24:29
Ricardo Torres (L2 Reviewer) require clarification on 2. Open Licensing for AgriOS (13424)
2026-05-05 03:23:18
Ricardo Torres (L2 Reviewer) passed 7. Privacy & Applicable Laws for AgriOS (13424)
2026-05-05 03:22:48
Ricardo Torres (L2 Reviewer) passed 6. Mechanism for Extracting Data for AgriOS (13424)
2026-05-05 03:22:16
Ricardo Torres (L2 Reviewer) passed 5. Documentation for AgriOS (13424)
2026-05-05 03:19:21
Ricardo Torres (L2 Reviewer) passed 3. Clear Ownership for AgriOS (13424)
2026-05-05 03:18:19
Ricardo Torres (L2 Reviewer) passed 1. SDG Relevance for AgriOS (13424)
2026-05-05 03:15:23
Ricardo Torres (L2 Reviewer) passed 4. Platform Independence for AgriOS (13424)
2026-05-05 03:15:21
Ricardo Torres (L2 Reviewer) moved AgriOS (13424) to under review
2026-05-05 03:15:10
Ricardo Torres (L2 Reviewer) finished consultation on 4. Platform Independence for AgriOS (13424)
2026-03-24 16:48:52
Ivan Perdomo (Expert) submitted their inputs on 4. Platform Independence for AgriOS (13424) as “input”
2026-03-24 14:59:49
Ricardo Torres (L2 Reviewer) requested consultation on 4. Platform Independence for AgriOS (13424)
2026-03-24 14:59:38
Ricardo Torres (L2 Reviewer) moved AgriOS (13424) to under consultation
2026-03-24 14:59:27
Ricardo Torres (L2 Reviewer) passed General Information for AgriOS (13424)
2026-03-24 14:57:48
Ricardo Torres (L2 Reviewer) pulled AgriOS (13424) under review
2026-03-13 13:52:40
Bolaji Ayodeji (L1 Reviewer) submitted their review of AgriOS (13424)
2026-03-13 13:52:40
System remove tag Late from AgriOS (13424)
2026-03-13 13:52:14
Bolaji Ayodeji (L1 Reviewer) passed Scale of Solution for AgriOS (13424)
2026-03-13 13:52:08
Bolaji Ayodeji (L1 Reviewer) passed 9C. Protection from Harassment for AgriOS (13424)
2026-03-13 13:51:30
Bolaji Ayodeji (L1 Reviewer) edited 9C. Protection from Harassment for AgriOS (13424)
2026-03-13 13:50:50
Bolaji Ayodeji (L1 Reviewer) passed 9B. Inappropriate & Illegal Content for AgriOS (13424)
2026-03-13 00:00:16
Bolaji Ayodeji (L1 Reviewer) passed 9A. Data Privacy & Security for AgriOS (13424)
2026-03-12 23:59:34
Bolaji Ayodeji (L1 Reviewer) failed 8. Standards & Best Practices for AgriOS (13424)
2026-03-12 23:59:08
Bolaji Ayodeji (L1 Reviewer) passed 7. Privacy & Applicable Laws for AgriOS (13424)
2026-03-12 23:59:06
Bolaji Ayodeji (L1 Reviewer) edited 7. Privacy & Applicable Laws for AgriOS (13424)
2026-03-12 23:57:51
Bolaji Ayodeji (L1 Reviewer) passed 6. Mechanism for Extracting Data for AgriOS (13424)
2026-03-12 23:56:27
Bolaji Ayodeji (L1 Reviewer) passed 5. Documentation for AgriOS (13424)
2026-03-12 23:56:12
Bolaji Ayodeji (L1 Reviewer) edited a note on 2. Open Licensing for AgriOS (13424)
2026-03-12 23:55:10
Bolaji Ayodeji (L1 Reviewer) passed 4. Platform Independence for AgriOS (13424)
2026-03-12 23:52:52
Bolaji Ayodeji (L1 Reviewer) passed 3. Clear Ownership for AgriOS (13424)
2026-03-12 23:52:48
Bolaji Ayodeji (L1 Reviewer) failed 2. Open Licensing for AgriOS (13424)
2026-03-12 23:52:28
Bolaji Ayodeji (L1 Reviewer) edited 2. Open Licensing for AgriOS (13424)
2026-03-12 23:52:21
Bolaji Ayodeji (L1 Reviewer) edited a note on 2. Open Licensing for AgriOS (13424)
2026-03-12 23:50:28
Bolaji Ayodeji (L1 Reviewer) passed 2. Open Licensing for AgriOS (13424)
2026-03-12 23:50:26
Bolaji Ayodeji (L1 Reviewer) edited a note on 2. Open Licensing for AgriOS (13424)
2026-03-12 23:49:58
Bolaji Ayodeji (L1 Reviewer) edited 2. Open Licensing for AgriOS (13424)
2026-03-12 23:49:12
Bolaji Ayodeji (L1 Reviewer) passed 1. SDG Relevance for AgriOS (13424)
2026-03-12 23:49:09
Bolaji Ayodeji (L1 Reviewer) edited 1. SDG Relevance for AgriOS (13424)
2026-03-12 23:47:53
Bolaji Ayodeji (L1 Reviewer) edited a note on 1. SDG Relevance for AgriOS (13424)
2026-03-07 04:00:01
System add new tag Late to AgriOS (13424)
2026-03-06 19:10:24
Bolaji Ayodeji (L1 Reviewer) passed General Information for AgriOS (13424)
2026-03-06 19:10:22
Bolaji Ayodeji (L1 Reviewer) edited General Information for AgriOS (13424)
2026-03-06 19:10:05
Bolaji Ayodeji (L1 Reviewer) edited General Information for AgriOS (13424)
2026-03-06 19:05:29
Bolaji Ayodeji (L1 Reviewer) pulled AgriOS (13424) under review
2026-02-02 14:25:07
Bernard Wright (Applicant) submitted application for AgriOS (13424)
