We've updated the Stigg React and JavaScript SDKs to fully support server-side rendering.

When using frameworks that perform server-side rendering (SSR), such as Next.js, this allows you to embed the Stigg React widgets as-is.

Full SSR support is available in the Stigg React and JavaScript SDKs from version 0.2.1 or later.

More details about the integration of Stigg when using Next.js can be found here.

We've made the currently selected environment persistent. The new improvement allows you to pick up your work when logging in again from the same browser.

When changes to the plans add-ons are rollout out only to new subscriptions (for example: when changing their price), grandfathering takes place.

To prevent a SKU sprawl, Stigg allows you to manually migrate each subscription to the latest plan and add-on version.

We've now extended our APIs to allow you to programmatically schedule the migration to take place at the end of the customer's current billing period, in addition to being able to trigger the migration immediately.

The new functionality is supported by the Stigg Node.js SDK v1.17.0 and our GraphQL API.

Support in the Stigg Console UI is also planned.

We've increased the precision of prices that can be defined in the Stigg platform. Prices can now be defined with up to 5 decimal points; thus, allowing you to bill customers for their usage with higher granularity.

Once defined, the prices are auto-magically reflected in all of the Stigg widgets, and when Stigg is integrated with a billing solution, prices are automatically synced to it.

Stigg's API and SDKs allow you to show customers a preview of the estimated subscription cost before provisioning or updating a subscription, for example: as part of a checkout or confirmation flow.

When Stigg is integrated with a billing solution, the response of the estimateSubscription and estimateSubscriptionUpdate calls now include information about the estimated tax fees, which can be presented to your customers. This includes:

1. Tax name - i.e. NJ Sales Tax

2. Tax amount

3. The tax percentage rate

4. Whether the tax is inclusive or exclusive to the subscription price

5. The prorated cost that's due now - with and without tax

6. The recurring subscription price - with and without tax

The enriched response is available in the Stigg Node.js SDK v1.15 and the Stigg JavaScript SDK v1.36.0 or later.

We've made it easier for users to focus on customers' currently active subscriptions by hiding inactive subscriptions from the customer details screen by default.

Want to view canceled subscriptions in order to determine the subscription history? No problem! 

Use the toggle in the top-right corner of the Customer details -> Subscriptions section to control the show or hide canceled subscriptions as needed. 

The subscriptions will be ordered according to start and dates. 

Subscriptions of products that allow multiple active subscriptions will be grouped according to the provided resource ID.

We've made it easier to determine the current feature usage and available entitlements of an active subscription, by allowing users to access this information directly from the subscription details screen, in addition to the previous access from the customer details screen.

We've made it easier to navigate through the different Stigg platform sections even when the left navigation bar is collapsed.

By leveraging the improved user experience you can now collapse the left navigation bar as you work with the Stigg platform and have more space for managing your packaging and pricing, while still being able to quickly jump between different sections as needed.

Collapsing the navigation bar is possible by clicking on the '<<' icon. Uncollapsing it is possible by hovering on the Stigg logo in the top-left corner and clicking on the '>>' icon.

Menu items with sub-sections will appear with a '>' indication. Clicking on these items will open a menu with the relevant sub-sections, which you the relevant sub-section will then open it.

When customers can provision multiple instances of your product, it's possible to monetize each instance separately. 

Common use cases include products that represent a website (i.e. Wix, HotJar) or an application. Each website or application can have a subscription to a different tier while allowing the customer to pay for all of their subscriptions using the same payment method.

Different sub-accounts and user roles can also be monetized using a similar method.

We're excited to share that Stigg now offers the flexibility to monetize your product using this pricing model.

Using Stigg you can now:

1. Easily provision multiple subscriptions for your product

2. Track feature usage in each subscription

3. Gate feature access in each subscription according to defined limits

4. Offer a self-served in-app upgrade experience using snap-in widgets

5. Bill your customers using a billing solution of your choice that's integrated with Stigg

In addition, you can combine products that customers can have a single subscription for together with a product that has multiple subscriptions and implement even more complex pricing models, such as monetization according to account + sub-accounts or platform + apps. 

More details about how all of this can be achieved can be found here.

We've extended our API and SDKs and now support 2 methods for reporting the usage of metered features:

1. Reporting of the usage change (delta) - for example: +A when A seats are provisioned, and -B when B seats are de-provisioned.

2. Setting the usage value - for example: C where C is the current seat count. This new reporting method is useful when the entitlement usage is calculated or aggregated by another data source.

To set the usage value, pass the updateBehavior.set property when reporting measurements.

Setting the calculated usage value is supported in the Stigg Node.js SDK v1.13.0 and Stigg Python SDK v0.5.0 or later.

More details can be found here.