# haydenbleasel/eververse architecture

> Architecture diagram of the GitHub repository haydenbleasel/eververse, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-03-30). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/haydenbleasel/eververse
- Repository: https://github.com/haydenbleasel/eververse

## Overview

The Eververse project is an open source product management platform—a full-stack solution that brings together ideas, feedback, and roadmaps for product teams, and it leverages AI to enhance the planning process. The project is organized as a large monorepo using Turborepo (as evidenced by files like turbo.json, pnpm-workspace.yaml) and is built with modern technologies such as Next.js, TypeScript, React (tsx files), Tailwind CSS, and PostCSS. There is a clear separation between various apps (each representing a different interface or service) and shared packages (libraries and integrations).

##### Main Components
- Frontend Clients and Applications:
- “apps/app”: The core product management application (where organizations manage features, feedback, initiatives, releases, roadmaps, etc.).
- “apps/web”: Likely a marketing/landing website providing information about the platform.
- “apps/portal”: A specialized portal (possibly for customer interactions or embedded experiences).
- “apps/widget”: A widget that can be embedded elsewhere.
- “apps/email”: The email service that handles notification and initiative update emails.
- “apps/studio” and “apps/docs”: Other UIs for advanced configuration or documentation.

- Backend/API & Services:
- “apps/api”: Acts as the backend with services for authentication, data endpoints, cron jobs (for tasks like importing data, sending digests, handling webhooks) and health checks.

- Shared Libraries and Integration Packages:
- A collection of “packages” (such as packages/ai, packages/analytics, packages/backend, packages/atlassian, packages/canny, packages/design-system, packages/editor, packages/github, packages/intercom, packages/linear, packages/observability, packages/payments, packages/productboard, packages/slack, etc.) provide core functionality, external integrations, analytics, authentication, UI components (design system), and configuration.
- The “packages/backend” folder includes database access (using Prisma) and authentication utilities.

##### Relationships and Interactions
- Frontend applications (apps/app, apps/web, etc.) interact with the backend API (apps/api) for data operations, authentication, and invoking business logic.
- The backend triggers cron jobs and processes webhooks (e.g., database events, integrations with external services like GitHub, Jira, Slack, etc.).
- Shared packages form a common layer that is imported into both apps and backend services. They encapsulate logic for integrations (e.g., atlassian, github, intercom), analytics, and even AI functionalities.
- External services (such as Stripe for payments, AI providers, and integration endpoints for Productboard or Canny) are accessed through dedicated packages/integration modules.

##### Architectural Patterns and Design Principles
- Monorepo Structure – The entire platform is arranged as a monorepo using Turborepo, which facilitates sharing modules and a consistent development workflow.
- Modular Separation – Clear division between multiple specialized applications (UI layers) and shared libraries (packages) promotes reusability and loose coupling.
- Microservice-like APIs – Although not physically separated into independent services, the “apps/api” folder’s directory structure (with separate routes for authentication, cron jobs, data endpoints, and webhooks) indicates a modular approach similar to microservices where each route or function is clearly scoped.
- Integration First – Numerous packages handle external integrations (such as Atlassian, GitHub, Productboard, etc.), highlighting an extensible design focused on connecting with third-party services.

##### Relevant Technologies and Frameworks
- Next.js, React, and TypeScript form the backbone of the frontend applications.
- Tailwind CSS and PostCSS are used for styling.
- Prisma (as seen in packages/backend/prisma/schema.prisma) is used for database access.
- Various packages indicate support for features like AI, analytics, and external service integrations.
- Turborepo and PNPM manage the monorepo.

- Each component should be labeled clearly, for example:
- “Frontend UI – App (Product Management Interface)”
- “API Gateway/Backend – Data & Auth Service”
- “Shared Libraries – AI, Integrations, Analytics, Design System, etc.”
- “External Services – GitHub, Atlassian, Stripe, etc.”
- Data flow from the UI (client browsers) to the backend API.
- API interactions with shared packages.
- Cron jobs and webhook routes triggering actions within the API.
- Shared libraries/integrations and external services (another distinct style).

##### Detailed Component Breakdown
- At the top level, illustrate user devices (browsers, mobile clients) connecting to the various frontend apps.
- A layer representing the shared service modules (the “packages” such as UX design system, integration modules, backend utilities) which feed into both the API and frontend.

## Diagram (Mermaid)

