Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #7327

N

Nitric

Company blog · nitric.io/blogprogrammingweb

Nitric is the company blog at nitric.io, writing about programming and web. Since 2021, 10 different Hacker News readers have linked it 47 times, most often “Ask HN: Looking for Feedback on Website”. It is still writing: the last post was on 2025-06-11, and you can follow it by feed.

Visit the blog
47mentions?
10HN people?
2021–2026first – last linked?
Links on Hacker News per year · peak 34 in 2024

Nitric Open Source Cloud-Native Framework auto-provisions infrastructure for your app from any language for any cloud. Launch now with AWS, GCP and Azure.

Most-linked posts?

  1. Ask HN: Looking for Feedback on Website
    3 people · 4 mentions · first linked 2021-11-26
  2. Speeding up Azure development by not using Terraform
    2 people · 2 mentions · first linked 2024-02-11
  3. The Servers Behind Serverless
    2 people · 2 mentions · first linked 2024-10-09
  4. Working with Terraform Can Be Much Faster
    2 people · 2 mentions · first linked 2024-07-31
  5. Terraform from an API
    2 people · 2 mentions · first linked 2024-08-11
  6. How Much Infrastructure Code Are Your Teams Writing?
    2 people · 2 mentions · first linked 2022-09-28

What Hacker News says?

  1. 100% agree with your point on application code shaping infra, that's the standard pattern that tech like this is trying to achieve, by providing a standard by which those infrastructure requirements can be automatically understood. Fair point on the second, can I ask what you specifically mean by concrete drawings? I'd really like to understand your perspective on separation of concerns between IaC and application c…

    Comment linking /case-studies/dropbio

    on “Speeding up Azure development by not using Terraform”
  2. Submitted Speeding up Azure development by not using Terraform as a story · 76 points

    HN discussion
  3. Thanks for the insight, your last point on reducing context windows for AI is exactly what Nitric is trying to achieve for humans as well reduced cognitive complexity for 80% of the work (from your second point). I can see a path forward for Nitric as platform engineering solution where standardization of architecture is achieved (with the aid of AI as well), through building Nitric custom providers: https://nitric.…

    Comment linking /docs/reference/providers/custom/building-custom-provider

    on “Speeding up Azure development by not using Terraform”
  4. Submitted What Is Infrastructure from Code? as a story · 24 points

    HN discussion
  5. Hopefully this helps give a better idea of how it works under the hood: https://nitric.io/docs/reference/providers/custom/building-c... Not just a feature of Pulumi, its just used as the IaC of choice for the out of the box deployment providers. This can be replaced with anything. At its core Nitric is really a tool to collect infrastructure requirements from an application and those requirements are delivered to a…

    Comment linking /docs/reference/providers/custom/building-custom-provider

    on “Speeding up Azure development by not using Terraform”
  6. Submitted Using Actual Code for IaC as a story · 20 points

    HN discussion
  7. Nitric doesn't wrap the state management for Pulumi, we actually encourage integrating directly with Pulumi's own cloud offerings to manage your infrastructure state. https://nitric.io/docs/reference/pulumi Note this only applies to our OOTB providers which use Pulumi as our deployment engine of choice. When you take away our providers Nitric becomes a communication layer between your application and any deployment…

    Comment linking /docs/reference/providers/custom/building-custom-provider

    on “Speeding up Azure development by not using Terraform”
  8. Submitted Platform engineering using Terraform Modules as a story · 7 points

    HN discussion
  9. One of the co-founders of Nitric here, and I'll bite on this one :) I hear the separation of concerns between IaC and application code argument quite a bit, but always see an inherent coupling between the two. If changes to your IaC require changes to your application code for your application to continue working then where is the separation of concerns? If its just deployment and runtime, this separation still exis…

    Comment linking /docs/reference/providers/custom/building-custom-provider

    on “Speeding up Azure development by not using Terraform”
  10. Submitted Contributors to AWS Lambda container cold starts as a story · 6 points

    HN discussion
  11. Why do people do this? I skim the article. I go wait "Nitric sounds like Pulumi". A few googles later, I find this : https://nitric.io/docs/reference/pulumi So, it's fast because it uses Pulumi... Does Pulumi no longer build on Terraform providers? (EDIT: looking, it seems like many Pulumi providers are still terraform wrappers...) Either way, it feels like this is just a Pulumi feature.

    Comment linking /docs/reference/pulumi

    on “Speeding up Azure development by not using Terraform”
  12. Submitted The Servers Behind Serverless as a story · 5 points

    HN discussion
  13. You're not wrong, it's one of the most difficult parts and definitely something we're trying to solve with Nitric. Here is the overview doc about how we handle this problem https://nitric.io/docs/reference/access-control would love your feedback.

    Comment linking /docs/reference/access-control

    on “Show HN: Nitric – Node.js framework for building portable cloud apps”
  14. Submitted Show HN: Combining LLMs and Voice Models – Part 1 as a story · 4 points

    HN discussion
  15. Thanks for checking it out. We've definitely gone with a convienience first approach for the framework but realize that's not suited to every scenario. By the way, the underlying tech is written in Go and we're adding support for other languages if Node.js is a big concern https://nitric.io/docs/language-support

    Comment linking /docs/language-support

    on “Show HN: Nitric – Node.js framework for building portable cloud apps”
  16. Submitted Ask HN: Looking for Feedback on Website as a story · 4 points

    HN discussion
  17. Dapr is fantastic if you're using Kubernetes, but we've found people having trouble with the learning curve. Also, Nitric's main SDK right now is for Node.js, but the underlying implementation is in Go and uses gRPC like Dapr. We have other SDKs in the works for Go, Python, Kotlin and C#. There is a bit more detail in the docs https://nitric.io/docs/language-support

    Comment linking /docs/language-support

    on “Show HN: Nitric – Node.js framework for building portable cloud apps”
  18. Submitted Speeding up Azure development by not using Terraform as a story · 4 points

    HN discussion
  19. I did browse the docs and repos[0]. I'm saying that "IfC" as formulated here[1] is an anti-pattern and what I refer to as misguided. > IaC tools like Pulumi, Terraform, AWS CDK, Ansible and others bring repeatability to infrastructure by giving you scripts that you can use across different environments or projects to provision infrastructure. This code/config is in addition to your application code, typically with a…

    Comment linking /docs/concepts/introduction

    on “Nitric Is Terraform for Developers”
  20. Submitted The Servers Behind Serverless as a story · 3 points

    HN discussion
  21. It appears to be an abstraction on top of Pulumi/Terraform (it's clearer on their homepage, which refers to both: https://nitric.io/ ) that abstracts over the underlying cloud resources (which tend to be cloud-dependent) with higher-level concepts like "buckets" and "services".

    Comment linking /

    on “Nitric Is Terraform for Developers”
  22. Submitted Terraform from an API as a story · 3 points

    HN discussion
  23. I've had the experience of trying to build software deployable to multiple cloud providers (independent instances) so it can run in customer environments. We still needed to use serverless offerings, which was a real pain. So much so, we've been building a framework to make it easier/possible - https://nitric.io

    Comment linking /

    on “Do you use MULTI-CLOUD or HYBRID-CLOUD infra?”
  24. Submitted We built a self-provisioning runtime as a story · 3 points

    HN discussion
  25. Thanks for that, there is no pricing as it's a FOSS framework not a platform. But I get where this is coming from. Nitric currently makes money working with enterprises on cloud solutions using the framework. We do accept sponsors on github maybe that's something we could include as a pricing page? The framework is backend focused and there is OIDC configuration you can include for authenticating requests to the bac…

    Comment linking /docs/apis?lang=python

    on “a thread”
  26. Submitted Show HN: Nitric – An open-source framework for serverless apps without lock-in as a story · 3 points

    HN discussion
  27. Submitted An open source universal back end framework as a story · 2 points

    HN discussion
  28. Submitted Nitric adds Deno 2 support as a story · 2 points

    HN discussion
  29. Submitted The Fastest Cloud Development Happens Locally as a story · 2 points

    HN discussion
  30. Submitted Working with Terraform Can Be Much Faster as a story · 2 points

    HN discussion

Search all of HN for nitric.io