Analytics and monitoring decision
June
The visible B2B product analytics loop is buildable, but a credible replacement needs more than the first screen. June earns its keep through ingestion, storage, reliability, so expect a weekend or multi-day build and a narrower personal scope.
Visit website↗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.
What a replacement has to do
- Build a narrow B2B product analytics collector for one site or app, ingest first-party events, and show a small set of decision-ready reports.
What it still won’t have
- enterprise governance and integrations
- bank, payment, tax, and reconciliation integrations
- high-volume ingestion and retention
- bot and identity resolution
- session replay privacy tooling
What remains hard
- Infrastructure at scale
- Execution quality
First-year cost
The build hours below are a category default, not an estimate for this product. Change them to your own numbers and the comparison follows.
No published price
June 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 deliberately narrow personal substitute for June, not a full clone. Use exactly this stack: Next.js 15 + TypeScript + ClickHouse + PostgreSQL. Primary job: Build a narrow B2B product analytics collector for one site or app, ingest first-party events, and show a small set of decision-ready reports. Start from an empty folder and create the complete working project. Make the default mode single-user and private. Store user data locally unless the core job requires the declared self-hosted database. Do not add analytics, telemetry, ads, or third-party accounts. Put every secret and external credential in .env and provide .env.example. Use realistic sample data that is clearly labelled and easy to delete. Implement the smallest polished interface that completes the core loop end to end. Include clear empty, loading, validation, success, and failure states. Add import and export so the user is not trapped in the app. Use accessible keyboard navigation, labels, focus states, and sensible contrast. Validate untrusted input and never log secrets or private file contents. Deliberately exclude these paid-product advantages: enterprise governance and integrations; bank, payment, tax, and reconciliation integrations; high-volume ingestion and retention. Do not fake integrations, network effects, proprietary data, model quality, compliance, or security claims. Where an external API is optional, keep the app useful without it and explain the degraded mode. Write focused unit tests for the data model and the most important workflow. Add one end-to-end smoke test that proves the core loop works. Create a README with setup, permissions, architecture, data location, backup, and limitations. Add scripts for install, development, test, build, and a production-style local run. Run the tests and build before finishing, then fix errors rather than merely describing them.
