We’re excited to introduce enum-type configuration features — a powerful new way to model and enforce selectable options within your pricing and entitlement logic.

With the new enum type, you can now define predefined sets of values for configuration features, making it easier to represent use cases like:

• Allowed AI models (e.g., GPT-3.5, GPT-4, Claude)
• Support level (e.g., community, email, dedicated CS rep)
• Specific country access (e.g. US, UK, India)

🚀 Why it matters:

• 🧠 Adds structure to feature configurations with discrete value sets
• 🛡️ Reduces integration errors with validated values
• 🔄 Works seamlessly across SDKs, APIs, and the Stigg app
• 🔧 Enables more dynamic and granular packaging strategies

Enum-type configuration features bring even more flexibility and precision to how you define and manage entitlements in Stigg.

Enum-type configuration features are supported by the Stigg GraphQL API, Stigg Node.js SDK v3.72.0, Stigg Python/Ruby/Go/Java/.NET SDK v2.488.0, Stigg Sidecar SDK v2.485.0, Stigg JavaScript SDK v3.49.0 and the Stigg React SDK v6.4.0 or later.

We've extended our integration with Salesforce and have added the ability to trigger Stigg workflows directly from Salesforce.

With this change you can now implement custom monetization flows, such as granting additional entitlement access, all while leveraging Stigg Workflows' state-of-the-art debugging and troubleshooting capabilities.

To trigger a Stigg Workflow, simply add a Stigg "Trigger Workflow" node to your Salesforce Flow and pass the workflow's trigger ID and optional JSON payload.

Triggering Stigg workflows from Salesforce is supported in the Stigg app for Salesforce v1.6.0 or later. 

More details about Stigg's integration with Salesforce can be found here.

We’re excited to announce support for offline and air-gapped environments using the Stigg Sidecar!

With this change, you can now integrate Stigg in highly secure or isolated infrastructure setups without requiring a direct connection to the internet. To do so, simply enable offline mode in the Stigg Sidecar SDK.

When offline mode is enabled:

1. Entitlement evaluation is performed entirely in-memory using a predefined configuration. 

2. Usage and event reporting (reportUsage, reportEvents) are disabled.

Offline mode is ideal for:

1. Air-gapped deployments

2. Environments with restricted network access

3. Testing with predefined entitlement data

Offline mode is available in Stigg Sidecar SDK for Java v2.420.0 or later. 

We've updated the behavior of subscriptions that are billed using invoices - these subscription will now become active and their entitlements granted immediately upon creation. 

Before this change, entitlements were only granted once the first invoice was paid. 

Following this change, entitlement fulfillment of sales-led subscription is separated from invoice payment.

Self-service subscriptions remain unaffected - entitlements will only be granted after a successful payment.

The new behavior change is automatically applied to all new Stigg customers. Rollout to existing customers will be done gradually.

We've updated the pricing table widget to show the available add-ons in each plan! 🎉

Available add-ons are determined according to the plan's compatible add-ons configuration in the Stigg app, which can be modified using no-code. Add-on visibility can also be controlled using no-code at the add-on level.

Changes to the configuration of available add-ons are auto-magically reflected in the pricing table widget.

With this enhancement, upselling customers using add-ons has never been easier - whether it's access to a full fledged feature such as SSO or additional access to metered features such as AI tokens.

Visibility for add-ons in the pricing table widget is supported in the Stigg React SDK v6.0.0, Stigg Vue.js SDK v5.0.0 and the Stigg Embed SDK v6.0.0 or later.

We've extended our API and SDKs to allow retrieving of all of customers' subscriptions.

Before this change, it was only possible to retrieve active subscriptions of a specific customer.

Developers can now leverage the getSubscriptions() endpoint to retrieve scheduled, trial, pending payment, active, canceled and expired subscriptions, as well as filter results by customer, resource ID, and product. The results are paginated, supporting a large number of subscriptions.

The new endpoint is available via the Stigg API, Stigg SDK for Node.js v3.70.1, Stigg SDK for Python, Ruby, Go, Java and .NET v2.448.1 and Stigg SDK for JavaScript v3.42.0 or later.

We've made it easier to schedule future subscriptions to the end of the billing period via the Stigg app.

When creating new subscriptions, users can now select the start date of the subscription:

1. Immediately - preselected by default.
2. End of billing period - relevant when there’s already active subscription to a paid plan. 
3. Specific date - allows for creation of backdated (past) and future subscriptions. 

When a subscription is created with future start date, it will become active on that date.

More details about subscription provisioning via the Stigg app and subscription statuses can be found in our docs.

We’re excited to announce that Stigg is now SOC 1 Type II compliant, marking a significant milestone in our ongoing commitment to enterprise-grade trust and security.

This new certification demonstrates that Stigg’s controls relevant to financial reporting have been independently audited and found effective over time. It reinforces our dedication to serving customers with the highest standards of reliability and accountability.

This achievement adds to our existing compliance with SOC 2 Type II and ISO 27001, underscoring a robust, multi-layered security posture that meets the demands of even the most rigorous enterprise environments.

For more details, reach out to our team or visit our Trust Center.

We've extended the Salesforce integration to support provisioning of subscriptions to paid plans, including price overrides!

Before this change, it was only possible to leverage Salesforce for provisioning of subscription to custom plans, which granted customers with the relevant entitlements.

With this change, Stigg can serve as an abstraction layer for billing even when provisioning is initiated from Salesforce. Essentially, this allows SaaS companies to leverage Stigg for implementation of basic quote-to-cash (Q2C) flows in addition to their fulfillment.

We’re excited to announce the Stigg's AI provisioning and invoicing agent, an AI-powered agent that can transform signed quotes, contracts, or order forms into fully provisioned subscriptions and invoices—automatically handling even the most complex usage and billing scenarios.

💪 Benefits

• Speeds up post‑sale processes and accelerates time-to-revenue
• Reduces errors and eliminates manual data entry
• Maintains consistency across CRM, Stigg, and billing systems
• Empowers monetization flexibility without engineering overhead

📚 Example use-cases

• Custom entitlements - product sold in packages, but to close a deal, some entitlements are added or removed.
• Custom billing periods - product sold in annual contracts, but some customers require quarterly or semi-annual billing.
• Custom pricing models - some customers are billed a flat fee for their usage, while others are billed using tiered pricing or incur overage charges.
• Custom charges - some customers are billed for usage of Feature X, while others are billed based on usage of Feature Y.

⛑️ Safety first

Stigg’s AI agents are designed for high accuracy; however, agent misinterpretation can occasionally take place. Luckily, Stigg agents include a set of guardrails to mitigate risk and ensure control:

• Human-in-the-loop interaction lets teams review before provisioning
• Full traceability and auditability - all provisioned entities include an indication that they were provisioned by the AI agent

🎬 See it in action

🚚 Availability

AI-based provisioning and invoicing is currently in beta. To request access, please contact Stigg Support.

More details can be found in our docs.