Analytics and monitoring decision
DataCity
A capable developer can build a useful, self-hosted analytics dashboard with a 3D visualization (multi-week effort), but reproducing the vendor polish, hosting convenience, and any commercial extras is non-trivial; existing open-source analytics projects (e.g., Umami, Plausible) cover most core analytics functionality.
Visit website↗Built by Marc Lou, who ships 32 products in this index
Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off50 h to build
$30/mo6 h/mo upkeep
No published price to break even against.
Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All DataCity alternatives, with the arithmetic →
What a replacement has to do
- Collect pageview and event hits → ingest via API key → store and aggregate events → render site-level metrics as a 3D city dashboard → let user browse, filter, and inspect event details.
What it still won’t have
- Hosted, maintenance-free infrastructure and uptime guarantees
- Polished, proprietary 3D visuals and UX tuning
- Any commercial support, demos, or onboarding provided by the vendor
- Built-in integrations or marketplaces the vendor may offer
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
DataCity does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal self-hosted analytics dashboard that visualizes site metrics as a simple 3D city. Tech stack: Next.js (React) for frontend, Node.js + Express for API, Postgres (or ClickHouse) for event storage, Three.js for 3D rendering, Docker for deployment, and DigitalOcean or similar for hosting. Core features in scope: (1) lightweight client tracking script that sends pageviews/events to the ingestion API; (2) ingestion API with API-key creation and validation, request logging, and basic rate limiting; (3) event schema and hourly/day rollups stored in Postgres (or ClickHouse) with background worker; (4) dashboard showing site-level metrics (visitors, pageviews, referrers) and a Three.js 3D city view where pages map to buildings sized by traffic; (5) simple account page to create/revoke API keys and view usage. Out of scope: multi-tenant billing, advanced segmentation, session replay, historical import connectors, and polished marketing UI. Include error handling, input validation, unit and integration tests for API and background jobs, and Docker compose for easy deployment.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 4 cited sources+3
- Evidence score60
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 4
Every page the run actually retrieved.
- official productDataCity — Your analytics as a 3D city
- official productDataCity product page snippet
- open sourceopenobserve/openobserve
- open sourcehyperdxio/hyperdx
Integrity checks
What held up, and what did not.
