We’ve expanded our webhook capabilities with a set of lifecycle events for the product entity, giving you deeper visibility and real-time automation around changes to your product catalog.

You can now subscribe to webhook events for:

• product.created – Triggered when a new product is created
• product.updated – Fired whenever product details are modified
• product.deleted – Sent when a product is removed

These events make it easy to:

• Keep internal systems (CRM, analytics, etc.) in sync
• Automate downstream workflows whenever products change
• Maintain a clean, up-to-date source of truth across your stack
• Build custom operational or go-to-market processes on top of product events

Whether you’re coordinating pricing updates, syncing product metadata, or triggering internal alerts—these lifecycle events give you full control.

You can learn more about these events and their payload in our webhook API reference.

We’ve expanded the flexibility of event-based meters with a new set of powerful filters that give you much finer control over how usage is counted.

You can now filter events using:

• Starts with
• Ends with
• Contains
• In (list of values)

These new operators make it easier than ever to measure usage based on specific attributes.

• Stigg Sidecar - running alongside your app or as a standalone service for low latency, resilient entitlement checks
• Persistent Cache Service - for streaming entitlement updates into your Redis storage
• Redis - for local storage when persistent cache is enabled
• An end-to-end example app - showing how all components work together

• A repeatable and production-ready way to deploy Stigg components on Kubernetes
• Built-in support for API key management, autoscaling, resource limits, and secure Redis communication
• Example manifests and templates that make it simple to integrate Stigg into existing workloads

1. Clone the stigg-helm-charts repo
2. Follow the instructions in README.md for either the Helm or the Kubectl + Kustomize deployments.

🔐 What changed

Stigg’s Snowflake integration now supports key pair authentication instead of username and password.
In this new flow, the public key is stored inside your Snowflake user configuration, and the private key is securely uploaded in Stigg.

This change ensures stronger security and aligns with Snowflake’s deprecation of username + password authentication.

💡 Why it matters

Snowflake is deprecating password-based authentication to strengthen account protection.
At Stigg, we have a deep sense for customer security and have therefore set key pair authentication as the default method for all new Snowflake integrations.

📦 Availability

• Default for all new Snowflake integrations.
• Existing customers can migrate to the new authentication method using the migration guide in our documentation.

⚙️ How to use it

1. Go to Integrations → Snowflake in your Stigg account.
   
   
   
2. Generate your key pair using the provided commands.
   
   
3. Add the public key to your Snowflake user configuration.
4. In Stigg, upload the private key (and optional passphrase) to connect.
   
   
5. To rotate keys later, upload a new private key and update the corresponding public key in Snowflake.

Full guide: Stigg documentation

We’re excited to announce the addition of new webhook events that give you greater visibility and control over your feature group lifecycle.

🆕  What’s New

You can now subscribe to the following webhook events:

• feature_group.created – Triggered when a new feature group is created.
• feature_group.updated – Triggered when changes are made to an existing feature group.
• feature_group.archived – Triggered when a feature group is archived.
• feature_group.un_archived – Triggered when a previously archived feature group is restored.

💡 Why It Matters

These new events enable you to:

• Keep external systems (dashboards, CRMs, analytics) in sync with your feature group activity.
• Automate workflows, such as notifying your team when new feature groups are created or monitoring changes to existing ones.
• Gain deeper observability into feature group lifecycle management.

📦 How to Get Started

• Head to the Integrations > Webhooks section in the Stigg app.
• Select the events you want to subscribe to.
• Start receiving real-time notifications for feature group activity.

We’re excited to announce that Zuora is now supported in the Stigg Checkout widget 🎉.

🆕 What’s New

• Seamless Zuora integration – Customers using Zuora can now process subscriptions directly through the Checkout widget, just like with other billing providers.
• No changes to the checkout experience – Your end-users continue to see the same familiar, streamlined flow — no code changes required.
• Multi-billing flexibility – Works seamlessly alongside Stigg’s multiple billing provider integration.
• Transparent migrations – Makes it easier to switch or migrate between billing providers without disrupting the checkout flow.

💡 Why It Matters

• Flexibility – Choose the billing provider that best fits your business without worrying about the checkout UI.
• Future-proofing – Easily support multiple billing providers as your business scales.
• Smoother migrations – Switch billing providers with zero impact on the customer-facing purchase experience.

