Nitric

Writing an API and a bucket usually means writing the application, then writing the Terraform that provisions it. Nitric reads the requirements straight out of your code. Declare a bucket, say what you need to do with it, and the deployment, configuration and IAM permissions follow.

SDKs exist for JavaScript, TypeScript, Python, Go and Dart. From the same source, Nitric generates Pulumi or Terraform and deploys to AWS, GCP or Azure, with custom providers covering anything else. Under ten lines of code is enough to stand up an API endpoint and a bucket with permissions already wired.

The framework leans on a handful of ideas.

• Infrastructure from code: resource requirements are inferred from the application rather than declared separately.
• Portability: changing service, IaC tool or cloud provider does not change the application code.
• Common resources: databases, queues, topics, APIs, key-value stores and buckets are first-class.
• IAM for humans: least privilege permissions are generated from what the code says it needs.
• Local development: projects run locally behind a dashboard before anything is deployed.
• Escape hatches: the abstraction builds on the underlying layers instead of hiding them, so custom work stays possible.

Installation comes through Homebrew on macOS, a shell script on Linux or Scoop on Windows. From there nitric new scaffolds a project and nitric up deploys it. It suits teams who want to settle the application architecture first and keep the deployment target an open question afterwards.