Blueprint · honestly labeled

An ecosystem engineered to outlive us.

How parts, prints, and finished witnesses reach people without SecuraCV in the middle — and why it keeps working when nobody's tending it. This page is the systems engineering, taught in the open: what's live, what's in design, and the projects that proved every mechanism before we borrowed it.

The operating principle

State in git. Checks in CI. Incentives elsewhere.

Ecosystems don't die of overload — they die of rot: a broken link, a stale part, a page someone forgot they owned. So every piece here is engineered as one of three durable things.

Files are the database

Vendor lists, build galleries, rosters, bills of materials — each is a plain file in the public repo, edited by pull request, rendered by this static site. No server to breach, no admin to lose interest. The way the gallery already reads builds.json.

CI is the caretaker

Scheduled jobs check what humans forget: is every part still stocked? Every link alive? Every printed model still matching its source? When reality drifts, the robot opens an issue. Nobody has to remember — that's the point.

Incentives live elsewhere

Whoever ships hardware has their own reason to keep shipping — a fab's commission, a vendor's margin, a maker's pride. The project maintains only what it must: firmware, docs, a flasher, and a catalog. Everything else is somebody's livelihood, not our chore.

The system

Five layers, no one in the middle

Each layer names who does the work, and what the project keeps. Status labels are honest — most machinery is designed, not shipped.

1

Parts find their way to makers BOMs live automation in design

Every device's bill of materials is a public, machine-readable file with part numbers at multiple distributors. One click builds a full cart at Digi-Key (their list API needs no account of ours); a weekly robot checks every line for stock and end-of-life at Mouser and Digi-Key on free tiers, and a link-checker sweeps for dead product pages. When a part fades, an issue opens itself before a maker ever hits a dead end.

Who ships: Mouser, Digi-Key, Seeed — parts we never touch. We keep: the CSVs and the checking robots.

2

Printed parts, printed forward models live program in design

Every enclosure is free forever — parametric OpenSCAD with committed STLs. For people without printers, vetted community members print at cost ("filament, energy, and wear"), the pattern the Voron project proved at 15,000-printer scale. Ours is stronger: a finished Canary signs its own build and health, so quality is verified by the device, not by a photo. Print-on-demand farms give anyone a card-payment path without touching our time.

Who ships: neighbors with printers, print farms. We keep: the models, the vetting checklist, and a roster file.

3

Kits built and sold by partners in design

The designs are open, so fabs can list them directly: order one from a shared-project page and the factory builds and ships it — a share of each order flows back to the community pool. Bigger partners can stock, list, and fulfill complete kits under their own operations. Independent sellers list on maker marketplaces. Nobody asks our permission, because the license already said yes.

Who ships: PCB fabs, kit partners, independent vendors. We keep: the shared-project listings and a vendors page.

4

The blessing: badges, not gatekeeping in design

A free compatibility badge — Works with SecuraCV — that any seller, printer, or enclosure remixer may use without asking. A primary mark reserved by simple public grant, recorded in a file anyone can audit. A vendors page that is itself a repo file: alphabetical, neutral descriptions, no rankings. And open-source-hardware certification from OSHWA, the neutral registry that tells commercial makers they're welcomed, not tolerated.

Who benefits: every honest seller. We keep: two documents and a badge file.

5

Money that never touches us in design

Commissions, royalties, and donations land in a fiscally-hosted community fund with a public ledger — the pool that pays a maker's parts and time when a neighbor asks for a witness they can't build (have one made). Money flows partner → fund → maker, in the open. Never customer → us.

Who holds it: a fiscal host with a public ledger. We keep: nothing — that's the feature.

The build gallery, grown up

Every remix credited, forever

The most-loved 3D-printing community mechanics of the last twenty years, rebuilt on files and git — where nobody can take them away.

Lineage

Remixes point both ways

Each entry in builds.json can name what it remixed — and the site shows the reverse too: everything remixed from yours. Credit chains survive because they're data in git, not rows in someone's database. Remix sources can even be external — a model on Printables, a bracket on Thingiverse.

