HashiCorp archives the Boundary open source repo
vmatsiiako
62 points
11 comments
October 12, 2026
Related Discussions
Found 5 related stories in 147.3ms across 9,162 title embeddings via pgvector HNSW
- Show HN: Kedge – Full-stack cloud with forkable VM snapshots and global SQLite wgjordan · 58 pts · July 29, 2026 · 42% similar
- RubyGems Open Source Supply Chain Security and OpenAI rietta · 45 pts · September 14, 2026 · 42% similar
- V1.1 state of open source- OS 4.4 months behind frontier [pdf] airplanesandOS · 12 pts · September 15, 2026 · 42% similar
- GitHub Has an Availability Problem. Is It Time to Look Elsewhere? dhruv3006 · 63 pts · August 17, 2026 · 42% similar
- OpenAI Forked Git on GitHub rahlokzero · 23 pts · July 11, 2026 · 41% similar
Discussion Highlights (4 comments)
hdjdnxjzhzhs
IBM archives the Boundary open source repo
sciencesama
hmm what is a good alternative to this ?
firesteelrain
I recall talking to a HashiCorp rep about Boundary and the ability to find a place for it. Still seems kind of niche. I guess it never really found its place as a CE version.
ProblemExplorer
An accurate title would be "IBM archives the IBM-HashiCorp Boundary Community Edition repo". That "HashiCorp" in the title is a farce. The "Hashi" of the HashiCorp is far gone. IBM and "Corp" are redundant. Community Editions don't make sense to the MBAs at IBM unless killing those off would create a global backlash (loss of goodwill for no positive revenue outcome is not good to an MBA. If loss of goodwill however, results in positive revenue, that's a good thing to an MBA. This is a well regarded, well studied and highly respected, revenue boosting MBA concept called "enshittification"). MBAs know that anything that doesn't directly translate into either viral growth or revenue next quarter is a waste of investor dollars. That makes anything else a risk to their own careers. Boundary is past its viral growth stage, so the MBA needs to see revenue next quarter. Boundary fails the test there, so off with it! HashiCorp was an innovative company founded by two engineers that built a lot of foundational, transformational infra products. Then, in a growth frenzy based off the traction of these tools they raised tremendous, vast sums of money and subsequently ~lost control of their vision~ hired MBAs, and the company went down the drain as well, or as MBAs call it - got acquired. What remains of those tools are a BSL that focuses on maintenance operations and feature requests that strictly ride along a highly scrutinized cost-benefit decision matrix of rent seeking behavior off IBM's contracts with organizations that had already embraced those tools. Billions of tokens have been burned in creating PPTs and Excel sheets, and emails discussing them, about why the Boundary Community Edition should be archived and abandoned.