Exponential.im

An open-source productivity and project management platform built with the T3 Stack. Manage projects, track goals and key results, plan your day with AI, and collaborate across workspaces.

Features

• Project Management - Create and track projects with status, priority, and progress across workspaces
• Action Management - Flexible task system with priorities, tags, and project linking
• Goals & OKRs - Hierarchical goal-key-result-action alignment
• Daily Planning - Journal system with reflection, planning tools, and daily scoring
• AI Assistant - Chat interface powered by Mastra agents with semantic video search
• Meetings - Calendar integration with transcription and auto-generated action items
• CRM - Contact/organization management, deal pipeline (Kanban), Gmail/Calendar import
• Workspaces - Organize everything by team or client (personal, team, organization)
• Bounty System - Attach bounties to actions for open-source contributors (coming soon)

Tech Stack

• Framework: Next.js 15 with App Router
• Language: TypeScript (strict mode)
• Authentication: NextAuth.js v5 (Discord, Google, Microsoft, Notion, Email)
• Database: PostgreSQL with Prisma ORM
• API: tRPC for end-to-end type-safe APIs
• UI: Mantine v7 + Tailwind CSS
• AI: OpenAI, Langchain, Mastra multi-agent system
• Testing: Vitest with Testcontainers for integration tests
• Deployment: Vercel

Getting Started

Prerequisites

• Node.js >= 20
• npm >= 10
• PostgreSQL (local or remote)

Setup

1. Clone the repository

   git clone https://github.com/positonic/exponential.git
   cd exponential
   

2. Install dependencies

   npm install
   

3. Configure environment variables

   cp .env.example .env.local
   

   Edit .env.local and fill in the required values. At minimum:

   Variable	Description
   DATABASE_URL	PostgreSQL connection string
   AUTH_SECRET	Generate with npx auth secret
   DATABASE_ENCRYPTION_KEY	Generate with openssl rand -base64 32 (required in production)
   A way to sign in	An OAuth pair (Google or Discord), SMTP or Postmark for emailed sign-in codes, or AUTH_LOG_SIGN_IN_CODES=true to print codes to the server log

   See .env.example for all available configuration options.

4. Set up the database

   npx prisma migrate dev
   

5. Start the development server

   npm run dev
   

   Open http://localhost:3000.

Self-hosting

A production install needs four variables (DATABASE_URL for a Postgres with pgvector, AUTH_SECRET, DATABASE_ENCRYPTION_KEY, OPENAI_API_KEY) and one way to sign in. No OAuth app or Postmark account is required. Start from .env.selfhost.example, which lists only what an install needs, then:

SKIP_ENV_VALIDATION=1 npm run build
npm run start:selfhost      # checks env and pgvector, applies migrations, serves
npm run scheduler:selfhost  # in a second process: runs the scheduled jobs (reads the same .env)

Container images

Two images, both built from the repo root. Neither bakes in any configuration: every variable is read when the container starts.

docker build -t exponential-app .                                          # the app
docker build -f docker/scheduler.Dockerfile -t exponential-scheduler .      # the scheduler

• App (Dockerfile): starts with npm run start:selfhost, so the container checks its environment and pgvector, applies pending migrations, then serves on port 3000. Health check: GET /api/health. The build needs a builder with at least 10 GB of memory: measured in a container, its working set peaks at about 9.2 GB, it completes under a 10 GB limit, and it is killed for running out of memory under 8 GB (with 4 CPUs or 14).
• Scheduler (docker/scheduler.Dockerfile): a small Node image with no Next build. It calls the app's cron routes on vercel.json's schedule, so point SCHEDULER_TARGET_URL at the app's address on the network they share.

A full install is four services: Postgres with pgvector, the app, the scheduler, and the Mastra agent service (agent runs and chat). The scheduler and Mastra reach the app over the private network; only the app needs a public address.

This is the beginning of the README. Read the rest at the original. Read the full README ↗