// the find
nitrictech/nitric
Nitric is a multi-language framework for cloud applications with infrastructure from code.
Nitric is an infrastructure-from-code framework that infers cloud resources (buckets, queues, APIs, databases) from your application code and generates Pulumi or Terraform to deploy them. It targets backend developers who want to write cloud-agnostic services without hand-authoring IaC. Supports TypeScript, Python, Go, and Dart across AWS, GCP, and Azure.
The automatic IAM generation is the standout feature — declaring `.allow('read', 'write')` on a resource and having least-privilege permissions wired up automatically removes a whole class of misconfiguration bugs. The local development runtime is a genuine time-saver: you get a local dashboard and can run the full stack without cloud credentials. The plugin architecture is honest about what it is — you can swap Pulumi for Terraform or write your own provider without changing application code. The generated Terraform modules are real, inspectable HCL, not a black box you have to trust.
Under 2000 stars after what appears to be several years of development is a slow adoption signal — the 'infrastructure from code' pitch has competition from SST, Encore, and Winglang, and Nitric hasn't clearly won any of those comparisons. The abstraction leaks badly for anything non-trivial: the escape hatches exist because the resource model can't cover edge cases, and at that point you're debugging both your app and the provider plugin. Dart support looks like a footnote — it's listed but the community around it is tiny and it's unclear who the target user is. The generated CDKTF bindings in `deploytf/generated` are checked-in machine code with vendored tarballs, which makes diffs unreadable and signals maintenance overhead the team may not want.