CloudQuery
@cloudquery.bsky.social
Data pipelines for cloud config and security data. Build cloud asset inventory, CSPM, FinOps, and vulnerability management solutions. Extract from AWS, Azure, GCP, and 70+ cloud and SaaS sources.
An engineer leaves your company. Access revoked. Laptop returned.
But their commits are still across dozens of repos.
For compliance audits, you need to know: which code was authored by former employees? 🧵
But their commits are still across dozens of repos.
For compliance audits, you need to know: which code was authored by former employees? 🧵
January 15, 2026 at 3:15 PM
An engineer leaves your company. Access revoked. Laptop returned.
But their commits are still across dozens of repos.
For compliance audits, you need to know: which code was authored by former employees? 🧵
But their commits are still across dozens of repos.
For compliance audits, you need to know: which code was authored by former employees? 🧵
Your legal team asks: "Which repos don't have a LICENSE file?"
GitHub shows license status one repo at a time. The API requires pagination. Writing a script means auth, rate limits, and maintenance.
Or... one SQL query 🧵
GitHub shows license status one repo at a time. The API requires pagination. Writing a script means auth, rate limits, and maintenance.
Or... one SQL query 🧵
January 14, 2026 at 3:15 PM
Your legal team asks: "Which repos don't have a LICENSE file?"
GitHub shows license status one repo at a time. The API requires pagination. Writing a script means auth, rate limits, and maintenance.
Or... one SQL query 🧵
GitHub shows license status one repo at a time. The API requires pagination. Writing a script means auth, rate limits, and maintenance.
Or... one SQL query 🧵
Node 18 reached end-of-life in April 2025.
Quick: how many Dockerfiles across your org still use `node:18` as the base image?
If your answer is "I'd have to clone every repo and grep"... read on 🧵
Quick: how many Dockerfiles across your org still use `node:18` as the base image?
If your answer is "I'd have to clone every repo and grep"... read on 🧵
January 13, 2026 at 3:15 PM
Node 18 reached end-of-life in April 2025.
Quick: how many Dockerfiles across your org still use `node:18` as the base image?
If your answer is "I'd have to clone every repo and grep"... read on 🧵
Quick: how many Dockerfiles across your org still use `node:18` as the base image?
If your answer is "I'd have to clone every repo and grep"... read on 🧵
You need to find which Dockerfiles still use Node 18 (now EOL). The usual approach: clone 500 repos, write bash scripts, maintain it as teams change.
There's a better way 🧵
There's a better way 🧵
January 12, 2026 at 3:15 PM
You need to find which Dockerfiles still use Node 18 (now EOL). The usual approach: clone 500 repos, write bash scripts, maintain it as teams change.
There's a better way 🧵
There's a better way 🧵
Durham folks: We're hosting an informal cloud governance meetup on Jan 28.
No panels. No slides. Just drinks and honest conversations about multi-cloud visibility, guardrails, and making compliance work without slowing teams down.
5-7pm at Alley Twenty Six.
https://lu.ma/x6lhihm6
No panels. No slides. Just drinks and honest conversations about multi-cloud visibility, guardrails, and making compliance work without slowing teams down.
5-7pm at Alley Twenty Six.
https://lu.ma/x6lhihm6
January 8, 2026 at 4:58 PM
Durham folks: We're hosting an informal cloud governance meetup on Jan 28.
No panels. No slides. Just drinks and honest conversations about multi-cloud visibility, guardrails, and making compliance work without slowing teams down.
5-7pm at Alley Twenty Six.
https://lu.ma/x6lhihm6
No panels. No slides. Just drinks and honest conversations about multi-cloud visibility, guardrails, and making compliance work without slowing teams down.
5-7pm at Alley Twenty Six.
https://lu.ma/x6lhihm6
Your CMDB thinks it discovered 10,000 servers. Reality? You have 8,500.
The missing 1,500 are containers that lived for 2 minutes and Lambda functions that executed 5,000 times. 🧵
The missing 1,500 are containers that lived for 2 minutes and Lambda functions that executed 5,000 times. 🧵
December 8, 2025 at 3:15 PM
Your CMDB thinks it discovered 10,000 servers. Reality? You have 8,500.
The missing 1,500 are containers that lived for 2 minutes and Lambda functions that executed 5,000 times. 🧵
The missing 1,500 are containers that lived for 2 minutes and Lambda functions that executed 5,000 times. 🧵
We analyzed 50 traditional CMDB implementations at enterprise companies.
Average time spent per month on CMDB maintenance: 40 hours.
Average data staleness: 12-24 hours.
Success rate delivering business value: 20-30%.
Here's what breaks and why 🧵
Average time spent per month on CMDB maintenance: 40 hours.
Average data staleness: 12-24 hours.
Success rate delivering business value: 20-30%.
Here's what breaks and why 🧵
December 8, 2025 at 2:15 PM
We analyzed 50 traditional CMDB implementations at enterprise companies.
Average time spent per month on CMDB maintenance: 40 hours.
Average data staleness: 12-24 hours.
Success rate delivering business value: 20-30%.
Here's what breaks and why 🧵
Average time spent per month on CMDB maintenance: 40 hours.
Average data staleness: 12-24 hours.
Success rate delivering business value: 20-30%.
Here's what breaks and why 🧵
Most cloud asset inventory projects fail not because of technical complexity.
They fail because teams optimize for data collection instead of decision velocity.
Here's how organizations evolve from ad-hoc scripts to systems that answer questions in seconds 🧵
They fail because teams optimize for data collection instead of decision velocity.
Here's how organizations evolve from ad-hoc scripts to systems that answer questions in seconds 🧵
December 1, 2025 at 2:15 PM
Most cloud asset inventory projects fail not because of technical complexity.
They fail because teams optimize for data collection instead of decision velocity.
Here's how organizations evolve from ad-hoc scripts to systems that answer questions in seconds 🧵
They fail because teams optimize for data collection instead of decision velocity.
Here's how organizations evolve from ad-hoc scripts to systems that answer questions in seconds 🧵
Free swag. Zero hassle. 🎁
Run one CloudQuery sync. That's the whole contest.
Complete your first sync, share results, get swag. Plus learn how API-driven cloud discovery actually works.
Details: https://www.cloudquery.io/blog/death-of-agent-based-discovery
Run one CloudQuery sync. That's the whole contest.
Complete your first sync, share results, get swag. Plus learn how API-driven cloud discovery actually works.
Details: https://www.cloudquery.io/blog/death-of-agent-based-discovery
November 12, 2025 at 3:15 PM
Free swag. Zero hassle. 🎁
Run one CloudQuery sync. That's the whole contest.
Complete your first sync, share results, get swag. Plus learn how API-driven cloud discovery actually works.
Details: https://www.cloudquery.io/blog/death-of-agent-based-discovery
Run one CloudQuery sync. That's the whole contest.
Complete your first sync, share results, get swag. Plus learn how API-driven cloud discovery actually works.
Details: https://www.cloudquery.io/blog/death-of-agent-based-discovery
Want CloudQuery swag? 🎁
Run a sync. That's it.
Complete a sync, share your results, win swag. Learn API-driven cloud discovery while you're at it.
Enter here: https://www.cloudquery.io/blog/death-of-agent-based-discovery
Run a sync. That's it.
Complete a sync, share your results, win swag. Learn API-driven cloud discovery while you're at it.
Enter here: https://www.cloudquery.io/blog/death-of-agent-based-discovery
November 11, 2025 at 3:15 PM
Want CloudQuery swag? 🎁
Run a sync. That's it.
Complete a sync, share your results, win swag. Learn API-driven cloud discovery while you're at it.
Enter here: https://www.cloudquery.io/blog/death-of-agent-based-discovery
Run a sync. That's it.
Complete a sync, share your results, win swag. Learn API-driven cloud discovery while you're at it.
Enter here: https://www.cloudquery.io/blog/death-of-agent-based-discovery
We spent 20 years installing agents on servers. Then AWS gave us APIs.
Why are we still installing agents like it's 2005? 🧵
Why are we still installing agents like it's 2005? 🧵
November 10, 2025 at 3:15 PM
We spent 20 years installing agents on servers. Then AWS gave us APIs.
Why are we still installing agents like it's 2005? 🧵
Why are we still installing agents like it's 2005? 🧵
Your CMDB updates daily. Your containers live 3 minutes. Your Lambda functions live 300 milliseconds.
See the problem? 🧵
See the problem? 🧵
November 7, 2025 at 3:15 PM
Your CMDB updates daily. Your containers live 3 minutes. Your Lambda functions live 300 milliseconds.
See the problem? 🧵
See the problem? 🧵
You manage 4,782 cloud resources across 6 accounts. Can you tell me which S3 buckets are publicly accessible right now? Which IAM roles haven't been used in 90 days? 🧵
November 5, 2025 at 6:00 AM
You manage 4,782 cloud resources across 6 accounts. Can you tell me which S3 buckets are publicly accessible right now? Which IAM roles haven't been used in 90 days? 🧵
Traditional CMDBs were built for servers with names like "web-prod-01" that run for years.
In 2026, that EC2 instance running your Lambda cold start lives for 45 seconds.
Traditional CMDB discovery would schedule a scan for tomorrow. By then, it's gone. 🧵
In 2026, that EC2 instance running your Lambda cold start lives for 45 seconds.
Traditional CMDB discovery would schedule a scan for tomorrow. By then, it's gone. 🧵
November 3, 2025 at 2:15 PM
Traditional CMDBs were built for servers with names like "web-prod-01" that run for years.
In 2026, that EC2 instance running your Lambda cold start lives for 45 seconds.
Traditional CMDB discovery would schedule a scan for tomorrow. By then, it's gone. 🧵
In 2026, that EC2 instance running your Lambda cold start lives for 45 seconds.
Traditional CMDB discovery would schedule a scan for tomorrow. By then, it's gone. 🧵
Your CMDB shows 847 EC2 instances. AWS console reports 1,203 running right now.
Security needs a list of unencrypted S3 buckets in 30 minutes. Your last discovery scan ran 18 hours ago.
Traditional CMDBs fail 70-80% of the time. Here's why, and what works instead →
Security needs a list of unencrypted S3 buckets in 30 minutes. Your last discovery scan ran 18 hours ago.
Traditional CMDBs fail 70-80% of the time. Here's why, and what works instead →
November 1, 2025 at 2:00 PM
Your CMDB shows 847 EC2 instances. AWS console reports 1,203 running right now.
Security needs a list of unencrypted S3 buckets in 30 minutes. Your last discovery scan ran 18 hours ago.
Traditional CMDBs fail 70-80% of the time. Here's why, and what works instead →
Security needs a list of unencrypted S3 buckets in 30 minutes. Your last discovery scan ran 18 hours ago.
Traditional CMDBs fail 70-80% of the time. Here's why, and what works instead →
Do you know we have a referral program? If you know someone who needs better cloud data infrastructure? Send them our way and earn a $500 Visa gift card when they become a customer.
Check out the full program details:
Check out the full program details:
Introducing the CloudQuery Referral Program - Earn $500 | CloudQuery Blog
Share CloudQuery with your network and earn account credits for every successful referral. Help more teams discover the power of infrastructure data and get rewarded for spreading the word.
buff.ly
October 23, 2025 at 12:38 AM
Do you know we have a referral program? If you know someone who needs better cloud data infrastructure? Send them our way and earn a $500 Visa gift card when they become a customer.
Check out the full program details:
Check out the full program details:
We wrapped up our AWS series on cloud asset inventories with the final video—released on the official AWS YouTube channel.
Together we covered why most inventory projects fail: teams treat them as technical implementations instead of business capabilities. www.cloudquery.io/blog/five-ti...
Together we covered why most inventory projects fail: teams treat them as technical implementations instead of business capabilities. www.cloudquery.io/blog/five-ti...
October 21, 2025 at 9:06 AM
We wrapped up our AWS series on cloud asset inventories with the final video—released on the official AWS YouTube channel.
Together we covered why most inventory projects fail: teams treat them as technical implementations instead of business capabilities. www.cloudquery.io/blog/five-ti...
Together we covered why most inventory projects fail: teams treat them as technical implementations instead of business capabilities. www.cloudquery.io/blog/five-ti...
We partnered with AWS to introduce CloudQuery as a cloud visibility solution—released on the official AWS YouTube channel.
October 20, 2025 at 9:06 AM
We partnered with AWS to introduce CloudQuery as a cloud visibility solution—released on the official AWS YouTube channel.
We teamed up with AWS to break down how to design cloud asset inventories that actually work at scale—released on the official AWS YouTube channel. buff.ly/UGSdrRu
How to Design a Cloud Asset Inventory for AWS | CloudQuery Blog
Learn the five essential design principles for building cloud asset inventories that deliver results—freshness, completeness, normalization, queryability, and extensibility. Discover the maturity…
www.cloudquery.io
October 17, 2025 at 9:06 AM
We teamed up with AWS to break down how to design cloud asset inventories that actually work at scale—released on the official AWS YouTube channel. buff.ly/UGSdrRu
We teamed up with AWS to break down cloud asset inventories. What they are, why they matter, and how to build ones that actually work at scale for the official AWS YouTube channel.
Full breakdown here: buff.ly/mR3SNL3
Full breakdown here: buff.ly/mR3SNL3
What Is a Cloud Asset Inventory? (and Why It Matters) | CloudQuery Blog
Understand cloud asset inventories—centralized databases of all your cloud resources built from AWS APIs. Learn the four core pillars (discovery, relationship mapping, change tracking, querying) and…
www.cloudquery.io
October 16, 2025 at 9:06 AM
We teamed up with AWS to break down cloud asset inventories. What they are, why they matter, and how to build ones that actually work at scale for the official AWS YouTube channel.
Full breakdown here: buff.ly/mR3SNL3
Full breakdown here: buff.ly/mR3SNL3
Feeding sensitive cloud config into AI models without leaking credentials or violating compliance is harder than most teams think. We walked through detecting multi-cloud attack chains that rule-based tools miss and scaling these pipelines to 50,000+ resources in production.
CloudQuery | Webinar: Building Secure AI Pipelines for Cross-Cloud Attack Detection
Learn how to safely update your cloud security from reactive to predictive with AI-powered threat detection. In this hands-on webinar, you'll learn how to build secure AI data pipelines that analyze…
buff.ly
October 15, 2025 at 9:06 AM
Feeding sensitive cloud config into AI models without leaking credentials or violating compliance is harder than most teams think. We walked through detecting multi-cloud attack chains that rule-based tools miss and scaling these pipelines to 50,000+ resources in production.
Want to win CloudQuery swag?
We loaded AWS infrastructure data into a public Postgres database. Your job: sync it with CloudQuery, write SQL queries, find the wasteful resources. It only takes about 10 minutes:
We loaded AWS infrastructure data into a public Postgres database. Your job: sync it with CloudQuery, write SQL queries, find the wasteful resources. It only takes about 10 minutes:
Find the Cloud Waste Contest | CloudQuery Blog
Win CloudQuery swag by finding cloud waste in our dataset. Sync AWS data with CloudQuery, solve 3 SQL challenges, get t-shirts, sweatshirts, and mugs. Open to all skill levels.
www.cloudquery.io
October 14, 2025 at 9:06 AM
Want to win CloudQuery swag?
We loaded AWS infrastructure data into a public Postgres database. Your job: sync it with CloudQuery, write SQL queries, find the wasteful resources. It only takes about 10 minutes:
We loaded AWS infrastructure data into a public Postgres database. Your job: sync it with CloudQuery, write SQL queries, find the wasteful resources. It only takes about 10 minutes:
One CloudQuery customer saves $30k/month by running SQL queries to find unused GCP resources. Lucky for you, we just published the exact queries they use. 🧵
GCP Quick Wins | CloudQuery Blog
Discover unused resources costing you money in GCP using CloudQuery + Postgres.
www.cloudquery.io
October 13, 2025 at 9:06 AM
One CloudQuery customer saves $30k/month by running SQL queries to find unused GCP resources. Lucky for you, we just published the exact queries they use. 🧵
GitHub Issues semantic search just got a fully managed upgrade. We previously showed this with PostgreSQL + pgvector. Now we're scaling it with BigQuery and Vertex AI for zero operational overhead.
Scale GitHub Issues semantic search with CloudQuery, BigQuery, and Vertex AI | CloudQuery Blog
Sync GitHub issues to BigQuery with CloudQuery, generate Vertex AI embeddings via BigQuery remote models, and deliver fast, fully managed semantic search and Q&A with Gemini—no vector database to run.
www.cloudquery.io
October 10, 2025 at 9:06 AM
GitHub Issues semantic search just got a fully managed upgrade. We previously showed this with PostgreSQL + pgvector. Now we're scaling it with BigQuery and Vertex AI for zero operational overhead.
Native GitHub Issues search works for keywords, but struggles with context and synonyms. Try asking "What are users requesting around Azure?" and you'll get fragmented results that miss the bigger picture.
Improve GitHub Issues search effortlessly with CloudQuery, PgVector and OpenAI | CloudQuery Blog
Turn GitHub issues into instant insights: sync with CloudQuery, generate PgVector embeddings in PostgreSQL, and answer natural-language questions with a tiny OpenAI-powered script.
www.cloudquery.io
October 9, 2025 at 9:06 AM
Native GitHub Issues search works for keywords, but struggles with context and synonyms. Try asking "What are users requesting around Azure?" and you'll get fragmented results that miss the bigger picture.