berglas — A tool for managing secrets on Google Cloud. Listed under Access control and secrets in the Security / Governance layer. 2 of 8 comparison attributes are recorded, each with the page it was read from.
Securely store API keys, passwords, certificates, and other sensitive data with Google Cloud’s Secret Manager.
4 OF 4 SIGNALS HELD
What it runs on, and what runs on it
0 cited edgesComputed from the stack graph, both directions. Every cited edge links the page it was read from; a vendor-added one links the vendor’s own source — this is the reason to be here rather than on the vendor’s own site.
No edges on record for berglas.
Nothing in the directory documents depending on it, and its own docs do not name what it runs on. An edge is only stored when a source states it.
Submit a documented integration →From GoogleCloudPlatform? No claim is needed for this: a link to your docs that names what berglas runs on is enough.
Open-source signals
A HOLLOW RING IS UNMEASURED, NOT ZERO · WE DO NOT SUBSTITUTE A PARENT COMPANY’S REPOSITORY FOR A PRODUCT THAT HAS NONE
Price
We hold no price for this product.
The seller publishes a pricing page, linked above, but we read no rate from it. Either it quotes by sales call rather than in public, or the last reading passed 21 days and was hidden rather than shown stale. If that changes — or if you publish /.well-known/pricing.json — it appears here with a capture date.
How we read prices →What its categories ask
2 answered · 6 unanswered8 questions declared by Access control and secrets. Most rows across the directory read like these.
“With Cloud Audit Logs integration, every interaction with Secret Manager generates an audit log.”2026-10-06
A ROW WITH NO ANSWER IS NOT A ROW WITH A “NO” · A VENDOR MAY ANSWER A BLANK ONE, MARKED VENDOR CLAIMED WITH ITS SOURCE · A DOCUMENTED VALUE IS DISPUTED, NOT OVERWRITTEN, AND STAYS VISIBLE WHILE WE RE-READ THE SOURCE
Practitioner reviews
Nobody has written one yet.
A review here is structured, not a star: hardware, scale band, what broke in production, and whether you would choose it again.
NO PERCENTAGE IS SHOWN UNDER FIVE REVIEWS · NO STAR RATINGS, EVER
Also in this category
25 products in Access control and secrets. Comparison defaults to within the category — pairing this with a GPU cloud would produce a page that means nothing.
USED BY = LISTED PRODUCTS DEPENDING ON IT, IN THIS DIRECTORY
Frequently asked
Is berglas open source?
Does berglas offer audit log?
Does berglas offer secrets management?
What does a blank mean on the berglas page?
Where do the berglas figures come from?
Can berglas change what this page says?
Something here is wrong — how do I fix it?
Is this listing run by GoogleCloudPlatform?
Cite this page
A model that quotes us should quote us correctly. The reading and its date sit inside the citation rather than beside it, because a quotation carrying only a URL goes wrong the week the URL changes.
infratoapp, “berglas — Access control and secrets”, read 6 October 2026. Audit log: Yes as published at cloud.google.com. https://www.infratoapp.com/products/berglas
What berglas can and cannot change here
Claiming GoogleCloudPlatform lets its admins and editors change the tagline, description, logo, docs link and deployment model of every product that org owns — live, labelled as theirs, and logged. Answers to blank questions and dependencies go live too, marked as the owner’s and sourced; a documented answer cannot be overwritten. Everything else on this page is a stated fact with a dispute route: price, licence and OSS figures. Those columns are ungranted at the database level, so they are not a feature we withheld — they are a write that cannot happen. Name, category, website, pricing page and package names can be changed by the owner only through our review. A dispute never deletes a value; it marks it and publishes the correction.