Resource Repository
The Nerdy Field Manual for cloud, FinOps, AI, and platform engineering tools — curated with operator notes, stack recipes, and practical next steps.
The Nerdy Ecosystem
Your go-to resources, tools, and content from the Talk Nerdy to Me universe.
Talk Nerdy Playbooks Hub
Automation scripts, Terraform modules & FinOps playbooks.
CloudCostChefs.com
FinOps dashboards, cost recipes & scripts for cloud optimization.
NerdyChefs.ai
AI prompt packs & agentic workflows for automation & cloud governance.
Cloud Element Map
LEGO for your infrastructure—snap together the pieces you need.
Follow on X
Daily Cloud, FinOps & Automation insights from @talknerdyto_me.
Diner Specials
Opinionated picks for teams making decisions right now. These are not just popular links. They are high-leverage starting points with clear tradeoffs.
Platform Portal Starting Point (Not the Finish Line)
Backstage
Platform engineering is mainstream, but many teams still confuse a portal launch with a platform strategy. Backstage is a start, not the whole system.
Best for: Teams creating a developer portal foundation
Avoid if: You have no platform owner or service catalog discipline
Nerdy Operator Note
A polished portal without golden paths becomes a very pretty internal wiki.
Also on the menu
AI Coding Guardrails, Not Vibes
Cognitive Debt Prevention Kit
Teams are adopting AI coding tools faster than they are adapting review and ownership practices. This closes that gap with templates you can pilot immediately.
Best for: Engineering managers and tech leads rolling out AI coding to real teams
The right outcome is not more AI usage. It is faster delivery without mystery code.
Kubernetes Cost Visibility Without Lock-In Panic
OpenCost
Kubernetes cost allocation is still a major blind spot. OpenCost is the best way to learn the problem before committing to a commercial reporting stack.
Best for: Platform teams with enough bandwidth to operate OSS tooling
Start with visibility. Do not attempt chargeback before labeling discipline exists.
From FinOps Dashboards to Action
Cloud Custodian
Many teams have visibility but still rely on manual cleanup and spreadsheets. Cloud Custodian is where governance starts becoming enforceable.
Best for: Teams with clear policies and an owner for automation
Policy engines amplify clarity. They also amplify confusion if you encode messy rules.
Stack Recipes
Curated bundles by job-to-be-done. Use these when you need a working starting stack, not just a list of tools.
AI Coding Guardrails Starter Stack
Adopt AI coding tools without losing codebase comprehension or review quality.
Who it's for: Engineering managers, tech leads, platform/devex teams
Outcome: A lightweight but enforceable workflow for AI-assisted coding: review gates, handoff discipline, and measurable guardrails.
Why this combo works: This stack balances primary-source docs with practical internal playbooks and observability mindset. It optimizes for team behavior change, not tool hype.
Tradeoffs
- Adds a small amount of review friction at first
- Requires team discipline to keep templates useful instead of bureaucratic
- Does not solve model quality issues by itself
Companion Paths
Recipe Ingredients
Rollout templates, review gates, and team operating patterns
AI coding workflow context and team enablement guidance
Primary source capabilities and constraints
Multi-model architecture reference and comparison input
Instrumentation mindset for validating AI-assisted changes in production
Platform Engineering v1 Starter Stack
Build a platform team foundation without confusing a portal launch for a platform strategy.
Who it's for: Platform teams moving from ad hoc enablement to productized internal services
Outcome: A practical starting stack for self-service foundations, policy, and telemetry that can evolve with team maturity.
Why this combo works: It intentionally combines a portal, orchestration option, policy engine, and telemetry foundation so teams avoid optimizing only one layer.
Tradeoffs
- Needs clear platform ownership and service onboarding discipline
- Tooling alone will not create golden paths
- Policy and telemetry require operational maintenance
Recipe Ingredients
Developer portal foundation and service catalog experience
Reference option for orchestration beyond portal-only approaches
Policy enforcement across platform workflows
Observability baseline for platform reliability and adoption signals
Practitioner patterns and implementation tradeoffs
Kubernetes Cost Visibility Stack
Get honest answers to “which team is spending what?” before finance asks harder questions.
Who it's for: Platform teams, SRE teams, FinOps teams supporting Kubernetes estates
Outcome: A staged path from raw Kubernetes cost visibility to stakeholder-ready reporting and infrastructure cost review in CI.
Why this combo works: It separates problem discovery (OpenCost), stakeholder reporting (Kubecost), and shift-left cost awareness (Infracost) instead of forcing one tool to do everything.
Tradeoffs
- You still need labels/tags and ownership conventions
- Running OSS tooling adds operational overhead
- Commercial tooling improves reporting but does not fix governance gaps
Recipe Ingredients
Open-source cost allocation baseline and learning tool
Stakeholder-ready Kubernetes cost dashboards and allocation views
PR-time cost feedback for Terraform changes
Operating model for ownership and decision-making
Multi-Cloud FinOps Baseline Stack
Visibility + tagging + commitment analysis: the minimum stack for serious multi-cloud cost management.
Who it's for: FinOps leads, cloud platform teams, engineering leaders with Azure/OCI/AWS/GCP estates
Outcome: A practical baseline for reporting, tagging discipline, and commitment optimization across providers.
Why this combo works: It combines program framework, internal implementation playbooks, and policy automation references so teams can move from dashboards to action.
Tradeoffs
- Requires consistent tagging and ownership standards
- Multi-cloud reporting always takes integration work
- Optimization decisions are only as good as utilization data quality
Recipe Ingredients
Operating model and maturity guidance
Metadata discipline and enforcement patterns
Cross-cloud cost visibility and reporting
Commitment optimization and purchase decision support
Policy automation for governance and cost controls
Decision Matrices
OpenCost vs Kubecost (Which K8s Cost Path Fits Your Team?)
Question: Do you need to learn the cost-allocation problem, or do you need stakeholder-ready reporting right now?
Both tools can be excellent. The right choice depends less on features and more on your team capacity, reporting urgency, and operational maturity.
| Option | Best For | Setup | Feature Depth | Ops Tax | Cost |
|---|---|---|---|---|---|
OpenCost | Platform teams with OSS capacity and a learning-first approach | Medium | Medium | Medium | Free |
Kubecost | Teams needing polished dashboards and faster stakeholder visibility | Low | High | Medium | Paid |
OpenCost Operator Verdict
Best first step if you need cost allocation literacy and want low lock-in. Plan for operational ownership.
Kubecost Operator Verdict
Best when speed-to-reporting matters more than OSS purity. Still requires labeling and ownership discipline.
Quick Heuristics
- Start with OpenCost if your platform team will actually operate and learn from it.
- Choose Kubecost if leadership needs reliable K8s cost reporting quickly and you can budget for it.
- Either way, fix labels/ownership first or your allocation data will be hard to trust.
Backstage vs Humanitec vs DIY (Which Platform Path Fits Your Stage?)
Question: Are you solving a portal problem, an orchestration problem, or a platform product maturity problem?
Most teams do not need the same platform stack at the same time. Choose based on your current bottleneck: discoverability, orchestration, or platform product discipline.
| Option | Best For | Setup | Feature Depth | Ops Tax | Cost |
|---|---|---|---|---|---|
Backstage | Teams building a developer portal foundation and service catalog experience | Medium | Medium | Medium | Build Cost |
Humanitec | Teams past the portal phase that need orchestration and self-service standardization | Medium | High | Medium | Paid |
DIY Platform | Teams with strong platform engineering depth and highly specific internal constraints | High | High | High | Build Cost |
Backstage Operator Verdict
Excellent front door for platform engineering. Pair it with real golden paths and ownership or it becomes a fancy internal wiki.
Humanitec Operator Verdict
Strong when your bottleneck is orchestration discipline, not portal UX. Best with a platform team that already knows its product model.
DIY Platform Operator Verdict
Only worth it when your needs are truly unique and you can fund long-term maintenance. DIY is a product commitment, not a sprint project.
Quick Heuristics
- Start with Backstage if your main problem is discoverability and service catalog access.
- Evaluate Humanitec when self-service orchestration and standardization become the bottleneck.
- Choose DIY only if you have strong platform product ownership and a clear reason not to assemble from proven components.
How We Curate
What Makes The Menu
Operator-first, not directory-first
Every resource on this page is here because it solves a real problem in cloud, FinOps, AI engineering, or platform operations, not because it is popular on social media.
Opinionated by design
We include best-fit guidance, anti-fit signals, and operator notes so teams can make better decisions faster.
Action paths over link dumps
Resources should connect to practical next steps: playbooks, templates, and implementation guides.
Reviewed and re-validated
Fast-moving AI and platform tools get a last-reviewed date to keep recommendations trustworthy.
Legend & Scoring
Status Labels
Battle-Tested
Reliable pick with clear use cases and repeatable operational value.
Worth Watching
Promising or situationally strong, but needs a tighter team/problem fit.
Score Dimensions
These scores are operator heuristics, not vendor rankings. The right tool depends on your team maturity, not just feature lists.
AI & Agent Development
Build AI-assisted engineering workflows with the right mix of docs, guardrails, and practical playbooks.
Practical rollout kit for teams adopting AI coding tools without losing codebase comprehension. Includes PR gates, handoff templates, and measurable guardrails.
Field Notes, Fit & LinksShowHide
Why it's here: This is the fastest path from cognitive debt awareness to team behavior change.
Best For
Teams introducing AI coding tools across multiple engineers and repos.
Avoid If
You want a generic policy memo instead of an operational rollout kit.
Nerdy Operator Note
Speed is not the metric here. Comprehension and maintainability are the metric.
Pairs Well With
Companion Playbooks & Articles
Our full breakdown of Anthropic's Claude Code: how to use it for cloud infrastructure, FinOps automation, and daily development workflows.
Field Notes, Fit & LinksShowHide
Why it's here: Strong bridge between AI tooling hype and real engineering workflows.
Best For
Teams evaluating agentic coding workflows and needing an implementation-oriented overview.
Avoid If
You need product comparison benchmarks more than hands-on workflow guidance.
Nerdy Operator Note
Great for rapid prototyping and repo tasks, but teams need guardrails before they scale usage.
Pairs Well With
Companion Playbooks & Articles
Extend Claude Code with reusable skills for cloud governance, FinOps checks, and team-specific workflows.
Field Notes, Fit & LinksShowHide
Why it's here: Skills are where AI usage becomes scalable team infrastructure instead of ad hoc prompting.
Best For
Teams standardizing repeated AI tasks and embedding domain-specific prompts/templates.
Avoid If
You have not yet defined repeatable engineering workflows worth codifying.
Nerdy Operator Note
The win is not more prompts. The win is fewer repeated mistakes across engineers.
Pairs Well With
Companion Playbooks & Articles
Official reference for Claude models and Claude Code. Essential reading before building Claude-powered workflows or internal standards.
Field Notes, Fit & LinksShowHide
Why it's here: Primary source docs reduce rumor-driven architecture decisions.
Best For
Teams standardizing Claude usage and needing canonical product behavior and constraints.
Avoid If
You need opinionated implementation guidance more than product documentation.
Nerdy Operator Note
Use the docs for constraints and capabilities. Use playbooks for rollout decisions.
Pairs Well With
Companion Playbooks & Articles
Reference for teams using GPT models or Azure OpenAI. Useful for model capabilities, API patterns, and multi-model architecture comparisons.
Field Notes, Fit & LinksShowHide
Why it's here: Critical primary source when comparing model orchestration or avoiding single-vendor assumptions.
Best For
Teams designing multi-model strategies or comparing provider capabilities and integration patterns.
Avoid If
You need provider-neutral decision frameworks without product-specific details.
Nerdy Operator Note
Useful for capability truth. Not a substitute for internal model routing policy and evaluation.
Pairs Well With
Companion Playbooks & Articles
Framework for building custom AI agent workflows and orchestration. Useful when simple coding-assistant workflows are not enough.
Field Notes, Fit & LinksShowHide
Why it's here: It becomes relevant exactly when teams outgrow single-tool agent workflows.
Best For
Teams building custom multi-step agent workflows with real orchestration needs.
Avoid If
You just need an AI coding assistant and have no orchestration requirement.
Nerdy Operator Note
Powerful, but make sure you have a workflow problem before you buy a framework solution.
Pairs Well With
Companion Playbooks & Articles
Platform Engineering
Developer portals, orchestration platforms, and community references for building self-service infrastructure that actually works.
Spotify's open-source developer portal framework. The default starting point for internal developer platforms.
Field Notes, Fit & LinksShowHide
Why it's here: It is the fastest way to get a portal foundation without inventing your own front door.
Best For
Teams building an internal developer portal with multiple service teams and plugin needs.
Avoid If
You only need a simple deployment dashboard and do not have platform ownership capacity.
Nerdy Operator Note
Backstage is a great front door. It is not the whole house.
Companion Playbooks & Articles
Cloud-agnostic orchestration for golden paths and self-service environments when portal-only approaches hit scale limits.
Field Notes, Fit & LinksShowHide
Why it's here: Useful reference for the "portal + orchestration" maturity jump most teams eventually face.
Best For
Platform teams that have portal adoption but need orchestration, standardization, and environment automation at scale.
Avoid If
You are still proving platform-team value and do not yet have clear platform product workflows.
Nerdy Operator Note
Strong when your bottleneck is orchestration discipline, not portal UI polish.
Pairs Well With
Companion Playbooks & Articles
Practitioner-led community and knowledge base with real implementation patterns and hard-won lessons.
Field Notes, Fit & LinksShowHide
Why it's here: Cuts through vendor messaging by surfacing practitioner tradeoffs.
Best For
Teams wanting practical patterns and peer advice before overcommitting to tooling.
Avoid If
You need step-by-step implementation artifacts rather than community discussion and references.
Nerdy Operator Note
Excellent place to calibrate your roadmap before buying your way into complexity.
Pairs Well With
Companion Playbooks & Articles
Microsoft guidance and best practices for platform engineering, especially useful for Azure-heavy organizations.
Field Notes, Fit & LinksShowHide
Why it's here: Good baseline reference when introducing platform engineering to leadership or Azure teams.
Best For
Azure-heavy teams that want vendor-backed patterns and platform engineering terminology alignment.
Avoid If
You are looking for cloud-neutral implementation depth with open-source examples only.
Nerdy Operator Note
Useful for alignment and language. Pair with community/operator guidance for the real implementation edges.
Pairs Well With
Companion Playbooks & Articles
FinOps & Cost Tools
Tools and playbooks that help you see spend clearly, allocate it honestly, and act on it fast.
Industry-standard operating model for cloud financial management. Start here before building dashboards and automations.
Field Notes, Fit & LinksShowHide
Why it's here: Framework-first thinking prevents teams from confusing tooling with FinOps practice maturity.
Best For
Teams building or rebooting a FinOps practice and needing shared terminology and maturity stages.
Avoid If
You need immediate implementation artifacts rather than a framework and operating model.
Nerdy Operator Note
Use this to structure the program. Use your playbooks to do the work.
Companion Playbooks & Articles
Cloud cost estimates in Terraform pull requests. Excellent for shifting FinOps left before infra changes deploy.
Field Notes, Fit & LinksShowHide
Why it's here: One of the clearest examples of a FinOps tool that changes behavior upstream.
Best For
Terraform-heavy teams wanting PR-time cost visibility and developer feedback loops.
Avoid If
Your biggest cost problem is untagged runtime spend and no ownership model.
Nerdy Operator Note
Great for PR hygiene. It does not replace runtime cost governance.
Pairs Well With
Companion Playbooks & Articles
Kubernetes cost visibility and allocation with stakeholder-friendly views and rich reporting features.
Field Notes, Fit & LinksShowHide
Why it's here: Fastest path to stakeholder-ready K8s cost visibility for many teams.
Best For
Teams that need polished Kubernetes cost reporting fast and can support a paid tool.
Avoid If
You lack the operational bandwidth to manage Kubernetes observability and cost attribution hygiene.
Nerdy Operator Note
Fast time-to-value if you need dashboards now. Still requires labeling discipline to trust allocation.
Pairs Well With
Companion Playbooks & Articles
CNCF-backed open-source cost monitoring for Kubernetes. Great for teams that want control and understand the operational tradeoffs.
Field Notes, Fit & LinksShowHide
Why it's here: Best first step for teams learning the K8s cost allocation problem without immediate vendor lock-in.
Best For
Kubernetes teams with enough platform capacity to operate open-source cost tooling.
Avoid If
You need executive-ready cost reporting tomorrow with minimal setup effort.
Nerdy Operator Note
Perfect for learning the problem. Not always the easiest way to run the solution.
Pairs Well With
Companion Playbooks & Articles
Policy-as-code engine for governance, cost, and compliance automation across cloud providers.
Field Notes, Fit & LinksShowHide
Why it's here: It moves teams from cost visibility to cost action with policy automation.
Best For
Teams ready to automate cost and governance guardrails beyond dashboards and manual reviews.
Avoid If
You do not yet have clear policies to encode or no operational owner for enforcement.
Nerdy Operator Note
Powerful, but only after your team agrees on the policies you actually want enforced.
Companion Playbooks & Articles
Multi-cloud commitment coverage analysis playbook for Azure, AWS, GCP, and OCI with practical scripts and decision framing.
Field Notes, Fit & LinksShowHide
Why it's here: This is one of the highest-ROI FinOps motions and a strong differentiator in the site catalog.
Best For
Teams looking for a high-impact FinOps optimization workflow beyond dashboarding.
Avoid If
Your spend data and tagging are not reliable enough to act on commitment recommendations.
Nerdy Operator Note
Optimization without trustworthy utilization and ownership data becomes spreadsheet theater quickly.
Pairs Well With
Companion Playbooks & Articles
Step-by-step guide to building a practical cost dashboard with Azure Cost Management, OCI data, and Power BI.
Field Notes, Fit & LinksShowHide
Why it's here: High-leverage visibility layer that helps teams align on reality before optimization debates.
Best For
Teams establishing visibility and shared reporting before deeper optimization automation.
Avoid If
You expect dashboards alone to fix ownership, tagging, or governance discipline.
Nerdy Operator Note
Dashboards are a communication tool. Governance and remediation still need operational muscle.
Pairs Well With
Companion Playbooks & Articles
Practical tagging schema, enforcement patterns, and automation guidance for Azure, OCI, AWS, and Terraform workflows.
Field Notes, Fit & LinksShowHide
Why it's here: Tagging is the hidden dependency for almost every serious FinOps or cloud governance workflow.
Best For
Teams whose cost reporting and governance efforts keep failing because metadata discipline is weak.
Avoid If
You are not ready to standardize ownership, environment, and cost-center definitions.
Nerdy Operator Note
Optimization without tagging is theater. Start here if your reports cause arguments.
Pairs Well With
Companion Playbooks & Articles
Infrastructure & Observability
IaC, policy, and observability tools for platform teams building production-grade systems with fewer surprises.
Playbook and Python script for generating Terraform cost reports and sharing estimates with stakeholders before deployment.
Field Notes, Fit & LinksShowHide
Why it's here: Good bridge between Terraform workflows and FinOps behavior change.
Best For
Terraform teams that need cost reporting workflows without waiting for a larger FinOps platform rollout.
Avoid If
You need cloud-runtime cost visibility more than plan-time cost estimation.
Nerdy Operator Note
Useful when you need visible cost discipline in IaC workflows before full FinOps maturity.
Pairs Well With
Companion Playbooks & Articles
Infrastructure as code using general-purpose languages (TypeScript, Python, Go, C#). Strong option when HCL becomes a team-fit issue.
Field Notes, Fit & LinksShowHide
Why it's here: Important alternative when Terraform is a poor fit for the team, not because of hype.
Best For
Teams that want to use general-purpose languages for infra and have strong software engineering practices.
Avoid If
You need the broadest ecosystem of Terraform modules and established HCL governance patterns today.
Nerdy Operator Note
Team fit matters more than language ideology. Pick the tool your reviewers can govern well.
Pairs Well With
Companion Playbooks & Articles
Unified observability platform for metrics, logs, and traces with a strong open-source ecosystem alignment.
Field Notes, Fit & LinksShowHide
Why it's here: Solid operator-friendly option for teams moving beyond fragmented metrics/logs setups.
Best For
Teams wanting broad observability coverage with strong dashboarding and OpenTelemetry alignment.
Avoid If
You have no telemetry instrumentation plan and expect the tool alone to create observability.
Nerdy Operator Note
Strong platform, but instrumentation quality still determines whether your dashboards tell the truth.
Pairs Well With
Companion Playbooks & Articles
Vendor-neutral telemetry standard for metrics, traces, and logs. Essential to avoid observability lock-in and instrumentation drift.
Field Notes, Fit & LinksShowHide
Why it's here: It is the foundation layer for sane observability architecture decisions.
Best For
Teams building long-term observability capabilities and wanting portability across vendors.
Avoid If
You need immediate dashboards but have no capacity to instrument services correctly.
Nerdy Operator Note
Instrumentation discipline beats dashboard aesthetics every time.
Pairs Well With
Companion Playbooks & Articles
Policy engine for infrastructure, Kubernetes, APIs, and authorization. One policy language across multiple enforcement points.
Field Notes, Fit & LinksShowHide
Why it's here: OPA becomes a force multiplier once platform and security teams agree on policy boundaries.
Best For
Platform teams standardizing policy enforcement across multiple parts of the stack.
Avoid If
You do not have clear policy ownership or cannot maintain policy reviews over time.
Nerdy Operator Note
The hard part is not writing Rego. It is deciding who owns policy and how changes are governed.
Pairs Well With
Companion Playbooks & Articles
Cloud Calculators & Discovery
Planning and discovery tools for estimating costs, mapping cloud services, and understanding what you are actually running.
Estimate Azure service costs before deployment. Good for early planning, budgeting, and rough comparisons.
Field Notes, Fit & LinksShowHide
Why it's here: Useful for pre-build cost conversations, especially when paired with FinOps playbooks.
Best For
Early sizing conversations and rough pricing comparisons for Azure workloads.
Avoid If
You need production-grade cost attribution or actual spend analysis.
Nerdy Operator Note
Great for estimating directionally. Do not confuse calculator outputs with real operational spend.
Companion Playbooks & Articles
Oracle Cloud cost estimation tool, useful when comparing OCI pricing to Azure or AWS alternatives.
Field Notes, Fit & LinksShowHide
Why it's here: Helpful in multicloud evaluation workflows, especially for OCI-heavy FinOps discussions.
Best For
Teams evaluating OCI for cost-sensitive workloads or comparing cross-cloud options.
Avoid If
You need tenancy-level reporting, inventory, or operational cost analytics.
Nerdy Operator Note
Useful for pricing direction. Pair with real tenancy reporting before making commitment decisions.
Companion Playbooks & Articles
Visual Azure service reference organized by category. Great for discovery and quick architecture conversations.
Field Notes, Fit & LinksShowHide
Why it's here: Useful discovery tool that reduces Azure service sprawl confusion during planning.
Best For
Engineers exploring Azure services, educating teams, or mapping options quickly.
Avoid If
You need prescriptive architectural guidance, governance, or cost decisions.
Nerdy Operator Note
Great for mapping the landscape. You still need standards to avoid turning discovery into sprawl.
Pairs Well With
Companion Playbooks & Articles
Generate HTML and Excel reports for OCI tenancy inventory, audits, and documentation workflows.
Field Notes, Fit & LinksShowHide
Why it's here: A niche but high-value playbook that strengthens your OCI content moat.
Best For
OCI teams that need inventory visibility and audit-friendly reporting quickly.
Avoid If
You need cross-cloud inventory in one tool without OCI-specific workflows.
Nerdy Operator Note
Inventory discipline pays off in both FinOps and security audits. This is a strong shortcut for OCI shops.
Companion Playbooks & Articles