We are excited to announce that Stigg is now available as a SaaS listing on AWS Marketplace.

This allows teams to discover, procure, and deploy Stigg directly through their AWS account.

💡 Why This Matters

• Simplified Procurement: Buy Stigg using existing AWS Marketplace workflows.
• Centralized Billing: Consolidate Stigg charges into your AWS bill.
• Faster Adoption: Reduce legal, finance, and vendor onboarding friction.

🛠 Get started

• Open the Stigg listing on AWS Marketplace.
• Subscribe using your AWS account.
• Complete onboarding in Stigg.

We are excited to announce a new security capability for the Stigg Frontend SDK: Configurable Token Expiration for Client-Side Hardening.

This feature builds upon our Client-Side Hardening (HMAC verification), allowing you to define a specific validity window for your customer tokens.

🆕 What’s New

You can now include an expiration timestamp field (exp) within the customer token to set the desired expiration session expiration time.

💡 Why This Matters

• Reduced Attack Surface: Limit the lifespan of client-side credentials.
• Compliance: Meet strict internal security requirements for token rotation and expiration.
• Granular Control: Choose an expiration window that fits your app’s session length (e.g., 15 minutes, 1 hour, or 24 hours).

🛠 Get started

To configure the expiration period, update your backend token generation logic to include the new expiration field.

Check out the updated Hardening Documentation to see full implementation details for your preferred language.

🆕 What’s New

We added the ability to import Zuora catalogs to Stigg.

• Keep Zuora as the source of truth: Imported plans are automatically marked as "Synced." This ensures Stigg treats Zuora as the master source of truth and prevents accidental overwrites of your billing data.
• Mirror Zuora Structure: The import replicates your Zuora hierarchy in Stigg. It maps Zuora Products to Stigg Products and Zuora Rate Plans to Stigg Plans, preserving your exact billing structure.

💡 Why This Matters

You can now import your existing product catalog from Zuora to Stigg with just a few lines of code.

This allows you to adopt Stigg without restructuring your billing catalog. You can manage entitlements in Stigg while maintaining the exact product and rate plan structure your finance team relies on in Zuora.

🛠 Get Started

Clone our import script repository and follow the instructions in the Readme file.

We’re introducing support for connecting your non-production environments directly to Stripe Sandbox accounts.

While Stigg has always supported Stripe's Test Mode, Sandboxes offer a "new flavor" of testing environment with distinct capabilities, providing greater isolation and flexibility for your billing workflows.

🆕 What’s New

You can now connect Stigg directly to a Stripe Sandbox, unlocking advanced testing capabilities that go beyond standard Test Mode.

• Distinct from Test Mode: Sandboxes are separate environments that allow you to isolate settings completely from your live integration. Unlike Test Mode, where some settings are shared with Live Mode, Sandboxes ensure total separation.
• Enhanced Flexibility: Leverage Stripe’s Sandbox capabilities such as creating up to five separate environments, granular access control for team members, and independent setting configurations.

For a deep dive into the differences between Test Mode and Sandboxes, check out Stripe’s documentation.

💡 Why This Matters

• True Isolation: Eliminate the risk of accidental changes to production. Since Sandboxes don't share settings with Live Mode, you can test complex pricing models and billing flows without fear of "leaking" configuration changes.
• Better Staging Parity: Mirror your production setup more accurately by copying settings from live mode at creation time, then testing independently.
• Granular Access: Invite developers or QA members specifically to a Sandbox environment without granting them permissions to your live Stripe account.

🛠 Get Started

To connect a Stripe Sandbox account:

1. In the Stigg app, go to Settings > Integrations > Apps.
2. Select the Stripe connector.
3. Toggle "Use Stripe test account" on.
4. Click "Connect with Stripe".
5. Follow the prompts to authorize and select your desired Stripe Sandbox account.

For more details on setting up the integration, visit our documentation.

We’re rolling out a set of powerful enhancements to the Checkout Widget, giving you more control over customization, behavior, and integration with your product’s purchasing flow.

🆕 What’s New

1. New Callback Support

You can now hook into key user interactions throughout the checkout flow using three new callbacks:

• onBillableFeatureChange - triggered when the value of plan's billable features (charges) changes
• onAddonChange - triggered when an add-on is added, removed, or updated
• onBeforeStepChange - invoked before the widget transitions between checkout steps

These callbacks give you deeper insight into user intent and allow for advanced analytics, validation, and UI coordination.

2. Add-on Visibility Configuration

The checkout widget now fully honors your add-on visibility rules.

You decide which add-ons are shown are shown to customers in Stigg widgets and the widget automatically enforces your configuration.

3. Support for Add-on Types

The widget now respects whether an add-on is:

• Single-instance (can be added once), or
• Multiple-instance (users can add multiple units)

