Replace June?

KINDA · weekend project
catalog price reference variescategory 📊 analyticsreported replacement votes 0

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.

the 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.

$ open in your agent (prompt prefilled, you press enter) or copy it raw · this prompt is generated from the build plan · improve it via PR

why people still pay

June: Customers pay for trusted numbers, retention, privacy controls, and a pipeline that remains accurate while traffic and schemas change.

what you lose

xenterprise governance and integrations

xbank, payment, tax, and reconciliation integrations

xhigh-volume ingestion and retention

xbot and identity resolution

xsession replay privacy tooling

prior art to inspect before buildingMatomoMature self-hosted web analytics platform.PostHogOpen-source product analytics, feature flags, and session replay.
reported replacements · 0share on X ↗"June replacement research and build prompt"
questions
What does the June verdict mean?

The core job looks buildable, with meaningful gaps: enterprise governance and integrations, bank, payment, tax, and reconciliation integrations. Read the full tradeoff list before committing. This research record is not a hosted IVCIFY tool.

What price does this directory record show for June?

June's pricing is usage-based or varies by plan. The official pricing URL is recorded, but a stable current amount was not safely recoverable in this pass. Do not publish a number until rechecked..

What do I lose by replacing June?

Honestly: enterprise governance and integrations; bank, payment, tax, and reconciliation integrations; high-volume ingestion and retention; bot and identity resolution; session replay privacy tooling. If any of those are load-bearing for you, keep paying.

Is there an open-source alternative to June?

The listed prior art includes Matomo (Mature self-hosted web analytics platform.), PostHog (Open-source product analytics, feature flags, and session replay.). Inspect those projects before starting from a blank prompt.