Customers who skip the plan selection in the checkout can now 

change their plan later without restarting the flow

. This makes it easier to explore options and adjust decisions mid-checkout.

Skip configuration support for credit products

, the checkout flow now lets customers skip optional setup steps and complete checkout faster.

Customers can now choose how often they’re billed (e.g., monthly vs yearly) even when skipping other configuration steps.

The “credits remaining” indicator has been updated for better clarity and visual consistency. It’s easier to see how many credits a customer has left.

Users encountering long checkout forms will now be able to scroll reliably without layout issues.

Helpful hints and tooltips now appear reliably within modal dialogs, so customers don’t miss important context.

In development environments, Stripe is now mocked so unhandled errors don’t break the app — improving local testing and stability.

Minor fix to the setup example in docs so it reads correctly and avoids confusion during integration.

Accurate plan pricing shown in plan selector

Plan prices now consistently display in the plan UI, preventing confusion over what customers are about to purchase.

Pay-in-advance values retained on plan change

If a customer had entered a prepaid amount and then switched base plans, it could clear unexpectedly. This value now persists correctly.

Components 2.5

Replicator now starts up significantly faster thanks to asynchronous initial loading. Instead of waiting for a full data sync before responding to requests, Replicator serves data as it becomes available. This reduces cold start time (especially for large datasets) and makes local flag evaluation feel instant in high-throughput environments.

The Node SDK now supports configurable timeouts and fallback values. You can set a global or per-call timeout to ensure your app doesn’t hang waiting for a response. If a request fails or times out, the SDK will return a default value you define. This improves reliability and makes it easier to design safe failover behavior in degraded conditions.

Dev Tools Update January 2026

You can now enable scheduled downgrades at the catalog level. When enabled, any self-serve downgrade is deferred to the end of the current billing period, with no proration or credits, and customers keep full access until then.

Schematic represents the scheduled downgrade state consistently across API, webhooks, plan history, and UI. While a downgrade is scheduled, customers are blocked from buying add-ons, credits, or prepaying seats, but can resubscribe to a paid plan. Webhooks fire when a downgrade is scheduled and when it’s applied, and entitlement enforcement updates automatically at the effective date.

Scheduled Downgrade

Track feature consumption against plan limits over time so you can understand trends, anticipate overages, and spot anomalies early. Filter by feature and time range then hover to inspect precise values. This view gives teams a single place to monitor adoption against limits. 

Use it to inform pricing, communicate usage with customers, and coordinate upgrades. Go to any company’s usage tab to view your charts. Available today on all plans.

Feature Usage Over Time Charts

Components 2.4 is out and includes a lot of new features, take a look and upgrade!

Components 2.5

Dev Tools Update January 2026

Scheduled Downgrade

Feature Usage Over Time Charts

Components v2.4

Dev Tooling Updates 11/25

Component Updates 11/25

Monetization Updates 11/25

Schematic changelog

Components 2.5

Dev Tools Update January 2026

Scheduled Downgrade

Feature Usage Over Time Charts

Components v2.4

Dev Tooling Updates 11/25

Component Updates 11/25

Monetization Updates 11/25