MIT License · Opencore

Your data. Your agent. Your rules.

DiviDen's core is MIT-licensed. Self-host it for full data sovereignty, bring your own OAuth credentials, extend it with custom integrations, or run private team environments. The managed platform adds marketplace, federation, and zero-config convenience — but the engine is yours.

Why Self-Host

Security, sovereignty, and extensibility

Every byte of data stays on your infrastructure. No third-party data processing. No vendor lock-in. Full control over integrations and agent behavior.

Full Data Sovereignty

Your conversations, contacts, relays, and agent memory never leave your servers. No shared databases, no telemetry, no cloud dependencies.

Bring Your Own OAuth

Self-hosted instances use your own Google Cloud project for Gmail, Calendar, and Drive. No shared credentials — complete OAuth isolation.

Custom Integrations

Extend the protocol with custom action tags, webhook handlers, and MCP tools. Wire DiviDen into your existing infrastructure without restrictions.

Private Team Environments

Run DiviDen for your team on your own infrastructure. Internal relays, private marketplace agents, and custom prompt configurations.

Federation Ready

Your self-hosted instance can federate with other DiviDen instances — including the managed platform — via DAWP (DiviDen Agent Wire Protocol).

Full Audit Trail

Every agent decision generates a reasoning brief. Self-hosted means you own the audit log — no third-party compliance concerns.

Open Core

What ships in the MIT-licensed core

Everything you need to run a fully functional AI command center. The managed platform adds convenience and network effects — but nothing is locked away.

Full AI Agent Engine
17 prompt groups, 63 action tags, persistent memory
Queue & NOW Engine
Dynamic priority ranking, queue gating, mark-complete workflows
Multi-Inbox
Up to 3 Google accounts per operator identity, unified inbox with account filtering
Calendar Integration
Full read/write Google Calendar with checkbox-style event management
Persistent Chat
Context compounds over sessions. Discuss with Divi from any view.
Goals & Progress
Define objectives, track measurable progress, automatic priority scoring
Relay Protocol
Direct, broadcast, and ambient modes with learning engine
The Brief
Full reasoning artifact on every agent decision
Teams & Projects
Persistent teams, scoped projects, visibility controls
Webhooks & API
Inbound/outbound webhooks, REST API with key auth
MCP v1.6 Tools
60+ tools including capabilities_browse, queue gating
AgentWidget System
Interactive components in chat — choice cards, action lists, payment prompts
Google Drive
Read-only access to Drive files via OAuth
Gmail API Send
Send via Gmail API — no SMTP config needed for Google accounts
Drafts & Inline Reply
Drafts filter tab, inline reply bar in inbox threads
Write Scopes
gmail.send, gmail.compose, full calendar read/write
Self-Hosted OAuth
Graceful degradation when Google OAuth not configured
Capabilities System
20 skill packs across 7 categories, integration-gated installs

Comparison

Self-Hosted vs Managed Platform

The core engine is identical. The managed platform adds network effects, zero-config integrations, and marketplace payments.

FeatureSelf-HostedManaged
AI Agent EngineFullFull
Chat, Queue, NOW, Goals
Multi-Inbox (3 accounts)BYOOPre-configured
Gmail API Send
Calendar Read/Write
Google Drive
Relay Protocol
The Brief (Reasoning)
AgentWidget System
Discuss with Divi
Capabilities (20 packs)
MCP v1.6 / A2A v0.4
Federation (DAWP)ConfigureBuilt-in
Bubble StoreNetwork
Stripe Payments85% payout
OAuth ConfigurationYour GCP projectZero-config
HostingYour infraFully managed
Data LocationYour serversOur cloud

Quick Start

Self-host in under 10 minutes

Clone the repo, configure your environment, and you're live. Production-ready with Docker or bare-metal Node.js.

1. Clone & Install

git clone https://github.com/dividen/dividen.git
cd dividen
yarn install
cp .env.example .env

2. Configure Environment

DATABASE_URL

PostgreSQL connection string

required
NEXTAUTH_SECRET

Random 32+ char secret for session encryption

required
NEXTAUTH_URL

Your instance URL (e.g. https://dividen.yourcompany.com)

required
OPENAI_API_KEY

LLM provider API key

required
GOOGLE_CLIENT_ID

Your GCP OAuth client ID (for Gmail/Calendar/Drive)

GOOGLE_CLIENT_SECRET

Your GCP OAuth client secret

GOOGLE_REDIRECT_URI

OAuth callback URL (https://your-domain/api/auth/google-callback)

FEDERATION_SECRET

Shared secret for cross-instance relay HMAC signing

STRIPE_SECRET_KEY

For marketplace payments (optional)

3. Initialize & Run

yarn prisma generate
yarn prisma db push
yarn build
yarn start

Or with Docker:

docker compose up -d

Note on OAuth: If you skip Google OAuth setup, DiviDen will gracefully degrade — the Integration Manager shows a setup prompt with a link to the Google Cloud Console instead of a broken connect button. No crashes, no silent failures.

Architecture

10 protocol layers, 60 data models

DiviDen is structured as a layered protocol — each layer is independently testable, extensible, and replaceable.

01
Identity & Profile
Routing manifests — not résumés. Skills, experience, task types, availability.
02
Goals & NOW Engine
Objectives + dynamic priority ranking engine that surfaces what matters now.
03
Ambient Relay Protocol
Direct, broadcast, and ambient modes. Agents exchange context-rich relays.
04
The Brief
Every orchestration generates a reasoning artifact with full transparency.
05
Ambient Learning
Every relay interaction feeds timing, disruption, topic success learnings.
06
Teams & Projects
Persistent teams, scoped projects, organizational context for routing.
07
Capabilities & Marketplace
Modular skill packs, integration-gated installs, 20 seeded capabilities.
08
Federation (DAWP)
Cross-instance communication. Your company, theirs. Agents still coordinate.
09
Integration Surface
A2A v0.4, MCP v1.6, webhooks, Agent API v2 — connect anything.
10
Marketplace & Payments
Agent marketplace with Stripe Connect. 85% developer payout.

Integration Scopes

Google OAuth — full read & write

Self-hosted instances use your own GCP project. The managed platform provides pre-configured OAuth. Either way, these are the scopes.

gmail.readonlyRead inbox threads, list messagesRead
gmail.sendSend mail as the authenticated user via Gmail APIWrite
gmail.composeCreate and manage draftsWrite
calendarFull read/write access to Google Calendar eventsRead/Write
drive.readonlyList and read Google Drive filesRead
userinfo.emailAccess user email addressRead
userinfo.profileAccess user profile informationRead

Run it yourself. Or let us. Either way, it's yours.

The MIT-licensed core gives you everything you need. The managed platform gives you everything you don't want to maintain.