This ensures that your packaging and purchasing rules are represented accurately in the UI.

4. Add-on Billing Period

The widget will now automatically hide add-ons that don't support the selected billing period.

5. Annual Prices in Summary

Prices in the summary will now appear in an annual format (e.g. $100.00 / year) when the selected plan only supports an annual billing period.

📦 Availability

These improvements are now available in the latest SDKs:

• React: v7.12.0
• Vue: v5.7.0
• Embed: v6.7.0

Ending trials using the Stigg app UI now takes effect instantly.

Once a trial ends, the subscription immediately transitions to the next applicable state (e.g., downgrade to a free plan, revoke entitlements, or convert to a paid subscription).

This updated behavior provides a more predictable and consistent user experience.

We’re excited to share that you can now configure credit top-ups and consumption within recurring paid plans.

🆕 What’s New

When creating or editing a recurring paid plan you can now:

• Define the credit currency that customers will able to top-up
• Map metered features to their credit consumption rate

Under-the-hood the new configuration leverages all of the constructs that we introduced as part of our support for prepaid credits, including: custom credit currencies, credit pools, credit grants and credit ledgers.

Credits (promotional or paid) can be granted to customers using the below methods:

• Programmatically via the Stigg API
• Through Stigg Workflows
• Directly in the Stigg App

💡 Why This Matters

Credits have become the standard for monetizing AI and other variable-cost features - they make usage predictable for customers and provide finance and product teams with a transparent, auditable, and scalable model.

This new functionality expands Stigg existing support for hybrid pricing models and allows you to extend your existing subscription-based offerings with with usage-based features that are monetized using credits.

🛠 Get Started

You can start configuring credit top-ups and consumption of paid plans in the Stigg app.

🍿 See It In Action

🔮 Coming Up Next - Recurring Credit Grants

To extend this even further, we’re planning to introduce Recurring Credit Grants - a powerful new capability that will allow you to automate ongoing credit issuance throughout the subscription lifecycle. Stay tuned!

🆕 What's New

You can now customize the number of skeleton plan loaders displayed while the Stigg Pricing Table widget is loading. This allows you to better align the loading state with your plan layout and create a smoother visual experience.

To configure it, simply set the new skeletonCount option when initializing the widget.

📦 Availability

• React SDK: v7.10.0
• Vue SDK: v5.6.0
• Embed SDK v6.6.0

🍿 See It In Action

We've made improvements to the infrastructure and scale of usage event ingestion from AWS S3, making it even easier than ever to migrate data, backfill usage, or integrate with complex data pipelines.

🌟 Feature Recap

Usage event ingestion from S3 allows you to:

• Ingest usage events directly from AWS S3 - Import raw usage events from a supported AWS S3 without building custom ingestion pipelines.
• Backfill historical usage at scale - Load months or even years of past events to support migrations, billing transitions, or customer onboarding.
• Sync of large volumes of events - Perfect for workloads that generate usage asynchronously, in batches, or from data processing pipelines.
• Leverage Stigg existing metering capabilities - Once ingested, events affect metering, consumption, entitlements, and credit burn without extra setup.

💡 Why This Matters

Our metering API is provisioned for 1000 events per second, which covers most workloads.  

For extremely high-volume cases, our infrastructure can scale beyond 100,000 events per second and process terabytes of data by using a bring-your-own-bucket object storage setup with dedicated ingestion channels and isolated storage capacity.

Until now, turning such high volume data into billable usage required custom ETL jobs, scripts, or fragile data plumbing.

With this capability, you can:

• Accelerate migrations from legacy billing or metering systems
• Unify real-time and batch usage under a single metering logic
• Reduce engineering overhead by eliminating custom ingestion code
• Trust Stigg to handle processing and enrichment of events
• Ensure billing accuracy even when usage is delayed or generated in bulk

📦 Availability

Usage Event Ingestion from AWS S3 is available to all customers of the Scale plan. See Stigg's pricing for more details.

🛠 Get Started

Full documentation and integration guides are available here.

We’re excited to announce expanded capabilities in Stigg Workflows - you can now provision and update subscriptions that include multiple billable features, add-ons, and variable entitlements in a single, streamlined flow.

This unlocks a more flexible and scalable way to automate complex subscription lifecycles.

🆕 What’s New

It's now possible to pass multiple values in a single Workflow action when provisioning and updating subscriptions using Stigg workflows, including:

1. Billable features of paid plans
2. Add-ons
3. Variable entitlements of custom plans

💡 Why This Matters

• Simplicity - reduces the number of required actions and significantly simplifies workflow complexity
• Atomicity - ensures that all updates take place at once.

📦 Availability

The new subscription provisioning and updates action nodes are now available to all Stigg customers using Workflows.