The Java and Python SDKs now support the same real-time flag evaluation architecture already available in all published backend clients.

DataStream

Both SDKs now open a persistent WebSocket connection to Schematic on startup. When a flag check comes in, the SDK pulls the company data once, subscribes to future updates for that company-flag pair, and resolves all subsequent checks locally without an API call. Plan changes, override updates, and usage changes are pushed to the SDK in real time. Read more about DataStream and cross-platform SDK features.

Replicator

Both SDKs now support Replicator, which replicates all flag, company, and user data into your own infrastructure via a Schematic-provided container backed by Redis. Flag checks never leave your network. Updates propagate automatically, and your application continues operating from the local cache if Schematic is unreachable.

Optimistic Metric Updates

When the SDK processes a track event tied to a metered feature, it now optimistically increments the local usage count before the server confirms. Flag checks that depend on usage limits reflect the change immediately instead of waiting for the round trip. This closes a real gap for hard limits: if a customer has 3 of 5 API calls remaining and makes a request, the SDK knows they have 2 left without waiting for server confirmation.

SDK support matrix for DataStream and Replicator is now: Go, C#, Java, Python. Node.js is coming soon. See the full SDK support table for details.

Plans, add-ons, and all monetized entitlement types (pay-as-you-go, pay-in-advance, overages, tiered pricing, credit costs, and credit bundles) now support quarterly pricing. Quarterly follows the same patterns as yearly: if a plan has a quarterly period, quarterly prices must be defined for base charges and for any monetized entitlements.

Display priority across the UI and checkout components is Monthly > Quarterly > Annually. Entitlement reset periods are unchanged. Entitlements on quarterly plans still reset on their existing daily, weekly, or monthly cadence.

Angular teams can now integrate Schematic with a native SDK that fits Angular's dependency injection and service patterns. The SDK provides the same capabilities as the React and Vue SDKs: entitlement checks, flag evaluation, embedded components, and access to the full Schematic client.

Install via npm and see the Angular SDK docs for setup and usage.

The initial Stripe App launched as a sidebar panel on customer records. The full-page view expands the app into a standalone workspace inside Stripe where your team can see a richer home view with company state, entitlements, and usage at a glance. The full-page layout gives more room for workflows like managing overrides, reviewing usage against limits, and navigating between customers.

This is part of a continued investment in making Stripe the primary workspace for commercial teams managing entitlements. Install the app from the Stripe App Marketplace.

Previously, auto top-up configuration was admin-only. Now, when building a credit-based plan, you can choose whether top-ups are automatic (works as before) or user-controlled with defaults.

When set to user-controlled, end users see controls in the credit component to turn auto top-up on or off, set their own top-up threshold, and choose their top-up amount. The threshold is defined as a number of credits remaining (not a percentage), which makes behavior predictable regardless of how many credit bundles the customer has purchased. Admins set the defaults; end users adjust from there.

This gives your customers direct control over their spending without requiring support tickets or manual configuration changes.

Custom plans are now a first-class object in Schematic.

For sales-led deals, your team can create a plan tied to a single company with its own pricing, entitlement limits, metered billing rates, and billing terms. The workflow covers the full provisioning path: create the plan, define pricing and limits, set a billing period, configure an optional grace period, and send a payment link or invoice. Grace periods support fixed expiration, indefinite access, or access only after payment is received.

Once live, the custom plan becomes the source of truth for that customer's lifecycle. Usage tracking, overrides, credits, upgrades, and renewal data all flow through the same plan object. Engineering is out of the per-deal path after the initial integration.

Read the launch blog post for the full breakdown.

When a request fails, gets retried, or produces an error, you can submit a track event with a negative quantity to reverse the recorded usage. This works across all metered features, not just credits.

For credit burndown features specifically, reversed usage returns credits to the customer's balance via an adjustment grant. Adjustment grants accumulate across multiple corrections per company, are always consumed before plan grants or purchased credits, and carry a rolling one-year expiration that extends with each new adjustment.

Negative quantity events require a server-side secret API key (publishable keys cannot submit them) and generate negative usage records in the ledger for auditing. See the usage adjustments docs for implementation details and code examples.

Switch between light, dark, and system themes from the account menu. The sidebar has three modes: collapsed (icon-only), standard, and expanded.

Both preferences persist across sessions. No configuration required.