Launchdarkly

Guardian went from a plan card to a paid add-on priced separately. Its own card ('Everything in Enterprise, plus', custom pricing, 'Get custom pricing' button) is gone and it now sits inside the Enterprise card as 'Paid add-on'; its column in the compare table was dropped and four compare rows are marked 'Guardian only'. The CodeControl / AgentControl / Full Platform track selector was removed: the Developer, Foundation and Enterprise cards now show directly under the page heading, and Guardian no longer has a card of its own.

Per-unit observability overage prices removed from the compare table: the Session Replays row ('Starts at $3.50/1k sessions'), the Errors row ('$0.30/1k per month') and the Traces and Logs rows ('$1.50/1M per month') no longer appear, and no per-unit observability overage price is listed anywhere else on the page. The $5 per 1k AI runs line and the 'Overage behavior $5 / 1000' row remain. Compare-table Service Connections row reworded: '$12/mo per service connection' is now 'SC-based billing'. The Client-side MAU row remains as '$10 / mo per 1K MAU' and the Foundation card still shows its rates.

Pricing page restructured around a CodeControl vs AgentControl product split (plus a combined 'Full Platform' option): a track selector now sits above the plans, with Full Platform preselected, so all four plans show by default. Foundation billing display went from a monthly-default 'Billed Monthly / Billed Yearly' toggle to a yearly-default 'Billed yearly' switch; monthly rates are unchanged and not removed, so this is not a price cut. A new AgentControl usage line of $5 per 1k AI runs past 5k a month was added on Foundation, with custom runs on Enterprise.

Quarterly roll-up · includes 4 weeklies

New 'AI & Agentic Access' section added to the feature comparison table with MCP Server available on all plans (Developer, Foundation, Enterprise, Guardian).

Enterprise and Guardian plans updated: description changed from 'Custom / Contact us for more information' to 'Custom pricing / Tailored pricing based on usage and licensing needs'; CTA changed from 'Contact us' to 'Get custom pricing'.

Release Assistant feature removed from the Enterprise plan. It no longer appears in the Enterprise plan card or in the full feature comparison table.

Developer plan descriptor changed from 'Pay only when you exceed Developer tier limits.' to 'No credit card required', emphasizing easier entry.

Quarterly roll-up · includes Jan 26 weekly

Developer plan tagline changed from 'Pay only when you exceed Developer tier limits.' to 'No credit card required', emphasizing ease of signup.

Developer plan now includes 5K Session Replays and Errors per month as a defined limit Traces add-on introduced starting at $1.50 per 1M per month

Client-side MAU pricing in comparison table decreased from $12/mo per 1K to $10/mo per 1K (17% decrease). Service Connections stay at $12/mo. Foundation now quotes separate rates for the two metrics and opens on yearly billing (before: "$12 per Service Connection or 1k client-side MAU", Monthly). The $10 Service Connection figure is the yearly rate (MAU yearly is $8.33); the monthly Service Connection rate is unchanged, still $12.

Foundation plan experimentation add-on pricing decreased from $33/mo per 10k experimentation keys ($333/yr) to $3/mo per 1k experimentation MAU Experimentation metric changed from 'experimentation keys' to 'experimentation MAU' across all tiers

Terminology changed from 'contexts' to 'client-side MAU' (Monthly Active Users) throughout pricing page and feature descriptions Release monitoring renamed to Release Assistant in Enterprise plan

Pricing model changed from per-seat ($8.33-$16.67/seat/month) to usage-based ($12/mo per service connection or 1K contexts) Foundation plan introduced at $12/mo for 1 monthly service connection or 1K monthly contexts

Client-side usage metric renamed from 'Client-side MAUS' (Monthly Active Users) to 'Client-side Contexts' to reflect broader targeting model supporting users, devices, accounts, and other entity types Data Export add-on availability explicitly shown in Pro plan features (marked as 'available')