Open Food Network

A not-for-profit open-source ecommerce platform, honestly reviewed. Built for farmers markets, food hubs, and co-ops — not another SaaS checkout.

TL;DR

• What it is: Open-source (AGPL-3.0) online marketplace platform that connects farmers, food hubs, and consumers through a shared distribution network [README].
• Who it’s for: Farmers market organizers, food co-ops, food hubs, and community-supported agriculture (CSA) operations who need multi-vendor order management without paying SaaS commissions on every sale [website].
• Cost savings: Commercial food marketplace platforms typically take 2–5% per transaction plus monthly fees. OFN self-hosted is $0 in licensing — your cost is a server and a technical person to set it up [README][2].
• Key strength: Genuinely used by 2,500+ enterprises in 15+ countries. This isn’t a proof-of-concept — it’s production software that food hubs are running real businesses on [website][1].
• Key weakness: Ruby on Rails stack with a non-trivial deployment footprint. The LocallyGrown competitor puts it plainly: “managing open source tools as the core of a business is beyond the available skills and energy for most markets” [2]. For food producers who struggle with spreadsheets, self-hosting OFN is a serious undertaking.

---

What is Open Food Network

Open Food Network is an online marketplace platform for local food distribution. The core use case: a food hub, farmers market operator, or buying group creates an online shop, onboards multiple producers as suppliers, and lets customers place orders across all of them in one cart. Think of it as the back-office software for a farmers market that wants to take online pre-orders — order management, producer payouts, customer accounts, and delivery logistics in one place.

The project is backed by the Open Food Foundation, a not-for-profit. That’s not a marketing claim — it’s structurally a different model than VC-backed SaaS. The code is AGPL-3.0, which means you can self-host it freely, but any modifications you deploy publicly must also be open-sourced. This matters: AGPL is more restrictive than MIT, and if you’re planning to white-label it or embed it in a commercial product, you need to understand the license carefully.

The README describes it in one sentence: “Connect suppliers, distributors and consumers to trade local produce.” That’s accurate and exactly as narrow as it sounds. This is not a general-purpose ecommerce platform. It’s purpose-built for the local food supply chain — multi-vendor, multi-hub, with producer-centric features like per-producer order reports and variant-level inventory management.

The project sits at 1,232 GitHub stars, which is low by software standards but misleading for a niche. A tool used by food hubs doesn’t need developer adoption numbers — it needs enterprise adoption numbers, and 2,500+ enterprises across 15+ countries is a more honest measure of real-world traction [website].

---

Why people choose it

The third-party data on OFN is thinner than for mainstream dev tools — the user base is food hub operators, not software reviewers. What exists is a curated testimonials page [1] and an illuminating counterpoint from a direct competitor [2].

The honest case for OFN comes from its users. Sara Rock at Tamar Valley Food Hub says the software “streamlined our admin so we can grow in every sense of the word” and specifically credits the order reports and payment processing [1]. Reuben Chesters at Locavore credits it with “increasing turnover, making it easy for people to add products to their weekly veg box, pay online and give us any special delivery instructions” [1]. George Monbiot, writing as OFN UK Ambassador, frames the value as structural: “owned and controlled by the people who grow, rear, process and eat the food” — a transparent supply chain that commercial platforms structurally can’t provide [1].

The common thread across testimonials is administrative relief for multi-producer coordination. Before OFN, the equivalent workflow involves spreadsheets, email chains, manual invoicing, and per-producer reconciliation. OFN centralizes this into one platform.

The honest case against OFN comes from its competitor. The LocallyGrown.net founder built a paid SaaS specifically because open source wasn’t working for the target audience. His argument is direct: “what they need most isn’t free software — it’s freedom from managing software” [2]. He ran Athens Locally Grown on open source tools starting in 2002, spent years evangelizing that approach at agriculture conferences, and eventually concluded that farmers and market managers don’t have the technical bandwidth to own the infrastructure. His estimate for what self-hosting actually costs: $50–150/hour for a technical contractor and 5–20 hours per month of ongoing maintenance — plus $20–200/month in hosting [2].

