Blog
Engineering, product, and public-sector notes on the DevOps execution layer.
The contract size a vendor wants and the reason a customer pays are two separate explanations. Working through a hypothetical ROI calculation to the end shows why counting only the hours saved per deployment falls short, and which items belong in the same table.
John Baek
Complaints about a familiar tool are easy to hear. But a complaint is not the same as a buying problem. What one conversation taught me about separating the friction a customer mentions from the problem their organization actually has to solve, and the four questions to ask instead.
John Baek
Issues, repositories, reviews, CI/CD, docs, AI. Every new feature made the product description longer, but not the reason to choose it today. So we changed the question: what decision can the customer not make right now? Why Change sits at the center of CollabOps.
John Baek
Adding one more criterion to the post about building every connector and still recommending migration. Do not make the structure that feels natural to the vendor the starting point for the customer. Ask for the outcome they want and the smallest change that delivers it, then do the engineering that integration actually requires.
John Baek
Organizations evaluating an SCM replacement ask two things. Does it handle deployment beyond version control, and where does it install — we run UNIX. On what it means for repository, change requests, pipelines, and deployment to live on one plane, and an honest answer to the UNIX question.
John Baek
Every adoption meeting asks whether we integrate with GitLab, SVN, and Jenkins. We do. And we still recommend migrating. On what integration can move, what it can't, and when integration genuinely is the right answer.
John Baek
Q2's four major releases (AI Agent GA, Integration Marketplace beta, OpenShift Operator, FIPS-validated builds) + 12 minor changes summarized.
John Baek
A GUI demo takes *5–10 minutes*. A CLI tour takes *30 seconds*. The CLI is the fastest way to convey our product's mental model.
John Baek
For the first nine months we *explicitly refused* to build an integration marketplace. At month twelve we reversed the decision. The four variables behind it.
John Baek
Seven enterprise tools compared on their on-prem deployment models. What each *assumes*, who each *excludes*, and why CollabOps started from a *different assumption*.
John Baek
Every modern B2B is *SaaS first*. We're *self-hosted first*. The four reasons — and the *paradoxical growth effect* of this choice.
John Baek
CollabOps AI Agent went GA after *eight months of beta*. The four launch holds we made and why each was cheaper than launching.
John Baek
Not an integration dashboard, not a workflow engine. What it means for state, authority, and execution to live on the same plane.
John Baek
Four months of redesigning permissions from policies fragmented across tools to a single graph. Why RBAC fell short, why ABAC wasn't the answer, and why graph-based delegation was load-bearing.
John Baek
