Clycyo
Roadmap & changelog · live

What we're shipping by end of April 2026.

Three explicit commitments below, dated. Below those, a log of what we just shipped, dated. We log regressions in this same place when they happen.

In flight · due 2026-04-30

See the docs entry →
Due 2026-04-30In progress

Data export — JSON + CSV

One-click export of pageviews, events, and visitor_identities for any website, scoped to a date range. Streamed download for >100k rows. Format: JSON Lines or CSV. The Postgres column set is already complete; the export job, the download endpoint, and the dashboard button are the work.

Due 2026-04-30In progress

Team accounts

Workspaces with multiple members. Replaces the current single-user model. Invitations by email, owner-transferable, with per-workspace billing seat. Existing single-user accounts will be migrated into a "Personal" workspace automatically; no link breaks, no re-onboarding.

Due 2026-04-30In progress

Per-person permissions

Owner / Admin / Editor / Viewer scopes per website inside a workspace, plus a read-only Stakeholder share link for board members and investors. Owner and Admin manage members and billing; Editor manages tracking and event names; Viewer reads only. The /open public demo is the precedent.

Shipped

  1. 2026-04-27

    Page-load time on every visit

    The tracker now reads PerformanceNavigationTiming on full loads and rAF-timed deltas on SPA route changes, and the visitor journey shows the load time next to every pageview. Aggregate avg + p75 are exposed at /api/public/demo.

  2. 2026-04-27

    Public read-only demo at /open

    The "View live demo" button now opens a real, live, read-only dashboard rendered against the actual clycyo.com analytics — no login, no mock data. Backed by /api/public/demo (cached 60s, aggregate-only).

  3. 2026-04-27

    clycyo.com tracks itself

    The marketing site now installs the standard tracker. Every metric on the home page and the /open demo comes from the same Postgres that powers customer dashboards.

  4. 2026-04-27

    Verified docs

    Revenue attribution and newsletter attribution now have end-to-end docs at /docs — both client-side and server-side paths, each tied to code that exists in production today.

Things we are intentionally not building
  • — Cross-site identifiers. We don't track users across sites.
  • — Session replay. Out of scope; privacy posture is a feature, not a bug.
  • — SDKs in seven languages on day one. We'll ship the TypeScript SDK first and grow from real usage.
  • — Sampling. We never silently drop your events. If you exceed your plan, we email — we don't throw away data.