That framing is useful because it’s honest about who OFN self-hosting is actually for. If you’re a food hub manager who also does bookkeeping, customer service, and producer relations, spending 5–20 hours per month on server administration is a real cost, not a footnote.

The OFN community forum shows a different side: sophisticated operators experimenting with the platform’s flexibility. The French affiliate white-labeled it for sustainable building supplies. Canadian users adapted it for flower farms. There’s active exploration of using it for carbon credits, organic waste processing, and fiber/textile networks [4]. The underlying multi-vendor order management logic is general enough that it extends beyond food when someone with technical depth is at the wheel.

---

Features

Based on the README and website:

Core marketplace:

• Multi-producer online shops — one customer cart, multiple suppliers
• Order management with per-producer breakdowns
• Inventory management with product variants (size, weight, etc.)
• Order cycling — scheduled open/close windows for order taking
• Customer accounts and order history
• Online payments (integrates with payment gateways — specific list not in available data)
• CSV/report exports for producer fulfillment
• Customer-facing shop with producer profiles

Hub and distribution:

• Hub model — a single “distributor” entity can aggregate from multiple “producer” entities
• Permissions system for producer-hub relationships
• Markup management — hubs can mark up producer prices before selling
• Delivery and pickup scheduling

Multi-instance network:

• OFN runs nationally-affiliated instances (UK, Australia, France, Canada, etc.) — each country’s instance is independently hosted but shares the same codebase
• Producers registered in one instance can potentially supply to hubs across the network

What’s not in the available data: specific payment gateway list, detailed API documentation, mobile app support, specific inventory sync capabilities. The feature list on the official guide (User Guide) is more comprehensive than what’s derivable from the README.

Technical stack: Ruby on Rails, PostgreSQL, Redis. Ansible playbooks provided for server provisioning [README]. BrowserStack for cross-browser testing, KnapsackPro for parallel test runs [README]. This is a substantial Rails application, not a simple install.

---

Pricing: SaaS vs self-hosted math

This is where the data gets sparse. OFN’s pricing page wasn’t included in the scraped data, and fabricating SaaS pricing numbers would violate what this review is supposed to do. What the available data does tell us:

Self-hosted (Community Edition):

• License: $0 (AGPL-3.0) [README]
• Server: Using LocallyGrown’s estimates as a benchmark, expect $20–200/month depending on scale [2]
• Technical maintenance: 5–20 hours/month if you’re doing it yourself; $50–150/hour if you hire out [2]
• Setup: Ansible playbooks are provided, but this is a Rails app with PostgreSQL and Redis — not a one-click deploy

Nationally-hosted OFN instances: OFN operates through country-specific affiliates (OFN UK, OFN Australia, etc.) who run the software and charge local enterprises to use it. These are the “SaaS” equivalent for most users. Pricing data for these wasn’t available in the scrape. Check your local OFN affiliate’s website directly — the model varies by country.

What the math looks like for self-hosting: If you currently pay $200–500/month to a commercial marketplace platform that takes a percentage of sales plus monthly fees, the server cost is trivially lower. The non-trivial cost is the technical overhead. A food hub processing $50,000/month in orders paying 3% transaction fees is paying $1,500/month in fees. Even with a $150/hr contractor for 10 hours/month ($1,500), the breakeven is at relatively modest volumes. At higher volumes, self-hosting economics become obvious. At lower volumes, the managed SaaS option (your local OFN affiliate) is probably the right call.

---

Deployment reality check

The README points to Ansible playbooks (ofn-install) as the provisioning path, and a Super Admin Guide for post-install configuration [README]. There’s a dedicated GETTING_STARTED.md and CONTRIBUTING.md for developers [README].

What you actually need:

