runninginproduction.com

What It Is

Running in Production is a podcast and interview site for developers, with a very clear focus: learning how other teams run web frameworks and technology stacks in production. It is not a traditional developer tool like an IDE, CI/CD platform, or monitoring service; it is closer to a “library of production practice case studies.” The site lists 100+ podcast episodes and several interviews, centered on technology choices, why those choices were made, and lessons learned after launch.

Core Content and Technology Coverage

The site’s biggest strength is its rich set of technology tags. The content includes frameworks and languages such as Rails, Django, Flask, Phoenix, Express, Koa, FastAPI, Laravel, Meteor, Jupyter, Golang, Python, Ruby, Node, and .NET Core, as well as common production components such as Docker, Postgres, Redis, AWS, Cloudflare, Sentry, Stripe, GitHub Actions, Kubernetes, and Nginx. For teams evaluating technology options, filtering real-world cases by tag is much closer to engineering reality than reading generic framework introductions.

Pricing, API, and Self-Hosting

The captured content does not show any paid subscription, pricing page, payment methods, or information about Running in Production’s own API, SDK, or self-hosting options. As such, it should not be viewed as a SaaS tool that can be integrated into an engineering workflow. That said, the site does include many case studies about API products, self-hosted sites, cloud deployments, and monitoring systems, which can serve as indirect references.

Pros and Cons

Its main advantage is that the content focuses on production environments, filling in the kind of “how it actually runs and why it was done this way” experience that official documentation often lacks. The detailed tagging system also makes it easy to search by tech stack. The drawbacks are also clear: it is mainly an English-language podcast and interview resource, which may be a barrier for Chinese developers; the quality and depth vary depending on each guest; and it lacks a standardized, handbook-style format. For teams looking to directly purchase, deploy, or integrate a tool, it does not provide executable functionality.

Who It’s For and Access from China

It is suitable for backend engineers, full-stack developers, architects, indie developers, and technical leads who want to research how frameworks are used in real-world businesses. The captured content does not provide information about access from China, so actual testing is required; there is also no payment information. For alternatives, consider Changelog, Software Engineering Daily, Real Python Podcast, or production-practice articles from individual technical communities. Overall, it is weak as a tool, but highly valuable as a resource for technology selection and learning from production experience.