Trinity

The open-source AI-native CRM. Our vision: the AI operating system for business. Run your whole company by chatting with the AI assistant you already love: ChatGPT, Claude, Gemini, and more.

Created by Thanh Tran · X @trntnthnh · YouTube · TikTok

Tiếng Việt · Website · Deploy · Roadmap · Contributing

Why Trinity

Most business software makes you learn its menus. Trinity flips that around: you tell your AI assistant what you need, and it runs the system for you.

• "Add Mr. Nam from Gò Vấp, interested in product A, call him back Friday." Done: contact, deal and reminder are created.

• "How did the Q3 campaign do compared to Q2?" Your assistant reads the data and answers with a chart.

• "Every morning, sync new orders from my Google Sheet." Trinity builds a small add-on for it. The add-on runs in its own sandbox, so it can never break the main system.

Start lean, grow with you. On first connect, your AI asks about your business, imports your Excel/Google Sheet, and builds the pipelines and screens you need. A core set (overview, customers, tasks, reports, inbox) is on; everything else is a switch in Settings › Features, and the menu only shows what is on. Your AI can turn features on for your industry.

Built for Vietnamese businesses first. Zalo, VietQR, Vietnamese UI and data formats work out of the box. Global CRMs don't cover these.

Related MCP server: HighLevel MCP Server

How it works

Trinity ships a built-in Model Context Protocol (MCP) server with OAuth login. In the app, Bắt đầu ("Get started") asks which assistant you use (ChatGPT, Claude, Claude Code, Antigravity, Gemini CLI, Cursor, Codex CLI, VS Code Copilot…) and copies one prompt: paste it and the assistant adds the server, signs you in and starts setting up. Any MCP-capable assistant connects to it and gets tools for records, pipelines, reports and add-ons, scoped by the connecting user's role. The server itself never calls an AI model and holds no AI API keys: the intelligence comes from the assistant you bring.

Your AI assistant (ChatGPT · Claude · Gemini · Cursor · OpenClaw …)
        │  MCP + OAuth
        ▼
Trinity  ──  CRM · Sales · Zalo · HR · Reports
        │
        └── Add-ons (Deno sandbox, one process each)

Features

How far it is tested

• Tested end to end on a fresh deploy (the Vercel button, a new Postgres database): first sign-in, connecting an AI assistant, building tables by chat, importing records, the AI tools.

• Tested with real accounts: publishing and scheduling posts to Facebook Pages and YouTube, Messenger messages, Facebook comment rules (auto-replies, hiding phone numbers), the Interactions timeline, incoming Zalo OA messages.

• Tested with sample data only: the posting queue, recurring posts and CSV import, dashboards and reports, the AI-native overview, feature switches, POS, HR, attendance and payroll, the online store (sample shop).

• These areas have automated tests; connectors are listed below.

Connectors and how far each is tested

Details per connector: docs/integrations/status.md. What comes next: ROADMAP.md.

See it

Tech stack

Next.js 16 · React 19 · Tailwind 4 · NestJS 10 · Express · Prisma 6 · PostgreSQL 16 · Redis · Deno (add-on sandbox) · pnpm monorepo.

Deploy

Pick one path. Both give you the same app.

Option 1: Vercel (serverless, no server to manage)

The button clones the repository into your GitHub account, creates the Vercel project with Root Directory apps/web, asks for the environment variables below and offers to add a Neon Postgres database. The repository is created under the name trinity; if you already have one with that name, change the name in the first step of the form.

Before you fill in the form:

1. Click "Add Neon" first. The environment-variable fields stay locked until the database is added.

2. Turn Neon Auth off when Neon offers it. Trinity has its own login and does not use it; leaving it on only adds unused NEON_AUTH_* variables.

3. Pick a region close to your users for both the Neon database and the Vercel functions (Project Settings → Functions → Function Region), for example Singapore (sin1) for Vietnam. The default is Washington (iad1), which makes the first request from Vietnam take about 5 s. Put the database and the functions in the same region.

4. Generate the secrets on your machine with openssl rand -hex 32 (and openssl rand -base64 32 for INTEGRATIONS_SECRET_KEY), and set INTEGRATIONS_MCP_ENABLED to true. Both are required: a new workspace is set up through your AI assistant, so without them it cannot get past the "Start" screen. If you forgot them, set them in Project Settings → Environment Variables and redeploy.

On every build, Vercel installs the workspace, builds it, applies the database migrations and seeds the first admin account (all idempotent, so redeploys are safe). Nothing else to run.

Environment variables (Project Settings → Environment Variables, or the form the button shows):

