Raccoon

6.0easy start · #20 of 24
in Event Tracking Software

Runs on api, self-hosted.

Raccoon is ranked #20 of 24 in event tracking software on The Geeks Club. It runs on API, Self-hosted.

Compared on event tracking software

SnowcatCloud 0 of 4 in the starter kit Lesson 18.2 Jitsu 0 of 4 in the starter kit Lesson 28.1 Stape 0 of 4 in the starter kit Lesson 37.9 RudderStack Customer Data Platform 0 of 4 in the starter kit Lesson 47.8 SetRoasFlow 0 of 4 in the starter kit Lesson 57.1 walkerOS 0 of 4 in the starter kit Lesson 67.1

Purpose: Raccoon ingests event data from mobile apps, websites, and services, then publishes it to message queues for stream processing.
Protocols and formats: Clients can send events over WebSocket, REST, or gRPC; WebSocket and REST support JSON and Protocol Buffers, while gRPC supports Protocol Buffers.
Destinations: Supported message queues are Apache Kafka (stable), Google Cloud Pub/Sub (alpha), and AWS Kinesis Data Streams (alpha).
Delivery acknowledgments: The server acknowledges delivery successes and failures; the documentation says it can be augmented for zero-data-loss or at-least-once guarantees.
Monitoring: Raccoon supports StatsD and Prometheus telemetry, and its built-in monitoring includes latency and active connections.
Deployment: The maker documents running Raccoon with Docker and deploying it on Kubernetes, including a Helm chart.
Security limitation: Raccoon does not provide application-level HTTPS or authentication; the deployment guide suggests using an API gateway or separate authentication service.
Intended use: Documented use cases include clickstream collection, adtech streams, IoT edge systems, and event sourcing.
License: The GitHub repository states that Raccoon is licensed under Apache 2.0.

Claim it for free: prove the domain, then correct facts, plans and screenshots. An editor reviews every change.