A History of CMDBs
Traditional CMDBs failed in the cloud era. Cloud CMDBs are different: real-time, API-driven, and built for modern infrastructure. Here's why.
Chris Reuter •
Traditional CMDBs failed in the cloud era. Cloud CMDBs are different: real-time, API-driven, and built for modern infrastructure. Here's why.
Chris Reuter •
Learn how Reddit leverages CloudQuery to build a scalable, multi-cloud asset inventory that powers their security and compliance efforts across AWS, GCP, and more.
Chris Reuter •
Cloud governance fails when teams lack the right mix of skills. Learn which 6 core roles prevent chaos, their responsibilities, and how to structure your team effectively.
Adam Cobb •
Find all internet-facing cloud resources across AWS, Azure, and GCP with SQL queries. Identify exposed VMs, storage, databases, and load balancers to reduce your attack surface.
Adam Cobb •
Cloud CMDB best practices for multi-account environments - automated discovery, tiered sync strategies, SQL-based querying, and historical data retention for compliance.
Joe Karlsson •
CloudQuery Platform RBAC: Control cloud asset access with SQL-based permissions. Map Azure AD/Okta groups to roles. Available now on all environments.
Joe Karlsson •
Agent-based CMDB discovery fails in cloud environments with containers, serverless, and managed services. API-driven discovery costs 90% less and works everywhere.
Joe Karlsson •
Traditional CMDBs miss most ephemeral resources because containers live just minutes. Modern cloud CMDBs use tiered sync strategies (15-30 min for critical, hourly for important, daily for baseline). Compare approaches, costs, and learn why ephemeral infrastructure killed traditional discovery.
Joe Karlsson •
Find out how CloudQuery can help you get clarity from a chaotic cloud environment with a personalized conversation and demo.
We use tracking cookies to understand how you use the product and help us improve it. Please accept cookies to help us improve. You can always opt out later via the link in the footer.