Skip to content

Standardize pricing + wire real Analytics/Usage pages#15

Merged
hallelx2 merged 1 commit into
mainfrom
feat/pricing-analytics-usage-pages
Jul 3, 2026
Merged

Standardize pricing + wire real Analytics/Usage pages#15
hallelx2 merged 1 commit into
mainfrom
feat/pricing-analytics-usage-pages

Conversation

@hallelx2

@hallelx2 hallelx2 commented Jul 3, 2026

Copy link
Copy Markdown
Owner

@

What

Front-end for two asks: standardized pricing and functional Analytics/Usage pages. Pairs with control-plane PR #2 (the endpoints these consume).

Pricing — one source of truth

lib/pricing.ts now defines the canonical ladder (free / pro / scale / enterprise) with the agreed numbers — Pro $29 / 500 docs / 20 GB, Scale $99 / 5,000 docs / 100 GB. Both the marketing Pricing section and the dashboard billing page render from it, so the site, the app, and the CP quota plans can no longer drift. Adds the Scale tier + a 4-up grid.

Analytics + Usage — real data (were fully mocked)

  • GET /api/dashboard/analytics and GET /api/dashboard/usage proxy to the CP analytics + quota endpoints for the callers org.
  • Analytics: live summary (total requests, success rate, avg latency, tokens), usage-by-source breakdown, daily request-volume chart, and a recent-calls feed with per-request source attribution.
  • Usage: real quota meters (queries / documents / tokens), usage-by-source bars, and plan ceilings from lib/pricing.ts.
  • lib/usage-sources.ts gives web / sdk / mcp / api consistent labels + colours (no purple, per brand).

Verification

  • tsc --noEmit clean.
    @

@
Standardize pricing + wire real Analytics/Usage pages

Pricing: new lib/pricing.ts is the single source of truth for the tier
ladder (free/pro/scale/enterprise) with the agreed numbers (pro 500
docs/20 GB, scale $99 5,000 docs/100 GB). The marketing Pricing section
and the dashboard billing page both render from it, so the site, the
app, and the CP quota plans can no longer drift. Adds the Scale tier and
a 4-up grid on both surfaces.

Analytics + Usage (were fully mocked): both pages now fetch real data.
- /api/dashboard/analytics and /api/dashboard/usage proxy to the CP
  analytics + quota endpoints for the caller org.
- Analytics: live summary (requests, success rate, avg latency, tokens),
  usage-by-source breakdown, daily request-volume chart, and a recent-
  calls feed with per-request source attribution.
- Usage: real quota meters (queries / documents / tokens), usage-by-
  source bars, and plan ceilings derived from lib/pricing.ts.
- lib/usage-sources.ts gives web/sdk/mcp/api consistent labels + colours
  (no purple, per brand).
@

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry @hallelx2, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

@vercel

vercel Bot commented Jul 3, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
vectorless-web Ready Ready Preview, Comment Jul 3, 2026 11:54pm

@coderabbitai

coderabbitai Bot commented Jul 3, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@hallelx2, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 39 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 82af4085-ec27-4ed5-9299-34f944cf61a1

📥 Commits

Reviewing files that changed from the base of the PR and between b30b0ee and 682889e.

📒 Files selected for processing (9)
  • apps/web/app/(dashboard)/dashboard/analytics/page.tsx
  • apps/web/app/(dashboard)/dashboard/billing/page.tsx
  • apps/web/app/(dashboard)/dashboard/usage/page.tsx
  • apps/web/app/api/dashboard/analytics/route.ts
  • apps/web/app/api/dashboard/analytics/usage/route.ts
  • apps/web/app/api/dashboard/usage/route.ts
  • apps/web/components/Pricing.tsx
  • apps/web/lib/pricing.ts
  • apps/web/lib/usage-sources.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/pricing-analytics-usage-pages

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@hallelx2 hallelx2 merged commit 1b9733a into main Jul 3, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant