Building
Productivity
LumaFlow
Turn scattered ideas into products people can actually use.
A local-first workspace for small product working groups, connecting proposals, validation, building, and release in one visible flow.
Open product file
COMMUNITY-DRIVEN PRODUCT COLLECTIVEISSUE 07 / 2026
Build products worth keeping, together.
A community collective proposing, testing, building, and maintaining useful products—across open source, proprietary software, free tools, and paid services.
06product files
04open proposals
03working groups
CURRENT CYCLESummer / 12 weeks
W07LF
LumaFlowBuilding
TR
TinyRelayLive
OF
OpenFrameLive
This weekThe LumaFlow group finished an offline-search prototype. No new project starts this week.
01 / SELECTED WORK
Products are not a backlog. They are decisions in motion.
Some have shipped, some are being tested, and some will stop when evidence runs thin. Every project shows where it truly stands.
All productsLive
Developer tools
TinyRelay
Release infrastructure that stays out of a small product’s way.
A composable set of open-source tools for changelogs, version pages, and lightweight release notifications.
Open product file
Planned
Research
SignalDesk
Collect signals that matter to your product—not every passing trend.
An industry-signal inbox for small teams that turns scattered competitor, community, and customer changes into actionable briefs.
Open product file
02 / THE HORIZON
Now, next, and maybe.
Time boundaries protect attention. Distant ideas keep a direction without pretending to be promises.
LumaFlow
Finish the closed alpha and make the core workflow dependable.
See current progress ↗SignalDesk
Validate whether a change deserves action before committing to a build.
Read the research premise ↗QuietForm
Keep the question open instead of building early to fill a roadmap.
Why it has not started ↗03 / FIELD NOTES
Document progress—and the moments we change our minds.
No growth theatre. Just release notes, research, and honest product trade-offs.
Browse all notesBuild logLumaFlow
LumaFlow Alpha, week six: removing a feature that looked essential
A community usability test led the working group to remove the priority system. Fewer options made the next useful move easier to see.
ReleaseTinyRelay
TinyRelay 1.2: plugin channels and a cleaner changelog
Custom outputs, commit-cleanup rules, and a better default template for small community projects.
Product thinking
Why our products do not all use the same license
Open source is not decoration, and proprietary is not the default. A license should fit the maintenance covenant.
Research noteSignalDesk
SignalDesk research: nobody needs another RSS reader
After 18 conversations, the question shifted from collecting more to identifying changes that deserve a new decision.
A SMALL COLLECTIVE WITH A LONG HORIZONCommunity means more than discussing together.
Community means more than discussing together.
It means sharing responsibility for every decision.
Open or proprietary, free or paid: none is a preset ideology. What matters is respect for users, a model that supports maintenance, and a community able to explain and review every choice.
How the collective works ↗01
Choose questions together
Working groups take ownership
Preserve user choice
Never build data traps
Publish real progress
Review decisions together