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.

We've extended the Sidecar service to expose metrics, including:

• Total number of initialization errors
• Total number of invalid API key errors
• Total number of network errors
• Total number of persistent cache hits
• Total number of persistent cache misses
• Total number of persistent cache errors

The metrics are helpful for monitoring the health and performance of the Sidecar service, and can be visualized in any Prometheus-compatible observability (such as Graphana).

The metrics are available in the Sidecar docker image v2.401.4 or later. 

More details can be found here.

We’re excited to introduce Workflows — a powerful low-code engine that lets you automate complex monetization flows using a visual drag‑and‑drop editor.

Workflows empowers product, growth, and engineering teams to own and iterate on monetization flows end-to-end, significantly reducing engineering cycles and accelerating time-to-market.

Example use-cases include:

• Granting additional entitlement access based on customer actions
• Automatically upgrading subscriptions when customers exceed their committed usage
• Automatic trial extension based on usage consumption
• Semi-automatic approval flows for subscription changes
• Internal alerts about trial expiration, subscription changes and usage consumption
• Customer-facing notifications about trial expiration and usage consumption

Using workflows you can:

• Create automated flows by connecting Trigger, Condition, and Action nodes on a canvas — visually intuitive and easy to master.
• Perform actions on the Stigg platform and in 400+ other applications, such as Salesforce, SendGrid and Slack — or run custom HTTP requests and code.
• Leverage LLMs to build AI-assisted flows.
• Monitor, troubleshoot and debug flow executions.
• Test, launch, and iterate on monetization flows — no deployment required.

All this, while keeping all monetization logic within Stigg for consistency, auditing, and simplified maintenance.

Workflows are currently in beta. To request access, please contact Stigg Support.

More details can be found in our docs.

We’re excited to announce the launch of our new GraphQL API reference — a comprehensive, developer-friendly resource that puts every query, mutation, type, and field right at your fingertips.

💡 What’s Inside?

• ✅ Complete Schema Coverage — Every endpoint, object, input, and enum is now fully documented.
• 📝 Detailed Descriptions — Clear explanations for every type and field, so you know exactly what to use and when.
• 💬 Example Queries & Use Cases — Learn by example and build faster.

With this change developers that integrate Stigg using the GraphQL API can get up and running much faster.

The new GraphQL API reference is available here. Interaction with the GraphQL API is also available using the GraphQL API Playground.

In addition, Stigg offers native backend and frontend SDKs that can further simplify the integration with Stigg, and also support automatic retries, access from Edge, caching and fallback values.