We've made provisioning of subscriptions to paid plans more customizable by allowing Stigg app users to override the default charge prices.

This new change allows you to offer customers the same plans using different price points, while still leveraging Stigg for managing the subscription billing.

Overriding the default plan price is possible when provisioning and updating subscriptions in the Stigg app, by hovering on the relevant charges and selecting the "Edit price" action.

When the default plan price is overridden, an proper indication will appear next to the charge's price.

To apply the changes to the subscription, confirm the subscription provisioning.

We've added an ability to easily differentiate between single and multiple add-on types:

1. Single instance add-ons allow only 1 instance of the add-on to be included in customers' subscription. This type is useful for add-ons such as: single sign-on (SSO), premium support, Snowflake integration, etc.
2. Multiple instance add-ons allow multiple instances of the add-on to be included in customers' subscription. This type is useful for add-ons such as: additional API calls, additional credits, etc.

The add-on type can be defined when creating or updating an add-on.

We've extended the list of supported usage-based pricing models by adding support for the package pricing model.

In this pricing model customers are charged the same price per block of units.

In the below example, when customers make 500 API calls, they'll be charged the price amount for a block of 1000 API calls. Similarly, when they make 1500 API calls they'll be charge the price for 2 blocks of 1000 API calls.

Support has been added for both in-advance commitment and pay-as-you-go billing models.

To charge customers using a this pricing model, select the "Package" option from the pricing model drop-down menu.

Package pricing is supported in the Stigg Node.js SDK v3.20.0, Stigg Python SDK v1.102.0, Stigg Ruby SDK v1.102.0, Stigg Go SDK v1.102.0, Stigg Java SDK v1.102.0, Stigg React SDK v5.13.1 and Stigg JavaScript SDK v3.13.0 or later.

When customers are subscribed to plans with pay-as-you-go pricing, usage of pay-as-you-go charges is synced from Stigg to Stripe every hour.

To allow easy debugging of the integration with Stigg, we've added the ability to manually sync usage from Stigg to Stripe directly from the Stigg app. To do so, open the relevant subscription in the Stigg app and click on the the "Sync usage to Stripe" action.

We've made the ability to copy the configuration of an environment to new and existing environments more accessible by allowing users to do so directly from the environment picker.

Copying environment configurations allows users to easily push pricing and packaging changes between environments - we call it "Git for pricing changes". 

Click here to learn more about this capability.

We've add an ability to debug and troubleshoot usage events directly from the Stigg app by providing visibility for recently reported events via a usage event feed.

To access it, click on the "Usage events" item in the left navigation pane.

Clicking on a a specific event from the event feed will provide additional details about each event, including:

1. Idempotency key

2. Ingestion time

3. The customer that the usage event was attributed to (when relevant)

4. Full event data

More details about the usage event feed can be found here.

We've made it easier than ever to meter feature usage based on events that are currently reported to Google Cloud Platform (GCP) Pub/Sub. 

To do so, simply install Stigg's native Pub / Sub connector, map reported events to the Stigg event schema, and connect it to an event-based metered feature in Stigg.

More details about this new ingestion source can be found here.

We've extended the Stigg SDK for Python to support both Pydantic v1 and Pydantic v2.

With this change, customers can use the latest version of the Pydantic framework together with the Stigg SDK. Customers that currently use Pydnatic v1 can plan the migration to Pydnatic v2 knowing that Stigg supports both framework versions.

This enhancement is supported in the Stigg SDK for Python v1.97.1 and Stigg Sidecar SDK v1.98.3 or later.

We've extended the Stigg SDK and now support programmatic cancelation of paid subscriptions without granting customers credits for unused time.

In SaaS it's common to grant customers time or credits for unused time when they cancel their subscription; however, there are case where vendors would prefer not to do so. Examples include preventing abuse of a specific product feature, as well as migrations of subscriptions between 2 plans.

The new functionality is supported by the Stigg Node.js SDK v3.15.0, Stigg Python SDK v1.85.0, Stigg Ruby SDK v1.85.0, Stigg Go SDK v1.85.0, Stigg Java SDK v1.85.0 or later, as well as our API.

We're excited to announce our native integration with Salesforce, which streamlines sales processes by automating fine-grained provisioning of bespoke enterprise accounts directly from Salesforce. 

Example use-cases include provisioning of trial access during a POC, full access when an opportunity is won, or additional product access following contract amendments or renewals.

With this new integration you can:

1. Reduce time from opportunity close to account provisioned from hours and days to 0.
2. Ensure alignment between the customer's contract and the level of access that they were provisioned.
3. Leverage the same entitlement management and metering infrastructure for access enforcement and usage reporting regardless of how your product is sold - via self-service, sales-led, sales-assisted, or all of the above.

Stigg’s native integration with Salesforce removes the need for duct-taping and stitching together complex workflows and systems, such as tying together feature flags with an internal admin panel and your SF account.

Fine-grained entitlements and usage limits are accessible today, directly from Salesforce. Gone are the days of having to maintain and build homegrown workflows to allow that level of flexibility 💪.

More details about the integration can be found in our docs.