Pulse Intelligence
6.8#2 in threat intelligence platformsFree planFree planWebAPILinuxmacOS
VisitPulse Intelligence vs Yeti
What both publish
| Fact | Pulse Intelligence | Yeti |
|---|---|---|
| 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. |
Pulse Intelligence plans
- Open-source self-hostedFree
Yeti plans
No prices published.
Pick Pulse Intelligence if…
Pulse Intelligence suits analysts, junior CTI teams, and SOC teams seeking a self-hosted threat intelligence workspace. It is intended for teams able to operate the required Node.js, PostgreSQL, and Redis-compatible services.
Pick Yeti if…
Yeti suits DFIR and CTI teams managing shared threat data, forensic artifacts, and automated analysis. It is aimed at organizations able to operate a Docker-based self-hosted deployment.