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.

We’re thrilled to announce the launch of our brand-new documentation system — your new go-to source for everything you need to know to build, integrate, and innovate with us faster than ever before.

💡 What’s New?

• Smart Navigation — Redesigned layout that adapts to how you work.
• Lightning-Fast Search — Find exactly what you need, instantly.
• AI-Powered Assistance — Get contextual help without leaving the docs.

Check it out now: https://docs.stigg.io/ 

We're excited to announce that every Stigg environment can now be integrated with multiple billing providers at the same time!

The new functionality allows SaaS vendors to leverage Stigg as the single source of truth for their product catalog, customers, subscriptions, and entitlements while using different providers for billing.

Common use-cases include requirements to bill customers from different business entities (for example: for revenue recognition and tax purposes) and the need to support multiple billing providers as a result of merges and acquisition.

Whenever a billing provider is integrated with a Stigg environment, the Stigg product catalog is automatically synced to it. Vendors can then leverage Stigg's SDKs, API and user interface to route customers and subscriptions to the relevant billing provider. When no explicit routing is specified, customers and subscriptions will be created in the billing provider that's designated as the "default".

Beyond managing multiple billing providers, this new functionality makes migration between billing providers easier than ever. To do so, start by changing the default billing provider to route all new customers and subscription to the new provider. Then, follow a simple procedure to migrate existing entities.

The new feature is supported by the Stigg Node.js SDK v3.63.0, Stigg Python SDK v2.331.1, Stigg Ruby SDK v2.331.1, Stigg Go SDK v2.331.1, Stigg Java SDK v2.331.1, Stigg C# SDK v2.331.1, Stigg Sidecar SDK 2.337.0, and Stigg JavaScript SDK v3.37.0 or later.

More details can be found in our docs.

We've added an ability for team members to automatically join a Stigg account using an authorized email domain. Users outside of the company can still join the account if needed via an explicit invitation. 

To enable this configuration, navigate to the Account Settings > Login options tab, under "access method" select "Authorized domain" and the relevant domain from the list.

The new configuration natively integrates with Stigg's role-based access control (RBAC) capabilities - team members that join the Stigg account are granted a default role and level of environment access.

Allowing users to automatically join a Stigg account using an authorized domain is available as part of Stigg's Scale plan. 

More details about the available login options can be found in our docs.

We've added the ability to schedule syncing of subscription metadata to integrated billing providers. Before this change, syncing of metadata to billing providers occurred immediately even if the actual change to the subscription was scheduled to take place at a later date.

Syncing metadata to billing providers can be helpful when when there are existing BI reports that rely on information from the billing provider. Integrating Stigg with billing providers allows you to leverage existing reporting capabilities.

To sync subscription metadata to integrated billing providers, pass the billingInformation.metadata property when calling provisionSubscription or updateSubscription. To schedule the sync, also pass the scheduleStrategy property.

The new behavior is supported by all existing SDK versions - no changes are required.