Platform Architecture Overview

blackLen is engineered with a modular, decoupled architecture designed for high throughput, strict tenant isolation, and responsive operator user experience.

---

Ingress Topology & Subdomain Routing

The platform is partitioned across dedicated subdomains:

• Marketing & Technical Documentation (blacklen.org): Public landing pages, feature tours, sitemaps, and technical documentation.
• Operator Workspace Application (app.blacklen.com): High-velocity Single Page Application (SPA) where security teams manage organizations, projects, checklists, scripts, and payloads.
• REST API Gateway (api.blacklen.com): Centralized backend handling authentication, object-level RBAC evaluation, data persistence, and rate limiting.

---

Frontend & Client Architecture

The operator workspace frontend is designed for fast, frictionless security workflows:

• Core Framework: React 19 built with Vite 7 for rapid compilation and minimal asset footprints.
• State Management: Redux Toolkit managing active organization contexts, project states, and notification channels.
• Embedded Script Engine: Integrated Monaco Editor powering in-browser custom script authoring and version history inspection.
• Token Management: Client-side credential management with automated token refreshing across active browser tabs.

---

Backend API & Storage Engine

The platform backend exposes a unified RESTful API:

• Framework: Django REST Framework (DRF) providing serializer validations, transactional integrity, and object-level permission enforcement.
• Relational Storage: PostgreSQL storing user accounts, organization memberships, projects, attack surface assets, checklist items, and versioned scripts.
• Cache & Rate-Limiting: Redis providing caching, session concurrency coordination, and multi-vector rate limiting.

---

Two-Tier Boundary Separation

Data in blackLen is strictly partitioned across two architectural tiers:

1. Tier 1 — Organization Governance:

   • Controls organization profile, member invitations, role management, and global resource libraries (tools, script templates, payload collections).
   • Bound to the Organization entity.

2. Tier 2 — Project Engagement:

   • Isolates specific security assessments, penetration tests, or red team exercises.
   • All scoped assets, active checklist execution states, and findings live exclusively inside the project boundary.
   • Bound to the Project entity with independent project-level membership roles.