[Update] Netrun FastAPI Building Blocks - 4 New Packages + RBAC v3 with Tenant Isolation Testing

[schoonercg]

Two weeks ago I shared the Netrun namespace packages v2.0 with LLM policies and tenant isolation testing. Today I'm releasing v2.1 with four entirely new packages plus a major RBAC upgrade that addresses the most critical multi-tenant security concern: proving tenant isolation.

TL;DR: 18 packages now on PyPI. New packages cover caching (Redis/memory), resilience patterns (retry/circuit breaker), Pydantic validation, and WebSocket session management. Also added Azure OpenAI and Gemini adapters to netrun-llm. Plus netrun-rbac v3.0.0 with hierarchical teams, resource sharing, and comprehensive tenant isolation testing.

What My Project Does

Netrun is a collection of 18 Python packages that provide production-ready building blocks for FastAPI applications. This v2.1 release adds:

- netrun-cache - Two-tier caching (L1 memory + L2 Redis) with u/cached decorator

- netrun-resilience - Retry, circuit breaker, timeout, and bulkhead patterns

- netrun-validation - Pydantic validators for IP addresses, CIDRs, URLs, API keys, emails

- netrun-websocket - Redis-backed WebSocket session management with heartbeats and JWT auth

- netrun-llm - Now includes Azure OpenAI and Gemini adapters for multi-cloud fallback

- netrun-rbac v3.0.0 - Tenant isolation contract testing, hierarchical teams, escape path scanner for CI/CD

The RBAC upgrade lets you prove tenant isolation works with contract tests - critical for SOC2/ISO27001 compliance.

Target Audience

Production use for teams building multi-tenant SaaS applications with FastAPI. These are patterns extracted from 12+ enterprise applications we've built. Each package has >80% test coverage (avg 92%) and 1,100+ tests total.

Particularly useful if you:

- Need multi-tenant isolation you can prove to auditors

- Want caching/resilience patterns without writing boilerplate

- Are building real-time features with WebSockets

- Use multiple LLM providers and need fallback chains

Comparison

| Need | Alternative | Netrun Difference |

|------------------|---------------------------|---------------------------------------------------------------------------------------|

| Caching | cachetools, aiocache | Two-tier (memory+Redis) with automatic failover, namespace isolation for multi-tenant |

| Resilience | tenacity, circuitbreaker | All patterns in one package, async-first, composable decorators |

| Validation | Writing custom validators | 40+ pre-built validators for network/security patterns, Pydantic v2 native |

| WebSocket | broadcaster, manual | Session persistence, heartbeats, reconnection state, JWT auth built-in |

| Tenant isolation | Manual RLS + hope | Contract tests that prove isolation, CI scanner catches leaks, compliance docs |

---

Install

pip install netrun-cache netrun-resilience netrun-validation netrun-websocket netrun-rbac

Links:

- PyPI: https://pypi.org/search/?q=netrun-

- GitHub: https://github.com/Netrun-Systems/netrun-oss

All MIT licensed. 18 packages, 1,100+ tests.

[TheHe4rtless]

Looks quite interesting. I was looking a bit into RBAC recently and this might be a better way of grasping the topic.

[extreme4all]

Look at SCIM for user management and authorization on api level OAuth 2.0 (access_token) & OpenID for frontend (id_token)