```mermaid
flowchart TD
    %% User Devices
    U["User Devices (Browser/Mobile)"]:::external

    %% Frontend Applications
    subgraph "Frontend Applications"
        A_APP["Core Product Management (Product UI)"]
        A_WEB["Marketing Website"]
        A_Portal["Specialized Portal"]
        A_Widget["Embedded Widget"]
        A_Email["Email Service"]
        A_Studio["Studio (Advanced Configuration)"]
        A_Docs["Documentation UI"]
    end

    %% API & Backend Services
    subgraph "API & Backend Services"
        API["API Gateway/Backend"]
    end

    %% Shared Packages & Integrations
    subgraph "Shared Packages"
        S_AI["AI Functionality"]
        S_Analytics["Analytics"]
        S_Backend["Backend Utilities"]
        S_Atlassian["Atlassian Integration"]
        S_Canny["Canny Integration"]
        S_GitHub["GitHub Integration"]
        S_Intercom["Intercom Integration"]
        S_Linear["Linear Integration"]
        S_Observability["Observability"]
        S_Payments["Payments Integration"]
        S_Productboard["Productboard Integration"]
        S_Slack["Slack Integration"]
        S_Design["Design System"]
    end

    %% External Services
    subgraph "External Services"
        E_Atlassian["Atlassian Service"]
        E_Canny["Canny Service"]
        E_GitHub["GitHub Service"]
        E_Intercom["Intercom Service"]
        E_Linear["Linear Service"]
        E_Payments["Payments Gateway"]
        E_Productboard["Productboard Service"]
        E_Slack["Slack Service"]
    end

    %% Connections from User Devices to Frontend Applications
    U --> A_APP
    U --> A_WEB
    U --> A_Portal
    U --> A_Widget
    U --> A_Email
    U --> A_Studio
    U --> A_Docs

    %% Frontend Applications communicating with Backend API
    A_APP -->|"calls"| API
    A_WEB -->|"calls"| API
    A_Portal -->|"calls"| API
    A_Widget -->|"calls"| API
    A_Email -->|"calls"| API
    A_Studio -->|"calls"| API
    A_Docs -->|"calls"| API

    %% API interacting with Shared Packages
    API -->|"uses"| S_AI
    API -->|"uses"| S_Analytics
    API -->|"uses"| S_Backend
    API -->|"uses"| S_Atlassian
    API -->|"uses"| S_Canny
    API -->|"uses"| S_GitHub
    API -->|"uses"| S_Intercom
    API -->|"uses"| S_Linear
    API -->|"uses"| S_Observability
    API -->|"uses"| S_Payments
    API -->|"uses"| S_Productboard
    API -->|"uses"| S_Slack
    API -->|"uses"| S_Design

    %% Shared Integrations connecting to External Services
    S_Atlassian -->|"integrates"| E_Atlassian
    S_Canny -->|"integrates"| E_Canny
    S_GitHub -->|"integrates"| E_GitHub
    S_Intercom -->|"integrates"| E_Intercom
    S_Linear -->|"integrates"| E_Linear
    S_Payments -->|"integrates"| E_Payments
    S_Productboard -->|"integrates"| E_Productboard
    S_Slack -->|"integrates"| E_Slack

    %% Click Events for Frontend Applications
    click A_APP "https://github.com/haydenbleasel/eververse/tree/main/apps/app"
    click A_WEB "https://github.com/haydenbleasel/eververse/tree/main/apps/web"
    click A_Portal "https://github.com/haydenbleasel/eververse/tree/main/apps/portal"
    click A_Widget "https://github.com/haydenbleasel/eververse/tree/main/apps/widget"
    click A_Email "https://github.com/haydenbleasel/eververse/tree/main/apps/email"
    click A_Studio "https://github.com/haydenbleasel/eververse/tree/main/apps/studio"
    click A_Docs "https://github.com/haydenbleasel/eververse/tree/main/apps/docs"

    %% Click Event for Backend API
    click API "https://github.com/haydenbleasel/eververse/tree/main/apps/api"

    %% Click Events for Shared Packages
    click S_AI "https://github.com/haydenbleasel/eververse/tree/main/packages/ai"
    click S_Analytics "https://github.com/haydenbleasel/eververse/tree/main/packages/analytics"
    click S_Backend "https://github.com/haydenbleasel/eververse/tree/main/packages/backend"
    click S_Atlassian "https://github.com/haydenbleasel/eververse/tree/main/packages/atlassian"
    click S_Canny "https://github.com/haydenbleasel/eververse/tree/main/packages/canny"
    click S_GitHub "https://github.com/haydenbleasel/eververse/tree/main/packages/github"
    click S_Intercom "https://github.com/haydenbleasel/eververse/tree/main/packages/intercom"
    click S_Linear "https://github.com/haydenbleasel/eververse/tree/main/packages/linear"
    click S_Observability "https://github.com/haydenbleasel/eververse/tree/main/packages/observability"
    click S_Payments "https://github.com/haydenbleasel/eververse/tree/main/packages/payments"
    click S_Productboard "https://github.com/haydenbleasel/eververse/tree/main/packages/productboard"
    click S_Slack "https://github.com/haydenbleasel/eververse/tree/main/packages/slack"
    click S_Design "https://github.com/haydenbleasel/eververse/tree/main/packages/design-system"

    %% Styles
    classDef frontend fill:#cce5ff,stroke:#004085,stroke-width:2px;
    classDef backend fill:#d4edda,stroke:#155724,stroke-width:2px;
    classDef shared fill:#fff3cd,stroke:#856404,stroke-width:2px;
    classDef external fill:#f8d7da,stroke:#721c24,stroke-width:2px;

    %% Assign Classes
    class A_APP,A_WEB,A_Portal,A_Widget,A_Email,A_Studio,A_Docs frontend;
    class API backend;
    class S_AI,S_Analytics,S_Backend,S_Atlassian,S_Canny,S_GitHub,S_Intercom,S_Linear,S_Observability,S_Payments,S_Productboard,S_Slack,S_Design shared;
    class U,E_Atlassian,E_Canny,E_GitHub,E_Intercom,E_Linear,E_Payments,E_Productboard,E_Slack external;
```
