Skip to Content
User ManualsPlatform Architecture

Platform Architecture

This manual provides the definitive architectural map of the PlugZero Intelligence platform, detailing the folder hierarchies and component organization for both the Frontend and Backend repositories.


⚙️ 1. Backend Architecture (plugzero_api)

The backend is built with Django REST Framework (DRF). It follows a “Plug-and-Play” micro-app architecture where each core feature is isolated into its own Django application.

Core Directory Structure

plugzero_api/ ├── accounts/ # User & Team Management, RBAC ├── analysis/ # Computational math & Google Gemini Integration ├── data_ingestion/ # Scraping, Files, and Survey engines ├── media_intelligence/ # Social Listening & Sentiment tracking ├── seo_intelligence/ # Technical Site Audits & Search Trends ├── plugzero_api/ # Core Configuration (Settings, Celery, URLs) ├── media/ # User-uploaded files & generated reports └── static/ # System static assets

🎨 2. Frontend Architecture (plugzero-analytics)

The frontend is a Next.js 16 application using the App Router for optimized performance and server-side logic.

Core Directory Structure

src/ ├── app/ # Routing Layer (Auth, Marketing, Dashboard) ├── components/ # UI Component Library (Atomic -> Domain) ├── lib/ # Standardized API Client & Logic Layer ├── types/ # TypeScript Definitions (API & Models) ├── hooks/ # Custom React Hooks └── context/ # Global State Providers

📡 3. Communication Patterns

Stateless API Interface

The Frontend communicates exclusively with the Backend via RESTful endpoints. All requests are authenticated using JWT tokens injected into the Authorization header by our standard fretcher utility.

Distributed Processing

Calculations triggered by the Frontend are offloaded to Celery Workers.

  • The Frontend receives a task_id.
  • The Backend processes the math in a background thread.
  • The Frontend polls or receives a state update to display the finished chart/insight.

Developer Rule: Never import code directly across micro-apps in the backend. Use the service layers or standard internal APIs to maintain decoupling.


Last updated on