Nitric Framework / Use cases

Internal Developer Platform (IDP)

When a team grows beyond a handful of developers, consistency, structure and boundaries play an integral part of keeping applications and teams healthy. This growth should not come at the cost of developer productivity.

Free developers to innovate and build amazing applications, with operational governance to consistently and reliably scales to meet customer demand.

Why develop an IDP?

An IDP enables developer self-service & lowers cognitive load by automating repetitive activities, providing a non-restrictive set of tools for development and following best practices and guardrails set by team leadership.

The right tools for the job

Improve team productivity and velocity.

Build safe, scalable apps

Implement and enforce guardrails for consistent, maintainable infrastructure.

Minimize team friction

Developers and Ops work together in parallel to deliver amazing applications.

Add Nitric to your IDP

The Nitric Framework is extensible, giving developers the ability to self-service their application infrastructure requirements. It also gives platform engineers the ability to implement consistent technologies, configuration and policies to maintain compliance.

Developer self-service

Delight developers with a rich DX that empowers immediate provisioning of resources for any environment (local - prod) directly from code.

Reliable infrastructure

Implement providers that provision resources, policies, permissions. Deliver secure and ready to scale infrastructure according to your guardrails.

Consistent and Portable

Centralize infrastructure provisioning, eliminate boilerplate & copy-paste projects. Easily port or upgrade your infrastructure without changing application code.

Teams work in parallel

Technology leaders define the guardrails

Technology leaders define innovation concepts, guardrail definitions and make technology choices in parallel with developers and operations.

Diagram showing leadership priorities for platform development

Developers request resources and skip the boilerplate

Diagram showing developer priorities for platform development

Nitric automatically infers that the application requires:

  • Storage bucket with read permissions
  • Container which encapsulates the function handler
  • API with HTTP GET method exposing the function on path "/pictures/:filename"

Platform engineers implement providers to fulfill requests

Cloud providers manage policies and permissions in different ways, Nitric lets you implement providers to provision infrastructure tailored to your cloud needs playing the role of the glue which connects developer self-service requests to concrete infrastructure. Extend or implement your own providers using any IaC technology such as Terraform, AWS CDK, Pulumi and Crossplane.

Diagram showing operations priorities for platform development