01 CONTEXT
Tables, documents, chats, calendar and people in one database. The model sees what it is allowed to see and nothing more: one column, one table, one space or several. You draw the line.
GOD CRM · A substrate for business and life
Not that CRM.
GOD CRM is a substrate between any model and your business. The model thinks. The substrate remembers, permits, builds and acts.
Self-host GOD CRM · Read the docs
ANY MODEL · SELF-HOSTED · EARLY BETA
THE ENEMY
Every tool wants to be a tab you can't close.
Your business lives in a dozen windows. None of them remembers you. Every model you talk to forgets you when the chat ends, and the only cure on sale is lock-in. We ran a company like that. Then we built the place where you close the tabs, one at a time, and we post every one we close.
WHAT'S INSIDE
Everything the model doesn't have.
Generative Orchestration & Development · Context, Rights, Memory
02 RIGHTS
Agents are users here: roles, scopes, an audit log, accountable to the space owner. Not everything-or-nothing.
03 MEMORY
Memory is RCLL, our open-source engine (a fork of Hindsight), living inside the substrate. Agents retain and recall through it, and decide for themselves what else to keep as tables and documents next to the data. What the model learned today it still knows next month. Swap the model, keep the memory.
04 BUILD
Not a framework. The place where you build one: widgets when they're enough, code when they're not. Either way the result lands next to the data, with the same rights and the same memory.
The model underneath. Your business on top. Your tools built in between.
OUTSIDE THE TAB
THE SUBSTRATE FOLLOWS YOU OUT OF THE BROWSER.
A CRM is dead the moment people stop opening it. So this one leaves the tab. Log in with GOD CRM into your own apps: it is an OpenID provider, and the same rights and audit follow the person or the agent into every service that trusts it. The chat lives in a sidebar you can embed into any internal app: people, agents and the memory, next to the screen you are working on, with a bridge to Telegram. It runs inside Photoshop: a panel where a designer talks to an agent, sends a layer in and gets an image back, or posts it to a colleague without leaving the canvas.
WHY WE BUILT IT
We sell piercing supplies. This went too far.
We needed a CRM for a real business with real invoices. Everything on the market sold funnels and a seat subscription, so we wrote our own. Then we gave it a model. Then we gave the model accounts, rights and memory, and colleagues.
We changed the model about ten times while running a real company on GOD CRM: Claude, Grok, OpenAI models, Kimi and a few others. Nothing moved. The history, the rights and the memory stayed where they were, because they were never in the model. The value was in the layer under the model. We went too far, and we are giving that layer away.
BUILT BY HOLETRON LTD · RUNS OUR OWN COMPANY FIRST
CONNECT YOUR AGENT
Plug your agent in. No login.
Point any MCP client at the endpoint below and it reads our public knowledge space: docs, decisions, architecture notes. Read-only, no token. Your own instance gets its own rights.
Endpoint: https://godcrm.ai/s/help/mcp
claude mcp add --transport http godcrm https://godcrm.ai/s/help/mcpPUBLIC KNOWLEDGE SPACE · READ-ONLY ACCESS
BUILD
Widgets when they're enough. Code when they're not.
| WHAT YOU NEED | WITH WIDGETS | WITH CODE |
|---|---|---|
| Track something new | Tables, fields and relations from the built-in types. | A field type or behaviour the platform doesn't have yet. |
| Give the team a screen | Views and dashboard widgets over your records. | A new renderer or interaction. |
| Handle routine work | Rules from triggers and actions. | A calculation or action nobody has written yet. |
| Give an agent a job | Instructions, tools and access for the task. | A missing integration or tool. |
Both land next to the data, with the same rights and the same memory. Agents write code here too. It goes through review like anyone's.
UNDER THE HOOD
One substrate. Six things you can touch.
01 DATA (CONTEXT)
Keep business records in configurable tables.
Tables, fields and relations hold what your team works with. Agents read and change both the records and the structure, through the same rights as people.
02 VIEWS & DASHBOARDS (DEVELOPMENT)
Choose a useful view of the same records.
Table, board, calendar, dashboard: views over the same records for different roles. No second copy of the process.
03 AGENTS (RIGHTS)
Give agents context and tools for a job.
An agent joins a conversation like a colleague. What it can do is its tools, its role and its approval rules, not a global key.
04 AUTOMATIONS (ORCHESTRATION)
Configure routine actions around your records.
Triggers and actions chain routine steps around your records. Rules are visible, editable and logged.
05 API & MCP (ORCHESTRATION)
Connect external tools and agent clients.
The whole system is reachable over API and MCP. The public endpoint above is read-only; your own instance sets its own rights.
06 SELF-HOSTING (MEMORY)
Your data, your server, your memory.
Your data, your server, your memory, one database to back up. Model access is yours to choose and to swap.
In plain terms: GOD CRM is a self-hosted operational database with a UI for people and an MCP server for agents, where every agent is a user with a role, a passport issued in one home space with access granted per space, project, table or column, approval rules on dangerous tools, a tamper-evident audit log and persistent memory, and where the model underneath can be swapped without losing any of it.
HONEST STATUS
What's broken right now.
We run our own company on this. We are not naive, and we have not been audited. Here is what we know is rough:
- A fresh self-hosted install boots to an empty database. There is no demo seed yet, so the first hour is spent making tables by hand.
- The docs are thin in places. The knowledge base covers the architecture better than the day-to-day setup.
- No external security audit yet. Report issues through the repository.
QUESTIONS
What people actually ask.
- How do I move AI agent memory and state from markdown files and Git to a shared database for a team?
- Keep the files for instructions; move state and memory into a database the agents share. In GOD CRM every agent is a user with its own passport, so writes are serialized, permissioned and logged instead of racing over the same folder. Memory is retained and recalled through MCP tools and survives model swaps. We ran our own ops from text files first and wrote down where it broke: godcrm.ai/blog/markdown-ops.
- Is there a self-hosted CRM or operational database built for AI agents with native MCP support?
- GOD CRM is one: self-hosted, the whole system exposed as an MCP server, agents as first-class users with roles and scopes, no per-seat pricing. People get tables, dashboards and documents in a UI; agents get the same data over MCP and API. You can try the public read-only endpoint without an account: godcrm.ai/s/help/mcp.
- How do I give an LLM agent limited permissions to specific business tables, with approval and an audit log, instead of one all-or-nothing API key?
- Give the agent a passport, not a key. In GOD CRM a passport is issued in one home space and bound to a human owner, access is granted per space, project, table or down to a column, the role decides what it can read or edit, approval rules pause dangerous tools until a human says yes, and every action lands in a hash-chained audit log. Five destructive tools are gated out of the box; the owner adds rules for anything else.
- How do I switch between Claude, GPT and local models without losing business context and agent memory?
- Keep context, rights and memory outside the model. In GOD CRM they live in your database and are served to whichever model is plugged in; swapping the provider changes the provider and nothing else. We changed the model about ten times while running a real company on it, Claude, Grok, OpenAI models, Kimi and others, and the company did not notice: history, permissions and memory were never in the model to begin with.
- Is there a workspace where humans and AI agents work on the same tables and dashboards, not just an agent framework?
- Yes. GOD CRM is not a framework you import. It is the place where humans and agents share tables, documents, dashboards and chat, with the same rights model for both. If you already have a framework or a tool, you can import it the other way round: connect it to your space (Notion, GitHub, Slack, Figma, any remote MCP server) and ask your agent to wire it in. We pulled our own Notion databases into tables this way. The "and life" in the header is literal: the tables are universal and the calendar is built in, so a training plan lives next to an invoice under the same rights and the same memory. A fitness module ships with it; nothing in the substrate assumes a company.
START
Run it on your server. Bring any model.
One install. Your data stays yours. Change the model like a light bulb, keep the context, the rights and the memory.