• A Linux VPS with meaningful specs — this is a Rails monolith, not a Go binary. Budget 4GB+ RAM minimum for production.
• PostgreSQL and Redis
• A domain, SSL (Caddy or nginx)
• SMTP for transactional email
• Comfort with Ansible or someone who has it

What can go sideways:

• Ruby on Rails deployments have more moving parts than Docker Compose tools. Ansible helps, but troubleshooting a failed playbook run requires actual sysadmin competency.
• The LocallyGrown founder’s core argument applies directly here: “Even with great documentation and role model markets to follow, managing open source tools as the core of a business is beyond the available skills and energy for most markets” [2]. He ran with open source tools for years before concluding this.
• AGPL license means any public modifications must be shared back. If you want to customize OFN and keep those customizations private, you have a licensing problem.
• The globally-federated nature of OFN means your instance is independent — you don’t automatically benefit from producer or customer networks on other countries’ instances.

Realistic time estimate for a technical user: A few days end-to-end to get a production instance stable, configured, and tested — not a weekend project. For a non-technical food hub operator doing it themselves: this probably isn’t the right path. Use a managed OFN instance through your country’s affiliate, or hire someone to deploy it once.

---

Pros and Cons

Pros

• Purpose-built for the actual use case. Every feature in OFN exists because a food hub or farmers market needed it. Multi-producer orders, order cycles, hub markups, producer reports — these aren’t bolted on. They’re core [README][1].
• Actually deployed at scale. 2,500+ enterprises in 15+ countries isn’t GitHub-star vaporware. Real food hubs use this for real orders [website].
• Not-for-profit mission alignment. The people running OFN are trying to disrupt concentrated agri-food power, not exit to a strategic acquirer. This matters for software you’re building a food business on [README].
• Strong community and global affiliates. Slack, a community forum, an active handbook, country-specific affiliates who provide support — this is not a one-person project [README].
• Real testimonials from real operators. The testimonials page has named people, named organizations, and specific operational benefits — not generic praise [1].
• Flexible enough to extend. The platform has been adapted for flower farming, sustainable building supplies, and organic waste processing — the multi-vendor distribution logic is more general than food-only [4].

Cons

• AGPL license creates legal friction. MIT lets you self-host, embed, fork, and stay silent. AGPL requires you to open-source modifications you deploy. For a food hub that just wants to run the software as-is, this is fine. For anyone building a commercial product on top, this requires a lawyer conversation.
• Technical overhead is real. Ruby on Rails + PostgreSQL + Redis + Ansible on a VPS is not a simple deployment. The LocallyGrown founder spent 20+ years in this space and concluded the maintenance burden is too high for most market operators [2].
• Low GitHub stars for a comparison signal. 1,232 stars doesn’t indicate quality, but it does indicate a small developer community contributing integrations and fixes — compared to, say, WooCommerce’s plugin ecosystem.
• Niche use case. This is not a general ecommerce platform. If you need a traditional product catalog, checkout flow, and one-vendor shop, OFN is the wrong tool.
• Federated model has limits. Each country’s OFN instance is independently run. There’s no single global network you tap into — you’re deploying your own island.
• Limited third-party review data. The software doesn’t show up in mainstream SaaS review aggregators (G2, Capterra) with significant data — which makes independent quality assessment harder than for tools with broader developer adoption.

---

Who should use this / who shouldn’t

Use Open Food Network if:

• You run a food hub, buying group, farmers market, or CSA that coordinates orders across multiple producers.
• Your current workflow involves spreadsheets, email, and manual reconciliation — and you’re processing enough volume that the maintenance overhead of self-hosting is cheaper than SaaS commissions.
• You want software that’s genuinely aligned with the local food mission, backed by a not-for-profit, and not trying to extract a percentage of every transaction indefinitely.
• You have a technical person (staff or contractor) who can handle a Rails deployment and ongoing server administration.
• You’re in a country with an active OFN affiliate and you want the managed version — the deployment burden disappears and you still get open-source software.

Skip self-hosting (use a managed OFN affiliate instead) if:

