Hackyard

I really like the capped Yard concept.

Hiding vote counts until voting closes is the detail that makes this work, since that is exactly where big hackathons turn into bandwagons. How do you keep the same-model rule enforceable?

I really like the capped Yard concept. Keeping the hackathons small while hiding vote counts until the end seems like a smart way to give every build a fair chance to be noticed.

Hackyard’s small, focused format makes it easier for every builder to get meaningful feedback—not just the loudest pitch. I’m building Chivalry Test, a privacy-first character quiz, and I appreciate communities that help independent projects get seen. Good luck to everyone joining the next Yard!

Finally a hackathon format for solo builders. No team coordination stress, no pre‑building advantage, and every project actually gets eyes on it. The permanent profile badges are also a fantastic touch for building public maker credentials.

Love it, can we all participate in those? Money Prices?

The capped Yard format with one named model for everyone so nobody wins on budget is a smart constraint. If model bills start adding up on other projects, pzero.studio is where we buy leftover capacity.

I really like the capped Yard concept.

Hackyard has that rare builder-first energy that immediately makes you want to open a project and start creating something. I love products that don’t just give developers another tool, but actually make experimentation feel exciting again. If you can keep that sense of freedom while removing the usual friction between an idea and a working build, Hackyard could become a seriously addictive place for builders. This feels like something made by people who genuinely love creating things.

Hidden vote counts until close is the detail that makes this credible - most "community voted" hackathons let momentum snowball early and everyone just votes for whoever's already winning. Curious how you handle the "one model for everyone" pick when a new frontier model drops mid-week vs an older reliable one.

great concept honestly, let's see how it goes tbh.

The capped-Yard model is the clever part here: capping entries at 20-100 per event and hiding vote counts until the deadline directly kills the two failure modes of most hackathons (bandwagon judging and submissions that never had a real shot). Curious how you keep the shared base model fair across teams with very different prompt-engineering skill.

Love the community-first approach to hackathons. Hidden votes make the competition feel much fairer. Small, focused Yards sound like a great way to discover genuinely great builds. 🔥

The one-year Champion sponsorship is the standout for me. Most hackathons end the moment the winners are announced, but long-term support could help a weekend build become a real product. What does the sponsorship include—distribution, mentorship, infrastructure credits, or something else?

The capped Yard format and hiding vote counts until the end is a brilliant way to ensure solo builders get equal visibility without bandwagon voting.

Hackyard Your product has strong potential, but I found a few key improvements that could make it even better. I'd love to share my feedback and suggestions—please contact me at [email protected].

Really like the builder-first approach here. Keeping each Yard small, using the same AI model for everyone, and hiding vote counts until the end makes the competition feel much fairer. The 48-hour solo format also sounds like a great way to actually ship something instead of just polishing a pitch deck. Great concept!