Deploying from the command line instead of the button (a fresh clone is enough). Run everything from the repository root (the project's Root Directory is apps/web, but the CLI has to upload the whole monorepo):

git clone https://github.com/tanthanhkid/trinity.git && cd trinity
vercel link --yes --project my-trinity                     # creates the project
vercel api -X PATCH /v9/projects/my-trinity -F rootDirectory=apps/web   # or: Settings > General > Root Directory
vercel api -X PATCH /v9/projects/my-trinity -F serverlessFunctionRegion=sin1   # functions near your users (default iad1 = Washington)
vercel integration add neon                                # or add any Postgres and set DATABASE_URL yourself
openssl rand -hex 32 | vercel env add JWT_SECRET production --sensitive
openssl rand -hex 32 | vercel env add SERVICE_SECRET production --sensitive
openssl rand -hex 32 | vercel env add CRON_SECRET production --sensitive
printf '%s' you@example.com | vercel env add SEED_ADMIN_EMAIL production
printf '%s' 'a-long-password' | vercel env add SEED_ADMIN_PASSWORD production --sensitive
printf true | vercel env add INTEGRATIONS_MCP_ENABLED production       # connect your AI assistant
openssl rand -base64 32 | tr -d '\n' | vercel env add INTEGRATIONS_SECRET_KEY production --sensitive
vercel deploy --prod

Tried on a fresh Vercel account (2026-10-15): about 4 minutes from clone to sign-in, most of it the first build.

• vercel link writes .env.local (a short-lived Vercel token) and adds it to .gitignore; vercel integration add neon also writes agent skill files (.agents/, .claude/, skills-lock.json). All are git-ignored and safe to delete.

• From the command line Neon is created in its default region and with Neon Auth on (unused NEON_AUTH_* variables, harmless). To choose the database region, add Neon from the Vercel dashboard (Storage) instead.

• The two INTEGRATIONS_* lines are required. A new workspace is set up through your AI assistant, so without them it stays on the "Start" screen. If you forgot them, add them and redeploy.

Then open the production URL and sign in with the admin account above. Notes:

• The first admin is only created when it does not exist yet; redeploying never overwrites a password.

• A new workspace starts empty on purpose: the sidebar only shows AI activity and Settings until your AI assistant builds the workspace from the Bắt đầu ("Get started") screen. After that the core set is on and everything else is a switch in Settings → Tính năng ("Features"); Zalo OA, for example, answers 403 until its switch is on. Settings is grouped in the Vietnamese UI as Tính năng & Kết nối (features & connections), Khách hàng (customer lists), Công ty & Nhân sự (users, roles, teams) and Cá nhân (profile, notifications); a section only shows when its feature is on.

• The interface is currently Vietnamese only. Your data and the AI tools work in any language.

• Vercel runs the API inside the Next.js app (one function, 60 s limit). Uploaded files need object storage: set STORAGE_DRIVER=vercel-blob with a Vercel Blob token, or an S3-compatible driver (see .env.example). Notifications use polling instead of WebSockets. Add-ons (Deno sandbox, the "Extensions" page) and Redis-backed features need a long-running server, so use Option 2 for them.

Option 2: Self-host with Docker Compose

You need Docker with Compose. On a laptop the first build takes about 5 minutes.

git clone https://github.com/tanthanhkid/trinity.git
cd trinity
./install.sh --up

install.sh creates .env from .env.example with freshly generated random secrets and admin password (it never overwrites an existing .env, so it is safe to re-run), prints the admin credentials once, and starts the stack with docker compose up --build -d. Open http://localhost:3000 and sign in with the printed admin account. No demo data is seeded by default; if you want demo data, set SEED_DEMO_DATA=true in .env (or run SEED_DEMO_DATA=true ./install.sh) before the first start.

Manual alternative: cp .env.example .env, replace every change-me-* value (openssl rand -hex 32), then docker compose up --build -d. If SEED_ADMIN_PASSWORD is empty, the generated password is printed by docker compose logs migrate.

Tagged releases publish ready-made images to GitHub Container Registry (ghcr.io/tanthanhkid/trinity-api, ghcr.io/tanthanhkid/trinity-web). More in docs/deployment.md.

To let your AI assistant drive Trinity, set INTEGRATIONS_MCP_ENABLED=true, a public INTEGRATIONS_PUBLIC_BASE_URL and an INTEGRATIONS_SECRET_KEY in .env, then follow docs/integrations.

For development without Docker: pnpm install && pnpm dev (needs Node 22, Postgres and Redis running locally).

Monitoring (optional)

Error reporting (Sentry) and anonymous product metrics (PostHog) are off by default: no network call is made and no SDK is loaded until you set the variables. Variables: SENTRY_DSN (API), SENTRY_DSN_WEB (browser), SENTRY_ENVIRONMENT, SENTRY_TRACES_SAMPLE_RATE, TRINITY_RELEASE, POSTHOG_KEY, POSTHOG_HOST, POSTHOG_REPLAY, MONITORING_HASH_SECRET. User ids are hashed (HMAC) before they leave your server; request bodies, cookies, headers, query strings, emails and phone numbers are stripped; session replay (if enabled) masks all text and inputs. Server events: onboarding_step, feature_toggled, plan_changed, table_created, table_updated, post_published, comment_rule_saved, with keys, counts and booleans only. Details in docs/deployment.md.

Why I built this

I'm Thanh. I build software with AI every day, and I kept seeing small businesses drown in menus and spreadsheets. So I built the system I wanted: one where you just tell your AI what to do. I'm giving it away so everyone can run their business this way. — Thanh Tran

Community

• 📺 YouTube: Lập trình với AI (Vietnamese tutorials, building with AI)

• 🎵 TikTok: @laptrinhvoiai

• 𝕏 X: @trntnthnh (release news)

• 💬 Questions, ideas and show-and-tell: GitHub Discussions

• 🐛 Bugs: GitHub Issues

• 🔒 Security issues: please follow SECURITY.md, not public issues

License

Trinity is licensed under AGPL-3.0. You can use, modify and self-host it for free. If you offer a modified version to others over a network, you must publish your changes under the same license.

Need to embed Trinity in a closed-source product or avoid AGPL obligations? A commercial license is available: see COMMERCIAL.md.

"Trinity" and the Trinity logo are trademarks. See TRADEMARK.md.