How growly-foundation/suite works
Project type and purpose
• This is a full-stack monorepo for an AI-powered DeFi “Suite”:
• Frontends: marketing site, admin dashboard, embeddable chat widget, playground
• Shared libraries: core utilities, UI components
• Backend: NestJS micro-service exposing AI/chat/agent APIs and on-chain integrations
• Purpose: let dApp builders embed an LLM-driven chat widget that guides users through DeFi workflows, managed via an admin dashboard, powered by a specialized multi-agent backend.
File structure
• Root: pnpm/Turbo monorepo orchestrates packages, workflows, Docker, CI/CD
• packages/core & packages/ui: shared code (models, services, components)
• packages/suite: React/TS “chat widget” library for embedding in dApps
• packages/dashboard, website, playground: Next.js frontends (admin, marketing, demo)
• packages/server: NestJS backend, modularized by feature (agent, chat, message, openai, suite-core, growly, firecrawl), interacts with a SQL database & external APIs
• Configs: Dockerfiles, docker-compose, GitHub Actions, Turborepo (turbo.json)
README for additional insights
• Client layers (Suite widget, Dashboard)
• NestJS server wrapping a Langchain multi-agent supervisor
• Specialized agents: Web3 Data Agent, Search Agent, Growly Agent
• Database for state, docs, workflow definitions
• External services: Firecrawl, DefiLlama, Tavily, Ponder (planned), OpenAI, x402 payments
• Tech stack: React/TS, Tailwind, Node/NestJS, Langchain, Onchainkit/Wagmi/Viem