Stigg's mission is to create a reliable and highly available solution that won't interrupt the mission-critical functionality of your application. To make sure that the critical paths are not affected, we have a few guardrails in place.

In the case where the entitlement local data is missing (for example: when a new feature is added to the codebase, but has still not been added to a plan) or our API is unreachable (for example: during a drop of internet connectivity), fallback values can be configured using the Stigg SDKs. 

We've extended the entitlement-check fallback strategy configuration, and now allow developers to define a global fallback strategy during the SDK initialization. 

The new configuration is supported in the Stigg Node.js SDK v0.76.0, Stigg JavaScript SDK v1.13.2 and Stigg React SDK v1.12.0 and later.

We're excited to share the general availability of support for persistent entitlement caching using Redis in the Stigg Node.js SDK.

By default, the Node.js SDK caches entitlement data in-memory to reduce the latency on subsequent entitlement checks. This approach is usually suffice when only one process or service is responsible for accessing the entitlement data.

By configuring the Node.js SDK to leverage a Redis server for caching, entitlement data becomes persistent, is synchronized even when accessed by multiple services and processes, and survives restarts. 

Persistent caching can also greatly reduce the latency of entitlement checks in application that leverage a serverless infrastructure, where each process is transient and can be de-provisioned after a limited period of time.

Persistent caching using Redis is supported by the Stigg Node.js SDK v0.7.5 or later. To enable it, please contact the Stigg Support Team.

More details about Stigg's persistent caching implementation can be found here.

As part of Stigg's support for scheduling downgrades when they're initiated by customers in a self-served manner, we've extended the Stigg Customer Portal widget to notify customers about the scheduled updates.

Using the updated widget, customers can also cancel the scheduled update and stay on the higher-priced plan.

The new change allows you to introduce a full-blown self-served SaaS subscription experience using only a few lines of codes. 

Communication of scheduled updates using the Stigg Customer Portal widget is available in the Stigg React SDK from version 1.11.1, the Stigg Vue 3 SDK from version 0.5.2, the Stigg Vue 2 SDK from version 0.0.6, and the Stigg JavaScript SDK from version v1.13.1.

We've extended our support for applications built using the Vue.js framework, and now not only support Vue 3 applications, but also Vue 2 applications.

Embedding Stigg's self-service component into Vue 2 application is possible by installing Stigg Vue 2 SDK. 

More details about the Vue.js SDKs and its integration can be found here.

We've added an ability to store custom metadata on Features.

To do so, open the Features screen from the left navigation pane and select the relevant features. Under the "Metadata" tab, click on the "+ Add" button and add the custom metadata.

To edit the defined metadata, click on the "Edit" button.

Accessing the feature metadata is possible using the getPaywall() method.

Metadata for features is supported by the Stigg Node.js SDK v0.70.0 or later and Stigg JavaScript SDK v1.11.0 or later.

We've add an ability to filter the customer list in the Stigg Console according to plan price (free, paid or custom) and the subscription status (active, in trial, etc.).

The new functionality allows you to focus on the customers that you care about most, for example: paying customers, customers on a custom plan, customers that are in a trial.

Viewing and filtering your customers is available when clicking on the "Customers" tab in the left navigation pane.

We've significantly reduced the latency of entitlement checks that are performed using the Stigg Node.js SDK.

We've extended our integration with Stripe, and allow you to collect your customers' tax ID during checkout. The tax ID is collect and stored directly in Stripe.

To collect the tax ID, simply pass the allowTaxIdCollection: true parameter to the provisionSubscription() method.

The new functionality is supported in the Stigg SDK for Node.js v0.68.0 or later.

With ever-growing competition in SaaS, you’ll need to provide seamless experiences to your buyers and full flexibility in updating their subscription.

The behavior of your Product's subscription downgrade logic has implications both on your customer experience and business.

At Stigg, we aim to make pricing decisions flexible and allow you to choose between 2 SaaS best-practices:

1. Downgrade immediately and grant credits for the remaining time of the billing period (like Slack and Notion), which is considered more "fair" from the customer's perspective. This is also the default behavior for Products in Stigg.
2. Schedule a downgrade to take place at the end of the current billing period (like Zoom, Trello, and GitHub), which is considered less favorable to your business, because it results in a loss of revenue. Scheduled downgrades can be canceled by customers in a self-served manner, as well as by users that have access to the Stigg Console.

To change the default behavior, contact the Stigg Support Team. An ability to control this configuration in a self-served manner is also planned 😎

Subscriptions that have a scheduled update will have a proper indication under the Customer details > Subscriptions section and Subscription details screens:

Details about the scheduled updates is available under the Subscription details screen:

More details about Stigg's subscription update behavior can be found here.

We've made it easier than ever to copy the IDs of Stigg entities - simplify click on the ID field to copy it. 

The new user experience further streamlines the integration of Stigg into your codebase and third-party applications.