📦 Availability

This functionality is supported in the latest versions of our SDKs:

• React: v6.11.0
• Vue: v5.3.0
• Embed: v6.3.0

🍿 See in action

👉 With Zuora support, Stigg Checkout gives you even more flexibility and peace of mind when managing billing across providers.

Managing large sets of features is critical as we scale upmarket and support enterprise-grade use cases. To make this easier, we’re introducing Feature Groups — a reusable way to organize, manage, and grant entitlements to groups of related features.

🔑 Why Feature Groups?

• Simplified management – Instead of handling hundreds of individual features, you can group them into logical sets.
• Consistency across plans – Ensure related features are always bundled and managed together.
• Faster packaging & updates – Grant, update, or revoke access to entire groups at once, rather than feature by feature.

🆕 What’s New

• Feature Group entity – Create, update, and archive groups of features. Each group has an ID, name, description, and list of features.
• Versioning – Feature Groups are versioned, making it easy to track and update changes across plans and add-ons.
• Plan & Add-on integration – Add entitlements by selecting a Feature Group; all included features are added automatically.
• Promotional entitlements – Grant promo access to entire groups just as you would with plans and add-ons.
• Visibility & management – See which groups a feature belongs to, update groups across environments, and export them to your data warehouse.

💡 Benefits

• Enterprise scalability – Handle hundreds of features with ease.
• Flexibility – A feature can belong to more than one group, supporting complex packaging needs.
• Transparency – Teams can see which entitlements belong to groups, and update plans/add-ons accordingly.
• Consistency – Version control ensures alignment across environments and plans.

📦 Availability

Managing feature groups is supported via the Stigg API.

Granting and revoking access to feature groups via promotional entitlements is supported in the latest versions of our SDKs:

• Node.js: v3.89.0
• Python / Ruby / Go / Java / .NET: v3.68.0
• Sidecar SDK: v3.72.0

🍿 See it in action

➡️ What's next

We’re adding dedicated webhook events to notify on creation, updates and archiving of feature groups — stay tuned!

👉 With Feature Groups, managing features at scale becomes simpler, faster, and more reliable — whether you’re bundling features into enterprise plans, granting promos, or aligning entitlements across environments.

We’ve added a generic getEntitlement() method to the Node.js SDK (v3.82.0) and Sidecar SDK (v3.56.0).

Previously available only in the Python, Ruby, Go, Java, and .NET SDKs, this functionality lets you check entitlements for any feature without knowing its type in advance (boolean, configuration, metered, etc.).

This makes it easier to integrate Stigg with proxy services that unify entitlements across legacy systems and Stigg, ensuring a smoother, more consistent developer experience.

We’re excited to announce a major upgrade to Stigg’s access management capabilities – you can now configure multiple domains for both Authorized Domains and Single Sign-On (SSO), allowing users across different domains to securely join your Stigg account. 

💡 Why It Matters

• Enterprise readiness – Perfect for organizations with multiple business units or subsidiaries using different domains.
• Centralized management – Streamlined identity and access management, all in one place.
• Seamless user experience – Authorized users log in quickly and securely, without repetitive setup.

⚙️ How to Get Started

1. Authorized Domains → In your Stigg account, go to Account Settings → Login Options → Add authorized domains.
2. Multi-Domain SSO → Work with your Stigg support contact to configure multiple IdP-managed domains.

This feature reflects our ongoing commitment to security, flexibility, and ease of use in enterprise access management.

We’ve updated Stigg's native integration with Stripe to give you more control and reliability when handling subscription cancellations.

What's new

• By default, when a paid subscription synced to Stripe is canceled, Stigg will now wait for Stripe's confirmation before marking the subscription as canceled in Stigg.
• This ensures tighter alignment between Stripe and Stigg, reducing the risk of mismatched states.
• Vendors who prefer to not wait for this confirmation can pass awaitSubscriptionCancellation: false when canceling subscriptions via the Stigg API or SDKs.

SDK Support

The new awaitSubscriptionCancellation parameter is supported in the latest versions of our SDKs:

• Node.js: v3.86.0
• Python / Ruby / Go / Java / .NET: v3.59.2
• Sidecar SDK: v3.61.0

What's next

We’re extending this functionality to Stigg’s Zuora integration — stay tuned!

See it in action