Self-hosted lead sourcing and enrichment

Give OpenGTM a market, a list, or a workbook. It finds companies and people, enriches rows through cost-ordered provider waterfalls, researches hard questions with cited agents, watches for buying intent, and sends qualified records to the tools your team already uses. Your data stays on your infrastructure; third-party calls use keys you choose. A zero-key demo is included.

Configure Firecrawl search and Spicrawl research.

See the workbench

The dashboard workbench runs on the native Go backend, with separate Companies and People, shared record history, Clay/CSV import mapping, and compact workspace navigation. Switch Light, Dark, System, and UI scale directly in the account menu. These recordings use fictional demo data. Build from main for this dashboard; published release tags may contain an earlier UI.

Inspect shared company facts, see its people, and follow a person's employment history without leaving the workbench.

Open the static dashboard screenshot.

Map source columns, check the row preview, and import into the record library. The preview keeps import and enrichment as separate actions.

Open the static dashboard screenshot.

Co-maintainer wanted

We're looking for a co-maintainer to help shape OpenGTM, review pull requests, ship releases, and build a faster enrichment backend. Experience with Go, PostgreSQL, browser automation, or provider integrations is especially welcome.

Interested? Join contributor and design-partner onboarding with a short introduction and the areas you'd like to own. Focused contributions are welcome too; start with CONTRIBUTING.md.

Run it

You need Git, Docker with Compose v2, and roughly 4 GB of available RAM. No provider key is required to try the demo.

On your laptop

macOS or Linux:

git clone https://github.com/debpalash/OpenGTM.git
cd OpenGTM
./scripts/install.sh

Windows PowerShell with Docker Desktop:

git clone https://github.com/debpalash/OpenGTM.git
Set-Location OpenGTM
.\scripts\install.ps1

Open http://localhost:3000. The first visit redirects to /setup: create the admin account there. The setup form asks for a one-time setup token, which the API prints once at startup (docker compose logs api-go | grep -i 'setup token'), or set SETUP_TOKEN in .env before the first start. No default admin account exists, and setup closes for good once an admin is created. The installer generates database, runtime-role, signing and service-token secrets, then starts the stack. It leaves an existing .env untouched.

On a server

Use a reviewed Go tag or commit. The example starts from main; replace OPENGTM_REF with your tested revision and record the resolved commit. Point a domain at the host and provide a TLS reverse proxy such as Caddy. On Linux with Git and Docker Compose:

OPENGTM_REF=main                 # replace with a tested Go tag or commit
git clone https://github.com/debpalash/OpenGTM.git
cd OpenGTM
git checkout "$OPENGTM_REF"
git rev-parse HEAD               # record this revision for rollback
./scripts/install.sh --no-start
DOMAIN=gtm.example.com                 # replace with your domain
cat >> .env <<EOF
APP_ENV=production
PORT=127.0.0.1:3000
CORS_ORIGINS=https://$DOMAIN
EOF
docker compose up -d --build

For Caddy, a site block is enough once DNS points at the server and ports 80/443 are open:

gtm.example.com {
    reverse_proxy 127.0.0.1:3000
}

Open https://gtm.example.com/setup and create the admin account (setup token: docker compose logs api-go | grep -i 'setup token'). Replace the example domain in both commands and Caddy config. The installer-generated secrets satisfy production startup checks; PORT=127.0.0.1:3000 keeps the bundled HTTP listener private. PostgreSQL, Redis, and the API bind to loopback or the internal Compose network. Set up backups and review the production checklist before inviting a team. Never expose port 3000 directly over the internet.

For a new release, fetch its tag, check it out and run docker compose up -d --build (the migrate service applies schema changes before the API starts). Keep the existing .env and Docker volumes when upgrading. The Docker guide explains the services and scaling.

Upgrade an existing Python installation

Take and verify a database and data-directory backup before cutover. The Go migration runner adopts the exact Alembic revision e7b2c4d6f8a0; older schemas must be upgraded with the previous Python release first. Drain Python workers, backfill pending jobs, and rehearse restoring the previous release before a production cutover. Follow the cutover runbook and migration guide.

Operate it

docker compose ps                         # service health
docker compose logs -f api-go worker-go   # follow requests and jobs
docker compose up -d --scale worker-go=4  # add capacity
docker compose down                       # stop without deleting data

Build from source

Needs Go, Bun and a Postgres/Redis (make up starts the compose stack). The web UI is embedded in the Go API binary, so one build gives one server:

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