LIVE_FEED
Real-time visitor tracking
Stream raw visitor data as it happens with zero latency. No polling, just persistent live transport.
Real-time observability
See users live
on the map in real time.
Drop in one script and see active sessions pulse across a living map. Built for teams that want signal now, not dashboard archaeology later.
Background shows the live visitor map widget in real time.
Everything you need, nothing you don't.
Obsidian-grade analytics that prioritize clarity over complexity.
VISUAL_ENGINE
Live world map visualization
Render global activity with a sharp, low-noise visual layer instead of a crowded analytics cockpit.
PERF_METRICS
Lightweight and fast
Built to stay out of the way, with a minimal client footprint and a direct path to live insight.
DEV_READY
Simple script integration
One script tag, fast setup, and no buried configuration before you can see traffic move.
EMBED_WIDGETS
Embeddable live widgets
Drop map and chart widgets into your site to share live traffic without rebuilding the UI yourself.
Pricing & limits
Pick the tier that fits your live traffic shape.
These plans are generated from the shared limit configuration used by Livedot itself, so the page reflects the actual site, event volume, retention, and history ceilings defined in code.
Cloud
Free
$0 no charge
A lightweight cloud tier for one site.
Use it to try the live map, validate setup, and monitor one property with short retention.
- 1 website
- 10,000 events per month
- 10 minutes of live traffic
Cloud
Pro
$2.99/mo billed monthly
More headroom for growing products.
Built for teams that need higher event volume, deeper retention, and room for a few sites.
- 5 websites
- 100,000 events per month
- 1 day of live traffic
Cloud
Max
$4.99/mo billed monthly
High-capacity limits for larger traffic.
Built for teams monitoring more sites, higher event volume, and a full week of live traffic.
- 20 websites
- 1,000,000 events per month
- 7 days of live traffic
What is an event?
One visitor session equals one event.
Each unique visitor to your site counts as a single event, no matter how long they stay. Custom interactions tracked with data-livedot-event each count as one additional event. Bots, failed requests, and repeat beacons from the same session do not count.
Need self-hosting?
Community
Run Livedot on your own infrastructure and manage the limits, retention, and deployment shape yourself.
View on GitHub
DEPLOYMENT
Up and running in seconds.
Livedot is designed for developers who value speed. Self-host with total data sovereignty using an optimized Docker image and a setup path that stays short.
Docker Source Code
1
docker run -d \
2
-p 5500:80 \
3
-v ./data:/data \
4
ghcr.io/mxvsh/livedot
FAQ
Questions teams ask before they ship.
Enough detail to evaluate the product quickly, without turning the page into a knowledge base.
What is Livedot? +
Livedot is a lightweight real-time monitoring tool that visualizes live user activity across a world map so teams can see traffic patterns as they happen.
How do I install Livedot? +
You can deploy Livedot with a Docker container, run it in Kubernetes, or use a standalone binary depending on your hosting setup.
Is Livedot self-hosted? +
Yes. Livedot is designed to be self-hosted so you keep control of your data and can run it in your own infrastructure with a simple Docker-based setup.
Is Livedot an analytics tool replacement? +
No. Livedot is built for real-time monitoring, not as a replacement for full analytics platforms. It helps you watch live activity as it happens, while your broader analytics stack can continue handling historical reporting and deeper analysis.
Does Livedot require a complex setup? +
No. The core setup stays minimal: one script integration, a lightweight client footprint, and fast access to live user signals.
What counts as an event? +
Each unique visitor session counts as one event, regardless of how long they stay on your site. Custom interactions tracked with the data-livedot-event attribute each count as one additional event. Bots, failed requests, and repeat beacons from the same session do not count.