You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@polaris.apache.org by "ZiggiZagga (via GitHub)" <gi...@apache.org> on 2025/12/25 10:49:34 UTC

Re: [D] Preventing Vendor Lock-in: Your Thoughts on IronBucket (New OSS Project) [polaris]

GitHub user ZiggiZagga added a comment to the discussion: Preventing Vendor Lock-in: Your Thoughts on IronBucket (New OSS Project)

**Why IronBucket matters now — and what comes next**

Hi,

Merry Christmas everyone!

**Object Storage Governance is becoming increasingly vendor‑controlled and increasingly fragile.**
- sudden licensing changes  
- features moving behind paywalls  
- IAM models that lock users into a single vendor  
- governance layers tightly coupled to proprietary APIs

**this creates real risks.**
- **Loss of independence** if identity and access control live inside the storage vendor  
- **Loss of trust** when governance rules are opaque or tied to closed systems  
- **Loss of portability** when applications depend on vendor‑specific IAM semantics  
- **Loss of resilience** when a project stops evolving but remains mission‑critical

**What I will do next**

To make this concrete, I’m preparing a **first binary release** of IronBucket so the community can actually run it, test it, and tell me where it breaks.

This initial release will focus on:

- a minimal but functional S3‑compatible proxy  
- OIDC‑based authentication  
- a simple policy engine  
- a quickstart environment  
- enough documentation to get people experimenting  

Open for feedback.

GitHub link: https://github.com/apache/polaris/discussions/1948#discussioncomment-15340380

----
This is an automatically sent email for issues@polaris.apache.org.
To unsubscribe, please send an email to: issues-unsubscribe@polaris.apache.org