• You’re a food hub operator without technical staff. The LocallyGrown founder’s point lands: most market managers should not be in the business of managing software infrastructure [2]. Your local OFN affiliate exists precisely for this.

Skip OFN entirely if:

• You’re a single-vendor farm selling direct. Shopify, WooCommerce, or even a Square site is simpler and better suited.
• You need a general-purpose ecommerce platform with a large plugin ecosystem. OFN doesn’t have that.
• You want an MIT-licensed codebase you can embed in a commercial product without open-sourcing your modifications. AGPL blocks that path.
• You’re building for any domain other than physical goods distribution through local networks. The platform’s abstractions (producers, hubs, order cycles) are food-and-distribution-specific.

---

Alternatives worth considering

• Shopify / WooCommerce — general-purpose, vastly more plugins and support options, but per-transaction fees and no multi-producer hub model. Right for single-vendor farms.
• LocallyGrown.net — a paid SaaS built by someone who started with open source and concluded the maintenance burden wasn’t worth it for most markets [2]. Worth evaluating if you want managed software without deployment headaches.
• Farmigo / Barn2Door — commercial CSA-focused SaaS platforms. No self-hosting option, but purpose-built for farm direct sales.
• CS-Cart Multi-Vendor — commercial multi-vendor marketplace software, more general-purpose than OFN, proprietary license.
• Coopcycle — AGPL-licensed platform for food delivery cooperatives. Similar philosophy, different use case (last-mile delivery vs. order management).
• Odoo — open-source ERP with ecommerce module. Much more complex, much more general. Right for larger food businesses that need accounting and inventory integrated.

For the core OFN use case — a food hub coordinating pre-orders across multiple producers — there isn’t a clear open-source equivalent with comparable real-world deployment history. The honest answer is: OFN self-hosted, a managed OFN affiliate, or a purpose-built SaaS like LocallyGrown. The choice depends on your technical capacity and volume.

---

Bottom line

Open Food Network is genuine software solving a real problem that most ecommerce platforms ignore: multi-producer local food distribution with transparent supply chains and no per-transaction extraction. The 2,500+ enterprises and 15-country deployment record prove it works in production. The not-for-profit backing and AGPL license mean the people running it have structurally different incentives than a VC-backed SaaS.

The honest caveat is also real: self-hosting a Rails application is not a weekend project, and the competitor’s argument that most food hub operators shouldn’t manage their own infrastructure is not wrong [2]. If you’re in a country with an active OFN affiliate, start there — same software, no deployment burden, support included. If you have the technical capacity to self-host and the volume to justify it, the licensing cost is zero and the mission alignment is hard to match. If you’re a single-farm operation or want a general ecommerce platform, look elsewhere.

---

Sources

1. Testimonials — Open Food Network (curated testimonials from food hub operators, ambassadors, and producers). https://openfoodnetwork.org/testimonials/
2. LocallyGrown.net — “Why Pay for LocallyGrown Instead of Using Free Open Source?” (first-hand account from a competing platform founder who started with open source tools). https://locallygrown.net/why-not-open-source
3. r/selfhosted — Reddit — “Are Self-Hosters Overlooking Crucial Network Issues?” (general self-hosting discussion on real operational overhead). https://www.reddit.com/r/selfhosted/comments/1979cnf/are_selfhosters_overlooking_crucial_network_issues/
4. Open Food Network Community Forum — “What, other than food, could the Open Food Network be used for?” (community discussion on platform extensibility beyond food distribution). https://community.openfoodnetwork.org/t/what-other-than-food-could-the-open-food-network-be-used-for/1787

Primary sources:

• GitHub repository and README: https://github.com/openfoodfoundation/openfoodnetwork (1,232 stars, AGPL-3.0 license)
• Official website: https://www.openfoodnetwork.org
• User Guide: https://guide.openfoodnetwork.org/
• Provisioning playbooks: https://github.com/openfoodfoundation/ofn-install