How haydenbleasel/eververse works
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.