Hey DailyDevs, I wanted to share a side project I’ve been pouring time into lately: Goca.
If you’re like me, you’re tired of writing the same 20 files just to start a new Go service following Clean Architecture. The layers, the interfaces, the DI config—it’s necessary, but it’s pure boilerplate.
That’s where Goca comes in. It’s a CLI tool that generates a full, production-ready Go feature (entity, use case, repository, HTTP handler) in seconds, all while strictly enforcing Uncle Bob’s Clean Architecture rules. It’s essentially my way of cutting out the setup tax.
Heads up: This is still very much in beta. It’s working great for my own projects, but there are definitely rough edges, and I’m still figuring out the best ways to handle database migrations and multi-protocol setups.
It’s open source (MIT licensed), and I’m genuinely looking for feedback from people who actually build production Go apps. If you hate boilerplate as much as I do, please check out the documentation and let me know where it breaks for you.
Link to the docs:<a href="https://sazardev.github.io/goca/" target="_blank" rel="noopener nofollow">https://sazardev.github.io/goca/</a>

Smiley Face

Kashitsuwa

Goca is an open-source CLI tool that automatically generates production-ready Go features following Clean Architecture principles. It creates entities, use cases, repositories, and HTTP handlers to eliminate repetitive boilerplate code when starting new Go services. Currently in beta with MIT license, the tool aims to reduce setup time while enforcing architectural best practices.

I finally built the Go project generator I always wanted: Goca (Beta)

Ahah you made me laugh with the “What developers say” section. This is a good idea of project and I will certainly look at it :)

Will try it out for a new project and will be giving you feedback along the way

Will give a try but why did you choose GORM?
Can I use other like sqlx?