Pulse Intelligence vs Yeti
Pulse Intelligence
github.comYeti
yeti-platform.ioSide by side
| Figure | Pulse Intelligence | Yeti |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | Yes |
| Windows | Yes | — |
| macOS | Yes | — |
| Linux | Yes | — |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 0 |
| Spec score · Threat Intelligence Platforms | 8.4 (#3) | 6.7 (#27) |
| API | The public API is read-only, supports scoped API keys, and is intended for analyst scripts, SOAR playbooks, internal tools, and integrations. | Yeti provides a REST API, including endpoints for importing observables from text, files, and URLs. |
| Deployment | The maker documents direct Node deployment and a Docker Compose full-stack deployment, with both the web app and worker kept running. | The documented supported installation method uses dedicated Docker containers and requires Git, Docker, and the Docker Compose plugin. |
| Enrichment | It enriches indicators through OTX, AbuseIPDB, and VirusTotal, with Redis-backed quota controls. | The documentation gives VirusTotal data enrichment as an analytics example and says analytics can be extended with private scripts. |
| Integrations | Its public read-only API supports scoped keys and integrations such as analyst scripts, SOAR playbooks, and internal tools. | Yeti describes exporting data in user-defined formats for ingestion by third-party SIEM and DFIR applications. |
| Purpose | Pulse Intelligence is an open-source, self-hosted threat intelligence workspace for analysts and junior CTI teams. | Yeti describes itself as a Forensics Intelligence platform and pipeline for DFIR teams, intended to bridge CTI and DFIR practitioners. |
Plans
In their own words
Pulse Intelligence
Pulse Intelligence is an open-source, self-hosted threat intelligence workspace for analyst workflows. It organizes threat actors, aliases, campaigns, indicators, reports, sources, CVEs and ATT&CK mappings, and ingests public feeds including CISA KEV, NVD, FIRST EPSS, abuse.ch, OTX, vendor blogs and security news. Indicator enrichment uses OTX, AbuseIPDB and VirusTotal, with Redis-backed quota controls. Analysts can save hunts across indicator fields, receive alerts for new matches and export results as CSV, STIX 2.1, MISP JSON, or Snort and Suricata rules. Scheduled Markdown reports can cover new indicators, KEV additions, hunt alerts and feed health. A public read-only API with scoped keys supports integrations; its default limit is 120 requests per API key per 60-second window, and indicator pages are capped at 500. The project lists Argon2id passwords, database-backed session cookies, hashed API keys and an admin-only audit log. Deployment requires Node.js 20.9+, PostgreSQL 17 or compatible PostgreSQL, and a Redis-compatible server. Native and Docker Compose deployment paths are documented.