Proof

Makes, with photos

"I made one" — a photo of real hardware on a real shelf — is the heartbeat of every maker community, and it's also the honesty filter: real prints, not renders. Makes join the gallery by pull request, credited like everything else.

Customization

Sliders in your browser

The enclosures are parametric OpenSCAD, the same format behind the beloved-then-abandoned Thingiverse Customizer. Ours runs as WebAssembly on this static site — adjust, preview, download your STL. No server to rot, and the same annotated file powers customizers on the big platforms too. Try the enclosure builder →

Reach

Mirrors, with the repo canonical

Official profiles on Printables and MakerWorld carry the models to where makers already are — every listing linking back here, every zip carrying its license. Never exclusive to any platform: the repo is the original, and you can leave with everything, anytime.

Education · learn from the field

Proven elsewhere, borrowed honestly

None of this is invented here. Each mechanism has a project that proved it at scale — and one cautionary tale that teaches what kills the commons.

Meshtastic — sell nothing, catalog everything

The LoRa mesh project ships zero hardware. Manufacturers build and sell the radios; the project keeps firmware, a device catalog, a web flasher, and a two-tier trademark policy — a free community badge anyone may use, a primary logo by public grant. Vendors fund development because being in the catalog and flasher is worth paying for.

Their trademark policy →

Voron — Print It Forward

A 3D-printer project whose printed parts are made by vetted community members at cost, with a public queue and a published defect checklist. Over 15,000 serialized machines, none shipped by the project. Our version swaps photo inspection for something stronger: the device's own signed self-test.

The PIF queue →

ESPHome — "for X" is the whole rule

Vendors sell pre-flashed devices under one elegant naming clause: a product may only end with "for ESPHome." Listing requires the config be open and the user able to re-flash — the community badge is earned by openness, and a browser flasher keeps every vendor honest.

Made for ESPHome →

Thingiverse — the cautionary tale

It invented the remix graph, photo makes, and the Customizer — then its owner closed the hardware, rewrote the terms, let the beloved tools rot, and leaked its users' data. The community stayed loyal for years and left the moment alternatives existed. The lesson isn't "don't build a commons." It's: never betray one. No silent relicensing, no exclusivity deals, no broken credit chains, no hostage data.

Why every file here stays in the open repo, forkable, forever.

OpenFlexure — eleven vendors, five continents

An open microscope manufactured by independent makers from Tanzania to Chile, coordinated by nothing more than a vendors page and a shared design. Distributed manufacturing of printed-parts-plus-electronics kits — the closest existing analog to a Canary ecosystem.

Their vendors page →

OSHWA — certification with teeth

Free self-certification against the open-hardware definition: a public ID, a searchable registry, and real enforcement against misuse. It's how a project signals — neutrally, permanently — that commercial derivatives are part of the plan.

The certification →

Systems engineering

Why it can't rot

The failure-mode analysis, in one breath.

No single point of caring

Every component is a repo file, a scheduled check, or another party's business. If we vanish, the files remain forkable, the checks keep filing issues, and the vendors keep selling — because their customers, not ours, are asking.

Drift is detected, not discovered

Out-of-stock parts, dead links, models whose printed files no longer match their source — each has a robot watching on a weekly clock, using free public APIs that cost nothing forever. Rot announces itself while it's still small.

Exit is trivial — so nobody needs to

Galleries, rosters, lineage, licenses: all in git, all yours, all forkable in one command. Twenty years of platform history says communities stay where leaving is easiest. We engineered for the exit precisely so it never happens.

Read the engineering

The full research and design — every tool named, every fee verified, every precedent cited — lives in the open repo as strategy doc 19, alongside the pricing and production docs it builds on. The markdown is the document of record; this page is the teaching version.

Doc 19 — The Open Fulfillment Network & Builds Ecosystem →

Everything labeled "in design" is exactly that — designed, argued, and written down, not shipped. In the spirit of the product, this page never pretends otherwise.