How vinceanalytics/vince works
Vince is a self-hosted web analytics service. The principal workflow is browser tracking into the server, event processing and storage, then dashboard/API queries that return analytics. The README also documents administration, shared dashboards, TLS, and tracking capabilities. The excerpts establish API routing, query handling, aggregation, session middleware, and time-series persistence; event-ingestion wiring and several UI/runtime connections are not shown, so those links are marked unverified or omitted.
Main entry points: stats_api.go Statistics API · shard.go Sharded event store · run.go HTTP server · plausible.js Browser tracker
Components 19
Tracking and dashboard
- Browser tracker
tracker/src/plausible.js - Embedded assets
app/embed.go - Analytics dashboard
app/public/js/app.js
Server and access
- HTTP server
internal/cmd/run.go - Sessions and sharing
internal/web/db/sessions.go - Request middleware
internal/web/db/plug/pipeline.go - Site and API-key admin
internal/ops/system_operations.go
Analytics queries
- Statistics API
internal/api/stats_api.go - Query parsing
internal/web/query/query.go - Aggregate statistics
internal/api/aggregates/aggregates.go - Property breakdowns
internal/api/breakdown/breakdown.go - Time-series results
internal/api/timeseries/timeseries.go - Current visitors
internal/api/visitors/visitors.go
Event storage
- Event model
internal/models/event_model.go - Event batch writer
internal/timeseries/timeseries_batch.go - Sharded event store
internal/shards/shard.go - Geo enrichment
internal/geo/geo.go - Pebble database
Other components
- Site visitor
Connections 21
- Site visitor → Browser tracker: visits site
- Browser tracker → HTTP server: sends events
- HTTP server → Statistics API: routes requests
internal/cmd/run.go - HTTP server → Request middleware: wraps handlers
internal/cmd/run.go - Request middleware → Sessions and sharing: loads sessions
internal/web/db/plug/pipeline.go - Statistics API → Query parsing: parses parameters
internal/api/stats_api.go - Statistics API → Aggregate statistics: computes totals
internal/api/stats_api.go - Statistics API → Property breakdowns: computes breakdowns
internal/api/stats_api.go - Statistics API → Time-series results: requests series
internal/api/stats_api.go - Statistics API → Current visitors: requests visitors
internal/api/stats_api.go - Aggregate statistics → Sharded event store: reads event series
- Property breakdowns → Sharded event store: reads event series
- Time-series results → Sharded event store: reads event series
- Current visitors → Sharded event store: reads current data
- Analytics dashboard → HTTP server: requests dashboard data
- HTTP server → Site and API-key admin: configures operations
- Event model → Event batch writer: supplies event fields
- Event batch writer → Sharded event store: writes event batches
internal/timeseries/timeseries_batch.go - Sharded event store → Pebble database: persists shards
- Geo enrichment → Event model: enriches event data
- Embedded assets → Analytics dashboard: provides assets