Stop copy-pasting from that one "clean architecture" GitHub repo everyone uses. Vandor generates proper DDD backends in Go with bounded contexts, use cases, and on-demand infrastructure via VPKG. Core-first, no bloat.
Powered by things you've heard of
Vandor does the boring architecture stuff so you can focus on making your startup's "innovative business model" actually work. We won't judge.
Domain-Driven Design First
Actually implements those patterns from the Blue Book you bought but never finished. Aggregates, bounded contexts, the whole shebang.
VPKG Package System
Community packages for infrastructure because we're not arrogant enough to think we know every database you'll want to use.
Core-First Architecture
Clean separation between domain and infrastructure. Your business logic won't know what HTTP is, and that's beautiful.
Actions & Aliases
Package-powered commands that extend your CLI. `vandor vpkg exec` or shortcut aliases like `vandor add:http-handler`. No Task runner needed.
Spoiler: We're not trying to replace Rails. But if you're writing Go, this might be helpful.
Need more convincing? We made a whole page about this.
See the Full Comparison (with charts!)We actually read the books (so you don't have to)
Like npm, but for Go infrastructure (and smaller)
Starts faster than you can say "webpack building..."
Born from the rage of seeing "one table = one domain" for the 47th time. Seriously, who started that? Vandor exists because someone needed to stop developers from treating Eric Evans' blue book like an abstract art piece open to interpretation.
No more "should this go in domain or adapter?" Slack debates. No more hexagonal layers getting freaky with each other. Just clean code that won't make your future self want to time travel back and slap you.
Core-first. Runtime-independent. Actually stable.
Official VPKG starter set. Add only what you need.
shadcn/ui vibes but for backends. You own the code
Free forever. Not a bait-and-switch
We made up these complaints because we don't have real testimonials yet. But hey, at least we're honest about it.
"I hate Vandor"
— Guy who maintains vandor/http package
Still writes VPKG packages every weekend
"Rails had generators in 2005"
— Ruby developer
Forgot Rails also doesn't enforce DDD
"Why not just use Spring Boot?"
— Java architect
Waiting 30 seconds for JVM to start
"This is just Go with extra steps"
— Minimalist developer
Currently debugging their 12th circular dependency
"Vandor doesn't even support Rust"
— Rust evangelist
Wrong programming language, but we appreciate the enthusiasm
"I'll switch to microservices when hell freezes over"
— Monolith enjoyer
Vandor works great for monoliths too actually
Seriously, it's this easy. We counted.
Current version (we ship decently fast)
Official packages (more coming when we feel like it)
Free forever (probably)
We thought about charging but then remembered we're developers making a developer tool. Awkward.
Forever (unless we get really desperate)
MIT License - Do whatever you want, we're not your parents
Built by developers who got tired of setting up the same architecture for the 47th time. Now it's your turn to save 3 days of Googling "golang clean architecture example".
No corporate BS. Just straight answers to your skeptical questions
Still have questions? Ask on GitHub Discussions
Stop debating where your repository interface belongs and just ship. Vandor handles the architecture police work so you can focus on making your startup founder happy (or at least less stressed).
Open Source (for real)
Actually permissive
Not a freemium trap