Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: update pricing structure to add new core plan and teams add-on #1264

Open
wants to merge 15 commits into
base: main
Choose a base branch
from

Conversation

marcklingen
Copy link
Member

@marcklingen marcklingen commented Feb 8, 2025

Important

Updated pricing structure with a new "Core" plan and "Teams" add-on, modified rate limits, and added hover card and tooltip components for enhanced UI.

  • Pricing Structure:
    • Renamed "Pro" plan to "Core" and updated its features and pricing.
    • Introduced "Teams" add-on for the "Pro" plan with additional features.
    • Updated pricing details and features for "Hobby", "Core", "Pro", and "Enterprise" plans in Pricing.tsx.
  • Rate Limits:
    • Updated rate limits for various API endpoints in api-limits.mdx.
    • Added new rate limits for "Legacy Tracing" and "Metrics".
  • UI Components:
    • Added HoverCard and Tooltip components in hover-card.tsx and tooltip.tsx.
    • Integrated HoverCard for "Teams add-on" information in Pricing.tsx.
  • Dependencies:
    • Added @radix-ui/react-hover-card and @radix-ui/react-tooltip to package.json.

This description was created by Ellipsis for 2506933. It will automatically update as commits are pushed.

Copy link

vercel bot commented Feb 8, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
langfuse-docs ✅ Ready (Inspect) Visit Preview Feb 21, 2025 6:10pm

@dosubot dosubot bot added the size:L This PR changes 100-499 lines, ignoring generated files. label Feb 8, 2025
@marcklingen marcklingen changed the title chore: update pricing structure chore: update pricing structure to break out teams features into add-on Feb 8, 2025
>(({ className, align = "center", sideOffset = 4, ...props }, ref) => (
<HoverCardPrimitive.Content
ref={ref}
align={align as any}
Copy link
Contributor

Choose a reason for hiding this comment

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

Avoid using 'as any' for the align prop. Consider defining an explicit type or mapping for align to preserve type safety.

Suggested change
align={align as any}
align={align as "center" | "start" | "end"}

Copy link

github-actions bot commented Feb 9, 2025

📦 Next.js Bundle Analysis for langfuse-docs

This analysis was generated by the Next.js Bundle Analysis action. 🤖

Two Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page Size (compressed) First Load % of Budget (350 KB)
/pricing 49.69 KB 383.69 KB 109.62% (🟡 +1.45%)
/pricing-self-host 49.72 KB 383.71 KB 109.63% (🟡 +1.44%)
Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.

@marcklingen marcklingen changed the title chore: update pricing structure to break out teams features into add-on chore: update pricing structure to add new core plan and teams add-on Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size:L This PR changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant