---
title: "Orchide Irakoze SR (@orchide) | Hashnode"
description: "Orchide Irakoze SR (@orchide) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@orchide"
---

@orchide

# Orchide Irakoze SR

@orchide · Joined July 2025

### [Why Our Users Are Convinced We're the Home of NestJS Monorepos](https://blog.opsctrl.dev/why-our-users-are-convinced-we-re-the-home-of-nestjs-monorepos?utm_source=hashnode&utm_medium=feed)

How opsctrl handles nestjs monorepos

7 min read · [blog.opsctrl.dev](https://blog.opsctrl.dev/why-our-users-are-convinced-we-re-the-home-of-nestjs-monorepos?utm_source=hashnode&utm_medium=feed)

[Jul 22](https://hashnode.com/posts/why-our-users-are-convinced-we-re-the-home-of-nestjs-monorepos/6a60e249ddbbedb0bde669db)

### [How We Isolate Hundreds of Tenants — and Prevent Cross-Tenant Bleed](https://blog.opsctrl.dev/how-we-isolate-hundreds-of-tenants-and-prevent-cross-tenant-bleed?utm_source=hashnode&utm_medium=feed)

A single-tenant deployment is easy: one app, one set of resources, one blast radius that only ever touches its owner. A multi-tenant platform is a different animal. On opsctrl, hundreds of unrelated a

7 min read · [blog.opsctrl.dev](https://blog.opsctrl.dev/how-we-isolate-hundreds-of-tenants-and-prevent-cross-tenant-bleed?utm_source=hashnode&utm_medium=feed)

[Jul 18](https://hashnode.com/posts/how-we-isolate-hundreds-of-tenants-and-prevent-cross-tenant-bleed/6a5c0a0c302f42cd00cb070e)

### [Every App Gets a URL: How opsctrl Handles Dynamic and Custom DNS](https://blog.opsctrl.dev/every-app-gets-a-url-how-opsctrl-handles-dynamic-and-custom-dns?utm_source=hashnode&utm_medium=feed)

One of the quiet promises of a Platform-as-a-Service is that you should never have to think about DNS. You push code, and a few moments later there's a live URL with a valid SSL certificate sitting be

8 min read · [blog.opsctrl.dev](https://blog.opsctrl.dev/every-app-gets-a-url-how-opsctrl-handles-dynamic-and-custom-dns?utm_source=hashnode&utm_medium=feed)

[Jul 18](https://hashnode.com/posts/every-app-gets-a-url-how-opsctrl-handles-dynamic-and-custom-dns/6a5be30f17e1a1eef12a965a)

### [What we've learn about NestJS after deploying a hundred api's](https://blog.opsctrl.dev/what-we-ve-learn-about-nestjs-after-deploying-a-hundred-api-s?utm_source=hashnode&utm_medium=feed)

A few months back we hastily released Opsctrl into the wild but within the constraints of a Private Beta and I've personally never learn so much about this framework up until recently .

2 min read · [blog.opsctrl.dev](https://blog.opsctrl.dev/what-we-ve-learn-about-nestjs-after-deploying-a-hundred-api-s?utm_source=hashnode&utm_medium=feed)

[Jun 23](https://hashnode.com/posts/what-we-ve-learn-about-nestjs-after-deploying-a-hundred-api-s/6a3abdbfec3e8a2768ec2cfb)

### [NestJS Deployment on pnpm 11: Fixing Native Binaries Like bcrypt in Docker](https://blog.opsctrl.dev/nestjs-deployment-on-pnpm-11-fixing-native-binaries-like-bcrypt-in-docker?utm_source=hashnode&utm_medium=feed)

You changed nothing. pnpm changed a default. And now your pipeline is on fire. Upon close inspection you find something like this: ERR\_PNPM\_IGNORED\_BUILDS The following dependencies have build script

5 min read · [blog.opsctrl.dev](https://blog.opsctrl.dev/nestjs-deployment-on-pnpm-11-fixing-native-binaries-like-bcrypt-in-docker?utm_source=hashnode&utm_medium=feed)

[1](https://hashnode.com/posts/nestjs-deployment-on-pnpm-11-fixing-native-binaries-like-bcrypt-in-docker/6a272a4b11ee3d024249941c) [Jun 8](https://hashnode.com/posts/nestjs-deployment-on-pnpm-11-fixing-native-binaries-like-bcrypt-in-docker/6a272a4b11ee3d024249941c)
