Your favorite restaurant just closed. Not because the food was bad, not because foot traffic dried up — because the platform took 25% of every order and the math stopped working. You've seen the V2EX thread circulating: "能不能有一个不以盈利为目的的外卖平台" (Can we have a non-profit food delivery platform?). You nodded along. I did too. But then I ran the numbers, and the fantasy collapsed.
This isn't just a China problem. Western devs have been burned by the same pattern with open source: "Why can't we have sustainable infrastructure without corporate sponsorships?" The answer is ugly, and it's the same answer hiding in that V2EX discussion.
The Platform Extraction Cycle
Here's what the V2EX thread reveals that most Western discussions miss: the food delivery duopoly in China (Meituan and ele.me) has created a Platform Extraction Cycle where every participant in the ecosystem is a cost center to be minimized.
平台抽成 (Píngtái chōu chéng): Platform commission. In the Chinese dev community = the percentage extracted per transaction, now euphemized into "service fees" as the actual extraction rate climbed past 20%. This is a signal about power asymmetry, not just pricing.
The consensus in that thread is that platforms are extractive. The reality the comments reveal is more complicated: the extraction isn't greed — it's the hidden cost of logistics, support, and infrastructure that nobody wants to pay for directly.
Let me show you what I mean.
The Trade-Off Nobody Talks About
When a platform charges 25% commission, here's where that money actually goes (approximately, based on industry reports and V2EX commenter breakdowns):
| Cost Center | % of Commission | What It Actually Pays For |
|---|---|---|
| Delivery logistics | 12-15% | Driver wages, insurance, vehicle maintenance |
| Platform infrastructure | 3-5% | Servers, payment processing, app maintenance |
| Customer acquisition | 2-4% | Marketing, discounts, user retention |
| Support operations | 2-3% | Customer service, dispute resolution |
| Profit margin | 2-5% | Investor returns, R&D, expansion |
Now remove the profit margin. You get a non-profit platform. Great. But you're still staring at:
- Delivery logistics (12-15%): Who pays drivers? If it's not the platform, it's the restaurant or the customer. The V2EX post doesn't answer this.
- Infrastructure (3-5%): Servers don't run on vibes. Payment processors charge fees regardless of your mission statement.
- Support (2-3%): Someone has to handle the "where's my order" complaints at 11 PM.
The non-profit model doesn't eliminate costs — it just changes who absorbs them. And in every historical example, "the community" absorbs exactly none of it until it's too late.
The Open Source Sustainability Parallel
This is where I need to stop pretending this is just a China problem. Western devs face the exact same pattern with open source infrastructure.
The Maintenance Debt Spiral: You use a library maintained by one person in their spare time. The library works great. Until it doesn't — and then you discover the maintainer burned out 6 months ago, the GitHub issues are a graveyard, and you're staring at a migration that will cost you 3 sprint cycles.
The V2EX thread asks: "Can't we have food delivery without extractive platforms?" The open source community asks: "Can't we have sustainable infrastructure without corporate sponsorship?" The answer from both communities' failure modes is the same: somebody has to pay, and "the community" is not a person.
I've seen this play out in three different contexts:
- Patreon for dev tools: Developers pledge $5/month to "support open source." The math doesn't work. $5/month from 1,000 users = $60,000/year. One full-time maintainer costs $120,000+. The gap doesn't close.
- Cooperative platforms: Worker-owned delivery cooperatives exist. They work at small scale. They collapse when they hit the coordination costs of city-wide operations.
- Community-funded infrastructure: Remember when Mastodon was going to replace Twitter? The servers are still there. The funding model never materialized.
The pattern is consistent: non-profit models optimize for low cost (good for users) and sacrifice operational sustainability (the infrastructure quietly rots until a crisis exposes it).
The Skeptical Take: Why Non-Profit Platforms Actually Accelerate Consolidation
Here's where I deviate from the V2EX consensus, and where I think the discussion is missing the real trap.
The non-profit model doesn't fight the duopoly — it enables it.
Here's the logic:
- A non-profit platform launches with community funding and volunteer labor.
- It works beautifully for 500 users in a single city.
- It hits the coordination wall: support tickets pile up, drivers demand stable income, servers strain.
- Either it dies quietly (most likely), or it professionalizes — hires staff, builds infrastructure, creates hierarchy.
- At step 4, it becomes what it hated: an organization with operational costs that must be covered.
The duopoly wins because it already has the infrastructure. The non-profit never gets there.
In my experience running a small SaaS that tried the "community-supported" model for 18 months: we optimized for low prices (attracting users) and sacrificed cash reserves (we had $3,000 in the bank when the AWS bill arrived). The math was simple. Income was voluntary. Expenses were not.
What Actually Works (The Unpopular Answer)
The V2EX thread wants a solution. Here's the uncomfortable one: the problem isn't profit — it's competition.
Meituan and ele.me extract 25% because they can. There's no alternative at scale. The solution isn't removing profit from the equation — it's making the market competitive enough that 25% becomes 8%.
This is what the comments in that thread are circling but never land on: the platforms aren't extractive because they're for-profit. They're extractive because they're monopolies. The profit is a symptom.
The non-profit platform fantasy is seductive because it promises to remove the bad actor. But the bad actor is a structural feature of monopoly, not a character flaw. Change the structure, not the morality.
The Survival Checklist (For Platform Builders and Platform Users)
If you're building any platform (delivery, SaaS, dev tools), here's what you should be asking before you promise "non-profit" or "community-supported":
- Map the actual costs before you map the community: Infrastructure, support, and compliance don't care about your mission statement. Run the numbers for year 3, not year 1.
- Identify who absorbs costs when "the community" doesn't: Volunteer labor is finite. Pledges are optional. Bills are not. Name the person or mechanism, not the abstract group.
- Design for failure modes, not happy paths: What happens when donations drop 40%? When a major contributor burns out? When a competitor undercuts your prices? The non-profit model requires more redundancy, not less.
- Measure sustainability, not just traction: "We have 10,000 users!" is not a metric. "We have 10,000 users and enough recurring revenue to pay one full-time maintainer" is a metric.
- Accept that some problems require organizations, not communities: Logistics, 24/7 support, and infrastructure at scale are organizational problems. "Community" is a wonderful word for participation. It's a terrible word for accountability.
What's your take?
I've been wrong about this before — I once helped build a "community-focused" dev tool that died because we never figured out who was going to pay for the servers when the initial enthusiasm faded. What's your experience with non-profit or community-funded infrastructure? Did it survive year 3?
Drop a comment below — I respond to every one.
Discussion on V2EX, June 2026: "能不能有一个不以盈利为目的的外卖平台" (79 replies)
Discussion: What's your experience with community-funded or non-profit platforms? Did they survive past year 2, and what actually broke them?
Top comments (0)