On this page
NodaBroker is still in development — the banner at the top of every page on this site says so, and it’s not a formality. There’s no signed-up customer running it yet, no live instance anyone outside the team has touched. This blog is where we’ll post what’s actually true about that process as it happens, rather than waiting for a launch announcement to say anything at all.
Why write about it before it’s ready
Most software blogs start after a product ships: case studies, feature announcements, the occasional retrospective. We’d rather start earlier than that, for a simple reason — brokers evaluating a CRM are making a multi-year bet on it, and the decisions made before launch (what the permissions model looks like, how self-hosting actually works, what “per instance” licensing means in practice) are exactly the things worth being transparent about before asking anyone to commit to them.
The Insights section on this site covers the reasoning behind those decisions in depth. This blog is the shorter, more frequent companion to it — progress, scope, and the occasional change of plan.
What you’ll actually find here
- Scope updates. What’s going into the first release, and — just as importantly — what’s being deliberately left out of it.
- Release planning. Realistic timing as we have it, not optimistic guesses.
- The occasional reversal. If something we planned turns out to be the wrong call, that’s worth a post too, not just the things that went right.
What you won’t find here
Announcements that NodaBroker is “live” before it actually is. If a post on this blog ever says a feature is available, it means it’s available — not planned, not “coming soon,” not in a private beta somewhere. Until that’s true, the banner at the top of this site stays up.