We've extended the plan and add-on entitlement configuration to support yearly reset periods. When enabled, Stigg will automatically reset reported customer usage for the relevant feature every year according to the customer's subscription start date.
The new configuration joins the monthly, weekly, daily and hourly reset periods that were already available beforehand.
We've added the ability to programmatically provision subscriptions in a free trial using the Stigg SDKs and API. Doing so allows you to implement custom user journeys, such as granting customers a free trial to higher tiers when they reach a certain achievement.
Programmatic provisioning of trial subscriptions overrides the default trial configuration in the Stigg app UI, which can be edited using no-code.
To force the provisioning of a subscription in a free trial, pass the TrialOverrideConfigurationInput parameter to the provisionSubscription method. To extend an existing trial, pass the trialEndDate parameter to the updateSubscription method.
The new functionality is supported in the Stigg Node.js SDK v2.46.0, Stigg Python SDK v0.712.0, Stigg Ruby SDK v0.712.0, Stigg Go SDK v0.712.0, Stigg Java SDK v0.712.0 or later, as well as via the GraphQL API.
We've extended Stigg's price localization capabilities and now support usage-based pricing with tiered volume discounts.
With this latest update you can now offer volume discounts to customers in different countries at price points that align with customers' purchasing power in those geographies.
More details about Stigg's price localization capabilities can be found here.
We've added the ability for multiple child plans of a product to inherit from the same base plan. With this change, re-using entitlements is easier than ever.
As always, publishing entitlements changes to a base plan will be automatically reflected in child plans.
To learn more about plan entitlement inheritance, click here.
Ensuring that customers are granted the precise level of access they pay for is a fundamental part of every pricing and packaging infrastructure.
Doing so with low latency, high availability and at scale is a challenge that must not be taken lightly. Example obstacles include the need to synchronize customer usage and entitlements across multiple microservices in real-time, low latency from anywhere in the world, and the ability to define a default level of access when there are connectivity issues.
Luckily, the Stigg platform provides functionality out of the box, and today we’re excited to announce that leveraging the full power of the Stigg platform is now easier than ever with the Stigg Sidecar.
Previously exclusive to Node.js, applications written in Python, Ruby, Go, and Java can now also benefit from Stigg's persistent caching mechanism, entitlement access from the edge and built-in fallback strategy for high availability and scale.
This means that you can now enjoy lightning-fast ⚡entitlement checks at scale regardless of your application’s architecture (monolith, microservices or serverless) or language it's written in.
More details about the Stigg Sidecar can be found in our documentation.
Applying changes to pricing and packaging is an absolute must as your product evolves.
Luckily, Stigg makes the rollout of such changes easy - they immediately take effect in new subscriptions, and you have the choice between grandfathering existing subscriptions or applying the changes to them too.
When applied to existing subscriptions, a migration process ensures that the changes are reflected in customers’ accounts. For companies with tens of millions of subscribers, this can take a long time.
We've completely redesigned the subscription migration pipeline from the ground up. The new pipeline boasts a massive 100X improvement from the previous implementation - up from 200K subscriptions to 20M subscriptions per hour!
We’ve invested a lot of thought and hard work to ensure that our platform sustains vendors with a HUGE customer base. Click here to learn more.
We're excited to announce our integration with the AWS Marketplace! 🎉
Stigg's native integration with the AWS Marketplace allows you to leverage the same entitlement management and metering infrastructure for access enforcement and usage reporting regardless of where your product is listed (on your public website or the AWS Marketplace) or how your customers are billed (via AWS or other billing solution).
The integration with the AWS Marketplace is currently available in beta for select customers. To access it, please contact Stigg Support.
More details can be found in our docs.
We've updated the payload of the subscription.canceled webhook to include details as to why the subscription was canceled, for example: due to failed payment or a user-initiated action.
The new functionality allows you to trigger workflows to prevent customer churn.
More details about the subscription.canceled event can be found here.
We've made it easier for customers with a Java backend to get up and running with Stigg by leveraging the Stigg Java SDK.
The initial version of the Java SDK serves as a wrapper around Stigg's GraphQL API - caching, polling or streaming of customer entitlements is not currently supported, but will be available soon.
More details on how Stigg can be integrated into your Java application can be found here.
We've added the ability to archive features to which you no longer want to grant new access.
When a feature is archived:
To archive a feature, use the "Archive" action in the context menu of the specific feature.
More details about archiving features can be found here.