Wispr Flow: Dictation That Works EverywhereStop typing. Start speaking. 4x faster.
Promoted
GCP Architecture Tools
Pick the right GCP compute, database & IAM — free, no signup
8 followers
Pick the right GCP compute, database & IAM — free, no signup
8 followers
Three free, client-side tools for Google Cloud decisions: • Compute Selector — Cloud Run vs GKE vs Functions • Database Selector — Cloud SQL vs AlloyDB vs Spanner vs BigQuery • IAM Checker — spot public access & over-broad roles Answer a few questions, get a recommendation with the reasoning — and when NOT to use it. 100% in-browser, no sign-up, no ads.
How does it stay current when Google rolls out new SKUs or pricing changes so often? Is there a public repo or roadmap you can point to?
@mcahitbh9l It’s a decision helper, not a live pricing or SKU tracker. It doesn’t pull any private data or connect to a user’s GCP account. Everything runs client-side in the browser, and the logic is based on current GCP documentation and practical architecture tradeoffs.
How current are the recommendations, since GCP keeps rolling out new instance types and pricing changes pretty often? Does it pull live data or is it based on a snapshot you maintain?
@yavuzaliolceop It’s based on the latest GCP documentation and kept up to date manually. I’m active in the Google Cloud community and follow GCP updates closely, so I update the logic when services, recommendations, or important tradeoffs change.
How does the IAM Checker actually scan existing project policies without any login or API access?
@nurten327711 It doesn’t scan your live GCP project directly. There is a gcloud command in the tool that exports the IAM policy as JSON. You run it yourself, then paste the JSON into the checker. The analysis happens locally in the browser — no login, no OAuth, no API access, and nothing is sent to a backend.
ran the IAM checker on a test project and it actually flagged a storage bucket i had forgotten was public, so that part feels genuinely useful. love that nothing leaves the browser either.
@sude1363931 Thank you so much for the feedback. I really appreciate it.
ran the compute selector on a side project and the recommendation actually matched what I'd been arguing for internally. love that it tells you when not to use a service too, feels honest.
@melahatt6ma Thanks, glad it helped. I wanted the tool to be honest about when a service is a bad fit too.