“A marketplace charges its sellers.” Flip that sentence and you get one of the more interesting businesses you can build: a member-owned data co-op where the people who supply the goods are paid out, not billed. Members contribute data, subscribers buy access, and contributors receive their share — by payout or non-custodial crypto — pro-rata to what they put in. Two plugins invert the flow, and the “sellers” become your beneficiaries with the money running toward them.

Data as a priceable good, not a file dump

The idea comes from an analysis on VBWD, a self-hosted, source-available full-stack SaaS SDK. The engine is the dataset plugin, and its model is precise: a dataset is priceable, purchase grants an entitlement, and the entitlement unlocks API access. As the original analysis puts it:

Subscribers do not buy a download; they buy the right to query, metered and governed, through an API the platform controls.

On the demand side, subscription is the natural fit: buyers are on tarif plans with recurring billing, entitlements granted, API access opened. The buyer side of a data co-op looks like any other subscription business — which is exactly why it is boring in the best sense. It is a solved shape.

The inversion: paying the suppliers

The interesting side is supply, and this is where the constellation stops resembling anything off the shelf. In an ordinary marketplace, withdraw moves a vendor’s sales proceeds out to them. In a data co-op you use the same plugin to distribute the subscription revenue to the contributors whose data made the product worth buying:

The flow that everyone knows as “pay the sellers” becomes “pay the members,” and the mechanics are identical because to the core it is the same thing: money owed, moving out, recorded against the invoice ledger.

Distribution is pro-rata — each contributor’s share reflects what they put in, and the split is arithmetic the core can hold because the point of truth is the invoice line item. Subscriber revenue is the asset; contributor payouts are the obligation; the engine keeps them in balance. Payouts settle through the provider-agnostic payment core or via non-custodial crypto to the contributor’s own wallet, which for a globally distributed set of contributors is often the only practical rail.

Referral grows a two-sided flywheel

A co-op has a two-sided growth problem: more contributors make the data more valuable, more subscribers make contributing more lucrative, and each pulls the other. The referral plugin lets you reward both sides for bringing more of both, and because it declares its incentives as line items against the same invoice, the rewards live on the ledger that already knows who is owed what — not a growth-hacking tool bolted on the side. And because plugins toggle on and off without a restart, you can launch with contribution and subscription alone, prove demand, then switch on payouts and referral as the co-op matures.

The honest boundary

VBWD gives you the priceable-entitlement-API pipeline, the subscription billing, the pro-rata payout engine, the crypto settlement, and the referral loop. It does not give you the hardest parts, which are governance and consent. You own the rules for what data may be contributed, the licensing under which members hand it over, the quality control that keeps the dataset worth buying, and the anti-abuse work of stopping someone from gaming the split with junk. Self-hosting personal data is a serious GDPR and stewardship responsibility, and paying contributors is a serious tax and compliance one. The platform removes the plumbing of collecting, gating, and distributing; it does not remove your duty to run the co-op fairly, lawfully, and with data your members genuinely agreed to share.

A co-op that pays its members is proven machinery pointed at the people who deserve the money — read the full analysis on VBWD, and the public code is on GitHub.

Written for Red Robot with AI assistance and human editing. Adapted from an original analysis published on VBWD.