Open Enrich vs OpenGTM
Open Enrich
github.comOpenGTM
github.comSide by side
| Figure | Open Enrich | OpenGTM |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | Yes |
| Web | Yes | Yes |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 0 | 2 |
| Spec score · Data Enrichment Software | 7.3 (#29) | 8.4 (#11) |
| Integrations | The README describes Salesforce and HubSpot export mappings, plus Google Sheets, TSV, and JSON export. | Documented destinations include HubSpot, Salesforce, Slack, Google Sheets, Airtable, Instantly, Smartlead, webhooks, warehouses, and consent-gated ad audiences. |
| License | The project is released under the MIT License. | The software is released under the GNU Affero General Public License version 3.0. |
Plans
In their own words
Open Enrich
Open Enrich has no write-up on Specifiction yet; its figures are above.
OpenGTM
OpenGTM is an open-source, self-hosted workspace for go-to-market teams and their agents. It handles lead sourcing and enrichment, AI research with cited answers, buying-intent tracking and sending qualified records to other tools. Workbooks combine imports, formulas, HTTP columns, enrichment waterfalls, AI research and output columns, with estimated spend visible before runs. Teams can segment live audiences, monitor hiring and buying signals, and schedule refreshes and automations. Listed activation destinations include HubSpot, Salesforce, Slack, Sheets, Airtable, Instantly, Smartlead, webhooks, warehouses and consent-gated ad audiences. The workspace is also available through REST, webhooks and an auditable MCP server with scoped read and write access. The project says data remains on the user's infrastructure and external calls use provider keys selected by the user. Teams can set workbook budgets to stop paid calls at a ceiling, although provider charges may apply. The software is free under AGPL-3.0. Installation requires Git, Docker with Compose v2 and roughly 4 GB of RAM. The project is pre-1.0; public multi-tenant hosting needs further work beyond team-controlled Compose deployment.