Repository Guide
Last Verified: 2026-05-03The Equa platform is split across several repositories, each handling a distinct concern. This guide explains what each repo does, its tech stack, and how they connect at runtime.
Repository Overview
How Repos Connect at Runtime
Key connections:- equa-web proxies all
/api/*requests to equa-server via webpack-dev-server (configured in webpack config, default targethttp://localhost:3000) - equa-web imports equa-patternlib as an npm dependency from GitHub:
"equa-patternlib": "github:EQUAStart/equa-patternlib-nextjs#master"(Source:equa-web/package.jsonline 24) - equabot-gateway communicates with equa-server and external AI/messaging services via WebSocket and REST
- Storybook runs independently as a visual component playground
Per-Repository Details
equa-web
Frontend single-page application for the Equa equity management platform.src/modules/): actions, admin, agreements, auth, captable, convertibles, documents, equanaut, esop, google-drive, guest, hh-finance, landing, organization, organization-dashboard, payments, profile, referrals, reports, roles, subscriptions, team-members, user-dashboard, welcome
Source: equa-web/src/modules/ directory listing
Path aliases (from equa-web/tsconfig.json):
equa-server
Backend API server using a workspace-based modular monolith architecture.equa-server/modules/ directory listing; equa-server/package.json workspaces config
equabot (equabot-gateway)
AI agent infrastructure supporting multi-channel messaging, browser automation, and tool execution.engines.node: ">=22.12.0" in package.json). Uses pnpm as package manager.
Source: equabot-gateway/package.json
equa-patternlib-nextjs
Shared React component library and design system with Storybook for visual documentation.equa-patternlib-nextjs/package.json
command-center-so
Internal operations dashboard for monitoring and managing the Equa platform and equabot infrastructure.command-center-so/package.json
equa-desktop-app-mac-ios
Planned repository for native desktop (macOS) and mobile (iOS) apps. Currently empty and not initialized — no source code, no package.json, no project files.Inter-Repository Dependencies
Branching Conventions
Branching patterns vary across repositories. There is no single enforced standard.
Source: git status and GitHub Actions workflow trigger configurations across repos
See PR and Commit Workflow for more detail on commit conventions and merge strategies.