Eleven days ago, I pushed the initial commit for SupportSage — an open-source tool that optimizes 3D printing support structures.
Today, it has exactly one star.
If you've never maintained an open-source project, you might laugh at that number. One star? That's the celebration?
Yes. Yes it is.
Why One Star Matters More Than a Thousand Page Views
Page views are passive. Someone's browser loaded your page. Maybe they were bored at work, or clicked a link from Reddit, or a search engine sent them. They saw the page for 3 seconds and moved on.
A star is active. Someone looked at your code, your README, your screenshots. They understood what the project does. And they made a deliberate choice to press that button — a small social signal that says "I see value in this."
That's a completely different signal-to-noise ratio.
What This One Star Actually Means
When I check the analytics:
- 303 total dev.to reads across 10 SupportSage-related articles
- 24 unique GitHub visitors in 14 days
- 781 repo clones (people are actually pulling the code!)
- 1 star
The conversion funnel from visitor to believer is brutally honest. Most people browse, nod, and leave. Only one person said "this matters to me."
And that's fine. Open source is a marathon, not a sprint.
What SupportSage Looks Like After 11 Days
Since launch, the project has grown from a CLI-only script to a full integration suite:
| Interface | Status |
|---|---|
| CLI | ✅ Core features |
| Web Demo (no backend) | ✅ Live |
| Desktop GUI | ✅ Released |
| Cura Plugin | ✅ Ready |
| FilamentDB integration | ✅ Auto temp lookup |
| Printsight integration | ✅ Post-print inspection |
The benchmarks hold solid at 33% material savings across all test models — tree supports with per-island severity grading consistently outperform traditional uniform supports.
The repo is at github.com/bossman-lab/supportsage if you want to see for yourself.
What's Next for SupportSage
- v0.3.0 — Multi-material support (dissolvable interface + standard body)
- PrusaSlicer plugin — community demand is loud on this one
- Printsight v0.3 — print failure prediction from gcode analysis (not just post-print inspection)
These are real features that take real time. But the one star tells me someone's watching.
Build in Public: The Experiment Continues
I've been documenting every step — from the initial idea through benchmarks, GUI, plugin, and now the first-star milestone. Twenty-one articles on dev.to. Zero dollars in revenue. One star on GitHub.
Would I trade those metrics for a stealth-build that nobody sees? Not a chance.
The build-in-public thesis isn't about virality or overnight success. It's about:
- Committing publicly so you can't quietly abandon the project
- Getting feedback early from people who actually use the tools
- Building a trail of proof that you didn't fake it
- Winning one believer at a time
Today, I have one believer. That's one more than day one.
SupportSage is open source. MIT license. Contributions welcome.
Repo: github.com/bossman-lab/supportsage
