I’ve been building something quietly over the past few months, mostly to scratch an itch I kept running into while working on personal projects.

It’s called AGAI — a small but growing web framework in Go.

I love Go for its simplicity, but when it came to web dev, I kept bouncing between ultra-minimal router libraries and overly abstract frameworks. I just wanted something that gave me:

Structure without ceremony

Templating that’s flexible but not verbose

Simple data components I can store in JSON or sync to DB

A way to just run the damn thing without a tangle of middleware

So I built this.

Why AGAI? AGAI gives you:

Model-driven development — define models, auto-sync schemas

A component system — think "JSON configs as database records"

Session support — works in-memory or on disk

PHP-style templates — yes, really. It parses them into Go templates

CLI-friendly: --migrate-model, --start-server, --help, etc.

It’s built for devs who like control but don’t want to reinvent the wheel for every new project. Not trying to replace Echo or Fiber or Gin — just offering another path for those of us who want fewer black boxes.

Still early — but usable It's currently at v0.2.1. I'm using it on a few small tools and sites of my own. Would love feedback from the HN crowd on the design decisions, especially:

The model/component system

The PHP-style templating syntax (good idea or bad nostalgia?)

What I’m missing that would make it useful in the real world

GitHub: https://github.com/vrianta/agai Docs are in the repo (clean + updated)

Thanks for reading — happy to answer questions or hear where I’ve gone totally off the rails.