saas-architect-skill

Map enterprise multi-tenant backend architecture to a scalable SaaS platform with Drizzle ORM, BullMQ, and TimescaleDB.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/boparaiamrit/build-second-brain --skill saas-architect-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: saas-architect-skill
Source: https://github.com/boparaiamrit/build-second-brain/tree/main/plugins/build-second-brain/skills/saas-architect-skill
Command: npx skills add https://github.com/boparaiamrit/build-second-brain --skill saas-architect-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Builds a scalable, governance-driven enterprise backend that enforces strict tenant isolation and a consistent, scalable architecture across Company → Workspace → Domain → Data.

Core Features & Use Cases

  • Enforces a rigid hierarchy to isolate data per domain while enabling shared modules across 10+ products.
  • Provides end-to-end patterns for audit, observability, caching, asynchronous processing with BullMQ, and TimescaleDB event data.
  • Supplies adaptable patterns (Adapter/Manager/Strategy) for SSO, libraries, and plan-based features, enabling runtime selection and easy replacement.
  • Delivers a design blueprint for multi-tenant SaaS backends, including migrations (Drizzle ORM → Prisma migration guidance) and tenant context resolution via Redis.

Quick Start

Build and integrate enterprise-grade multi-tenant backends by applying the tenant-context guard, Drizzle ORM schema, BullMQ queues, TimescaleDB events, and MSSP patterns across modules.

Frequently Asked Questions about saas-architect-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a multi-tenant SaaS backend with Drizzle ORM and TimescaleDB?

Build a multi-tenant SaaS backend by mapping a Company → Workspace → Domain → Data hierarchy using Drizzle ORM schemas, TimescaleDB hypertables for events, and Redis for tenant context resolution to enforce strict data isolation.

How does BullMQ handle asynchronous processing in a multi-tenant architecture?

BullMQ handles asynchronous processing in a multi-tenant architecture by managing background queues that operate within the established tenant context, ensuring isolated job execution across shared modules and multiple workspaces.

What is the best way to structure SSO integrations for an enterprise SaaS platform?

The best way to structure SSO integrations is using adaptable design patterns like Adapter, Manager, and Strategy to enable runtime selection and easy replacement of authentication providers across different company domains.

Can I use this architecture to share modules across multiple products and domains?

Yes, you can share modules across multiple products and domains because the architecture enforces a rigid tenant isolation hierarchy while delivering adaptable patterns for shared recipient services and library features across 10+ products.

How do you enforce tenant isolation using Redis in an enterprise SaaS application?

Redis enforces tenant isolation by resolving and maintaining the tenancy context throughout the request lifecycle, ensuring all subsequent database queries and background jobs remain scoped to the correct Workspace and Domain.