You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, I just want to say that Azimutt is genuinely one of the best database exploration tools I've come across. The ERD experience, the ability to handle large and messy schemas, the AML language... it's exactly what I've been looking for for years. I'm really impressed by what you've built here.
I'm currently planning to self-host Azimutt on a Kubernetes cluster for internal use at my company, and I'd love to commit to it as our go-to database documentation tool. Before doing so, I have a few questions about the release process that I couldn't find answers to in the docs.
Observations that raised some questions
The latest commit on main appears to be from ~8 months ago (603bc8c)
The Docker image ghcr.io/azimuttapp/azimutt:main was last pushed on 2026-03-23 — so it seems more recent than what the GitHub commit history shows
There are no versioned tags (no semver, no GitHub releases)
The Helm chart README itself explicitly states it is not versioned
This creates some uncertainty: is the public GitHub repo actually in sync with what gets built and deployed? Or is there a separate, private development branch?
Questions
Is the public repo up to date? Or is active development happening in a private branch/repo, with only occasional syncs to the public one?
Is there a plan for proper versioning? Even a simple tagging strategy (e.g. v2025.03) with a changelog would make a big difference for self-hosters — it would allow pinning to a known-good version and understanding what changed between updates.
How stable is the self-hosted experience intended to be? Is it a fully supported deployment path, or more of a best-effort community feature alongside the main SaaS offering?
I'm really hoping the answer is positive, because I genuinely want to use Azimutt long-term and make it part of our internal tooling. I just want to make sure I'm not building infrastructure on something that could silently diverge or break without warning.
Thanks a lot for the work you're doing on this, and for any clarification you can provide! 🙏
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi team 👋
First of all, I just want to say that Azimutt is genuinely one of the best database exploration tools I've come across. The ERD experience, the ability to handle large and messy schemas, the AML language... it's exactly what I've been looking for for years. I'm really impressed by what you've built here.
I'm currently planning to self-host Azimutt on a Kubernetes cluster for internal use at my company, and I'd love to commit to it as our go-to database documentation tool. Before doing so, I have a few questions about the release process that I couldn't find answers to in the docs.
Observations that raised some questions
mainappears to be from ~8 months ago (603bc8c)ghcr.io/azimuttapp/azimutt:mainwas last pushed on 2026-03-23 — so it seems more recent than what the GitHub commit history showsThis creates some uncertainty: is the public GitHub repo actually in sync with what gets built and deployed? Or is there a separate, private development branch?
Questions
Is the public repo up to date? Or is active development happening in a private branch/repo, with only occasional syncs to the public one?
Is there a plan for proper versioning? Even a simple tagging strategy (e.g.
v2025.03) with a changelog would make a big difference for self-hosters — it would allow pinning to a known-good version and understanding what changed between updates.How stable is the self-hosted experience intended to be? Is it a fully supported deployment path, or more of a best-effort community feature alongside the main SaaS offering?
I'm really hoping the answer is positive, because I genuinely want to use Azimutt long-term and make it part of our internal tooling. I just want to make sure I'm not building infrastructure on something that could silently diverge or break without warning.
Thanks a lot for the work you're doing on this, and for any clarification you can provide! 🙏
Beta Was this translation helpful? Give feedback.
All reactions