Stigg has long provided ultra-low latency entitlement checks and fail-safe resilience when using our GraphQL-based SDKs. Today, we’re bringing those exact same high-availability features to developers integrating via REST!

With this release, customers leveraging REST-based SDKs can now benefit from < 10ms latency when performing entitlement checks by proxying requests through the Stigg Sidecar service.

🆕 What’s new?

REST-based SDKs can now benefit from the following:

• Sidecar Support: Install and deploy the Stigg Sidecar to proxy requests directly from REST-based SDKs.
• In-Memory & Persistent Caching: Configure the Sidecar service with a Redis instance to persistently cache entitlement and usage data locally across multiple nodes, or utilize out-of-the-box in-memory caching.
• Global Fallback Strategy: Configure the Sidecar service with a global fallback strategy for entitlement evaluations, ensuring default access rules apply even when data isn't cached.
• Offline Mode: Configure the Sidecar service to work in offline mode for local development and testing, allowing you to bypass Stigg API network requests entirely.

💡 Why it matters

• Sub-10ms Latency: REST API users can now resolve entitlement evaluations instantly from a local memory or Redis cache, reducing check latencies to under 10ms.
• Fail-Safe Resilience: Gain full offline resilience for your REST integrations. The Sidecar is engineered to keep serving entitlements even when the Stigg API is unreachable or network errors occur - serving cached entitlements, or fallback values for uncached ones.
• Streamlined Testing: With offline mode enabled, the Sidecar skips API key validation and limits entitlement evaluations strictly to your defined fallback values, turning other service methods into no-ops. This makes isolated testing and local development fast and predictable.

⚒️ Get started

1. Deploy the Stigg Sidecar as a shared service or alongside your main host application.
2. Provide your Sidecar deployment with connection details for your Redis instance to enable persistent caching, and/or configure default access rules using the ENTITLEMENTS_FALLBACK environment variable.
3. Update the configuration of the Stigg REST SDK to route requests through the local Sidecar proxy.

For detailed architecture diagrams and deployment instructions, check out our Stigg Sidecar Documentation.

📦 Availability

• REST is supported in the Sidecar service from v8.1.1 or later.
• Persistent caching is available for customers on the Stigg Scale plan.

We;ve moved the credit configuration out of the Plan price wizard and into a brand-new, dedicated section directly within the Plan details screen.

This architectural update was implemented to make it seamless to update and roll out credit changes to your entire customer base at scale, operating exactly like our existing entitlement rollouts.

🆕 What’s new?

• Dedicated Credit Configuration Section: The setup for feature-to-credit mapping and default top-up pricing has been decoupled from the Plan price wizard. It now lives in its own prominent, standalone section on the Plan details screen.
• Mass Subscription Rollouts: You can now roll out changes to a plan's credit configuration across millions of active subscriptions simultaneously. Whether you are adjusting how many credits a feature costs or modifying the default top-up price, propagating these updates to your users is now effortless. Any updates you roll out will only affect credit grants and deductions that take place after the change is successfully published.

💡 Why it matters

• Effortless Scalability: Managing and iterating on credit-based pricing models for a massive user base is now significantly easier. Update your credit mappings once and push them to all your subscriptions without breaking a sweat.
• Improved Visibility & Organization: Giving credit configuration its own dedicated space keeps your workspace organized, making it much faster to view, understand, and adjust how credits are consumed within your plans.

ℹ️ Important note on rollouts

Please note that changes to a feature’s price in credits and default top-up pricing are not retroactive. 

⚒️ Where to find it

1. In the Stigg app, navigate to your Plans and select any existing plan.
2. Instead of opening the Price Wizard, look directly at the Plan details screen.
3. Scroll down to locate the new, dedicated Credit configuration section to view, edit, and roll out your feature-to-credit mapping and top-up pricing!

🍿 See it in action 

Integrating Stigg into your existing data stack just got significantly faster and more flexible. We’re excited to introduce our new, upgraded data export pipeline - expanding support far beyond Snowflake and BigQuery to nearly 20 new destinations, paired with granular control over sync schedules, entity selection, and monitoring!

At Stigg, we believe you should always have full, seamless ownership of your data. This update makes it easier than ever to bring Stigg data directly into your warehouse, data lake, operational database, or storage layer without complex custom ETLs.

🆕 What’s new?

1. 22 New Supported Destinations

You are no longer limited to Snowflake and BigQuery. Stigg now supports native exports to:

• Data Warehouses & Lakes: Databricks, Amazon Redshift, Amazon Redshift Serverless, ClickHouse, Amazon Athena, SingleStore, Delta Lake
• Relational & NoSQL Databases: PostgreSQL, MySQL, Microsoft SQL Server, Oracle, Amazon Aurora (PostgreSQL & MySQL), MongoDB, MotherDuck
• Cloud Storage & Files: Amazon S3, S3-compatible storage, Google Cloud Storage (GCS), Azure Blob Storage, Apache Iceberg, SFTP, Google Sheets

2. Flexible Sync Scheduling & Custom Frequencies

Take control over when your data updates. Choose your sync frequency (every 1-24 hours), or trigger an immediate manual sync at any time with a single click in the Stigg app.

3. Entity Customization

Choose exactly which Stigg entity groups sync to your destination (Customer Data, Product Catalog, and Usage Tracking). Keep your schemas clean and export only the data your team needs.

4. Real-Time Sync Monitoring & Visibility

Track the status, progress, and history of every sync run in real-time without refreshing the page:

• Determine exact timestamps and status (Successful vs. Failed) for the last sync.
• Drill down into error logs, sync durations, total rows transferred per entity, and whether the run was automated or triggered manually.

💡 Why it matters

• Seamless Stack Integration: Connect Stigg directly to your existing data infrastructure without needing intermediate data pipelines.
• Operational Control: Tailor export workloads to fit your warehouse costs and reporting cadences by selecting specific entities and scheduling custom sync frequencies.
• Troubleshooting Transparency: Instantly verify sync health and diagnose errors directly within the Stigg dashboard without digging through external system logs.

⚒️ Get started

1. In the Stigg app, navigate to the Integrations > Apps section and click on + Add.
2. Under the Data export section, select your desired destination, and follow the setup instructions.
3. Select the Stigg entities you want to export and set your preferred sync schedule.
4. Click Sync Now to run an initial sync immediately and view real-time progress in the history tab!

For detailed setup instructions and schema details, check out our Data Export Documentation.

📦 Availability

• New Customers: Available immediately to all new customers on the Scale and BYOC plans.
• Existing Customers: Our team will be reaching out and working closely with existing Snowflake and BigQuery integration users to ensure a smooth migration to the new pipeline.

🍿 See it in action

You can now manage your custom, sales-led enterprise agreements entirely through conversation. We're excited to introduce the stigg-contracts AI agent skill, designed to let you handle complex contract workflows using simple, natural language.

🆕 What’s new?

With the new stigg-contracts skill, your AI agent can process and manage contract-based agreements directly from your prompts.

Here is what you can now do using everyday language:

• Flexible Contract Creation: Tell the AI exactly how you want to structure a new deal. You can instruct it to provision access only, set up billing only (with negotiated terms and custom pricing), or handle both simultaneously.
• Full Lifecycle Management: Simply ask the agent to attach or detach subscriptions, process amendments and renewals, archive old contracts, refresh usage, or pull up a customer's existing contracts and invoices.

💡 Why it matters

• Zero-Click Workflow: Ditch the manual UI navigation. Send the order form to the AI agent, and it will configure custom pricing, attach subscriptions, and generate invoices for you without requiring a single click.
• Set up enterprise entitlements & invoicing in minutes: Streamline your sales-led processes by turning complex order forms into active billing contracts in less than 5 minutes.
• Accelerate Operations: Effortlessly bridge the gap between a signed deal and active software provisioning by simply typing out exactly what you need.

⚒️ Get started

1. Configure your AI environment to use Stigg

2. Send the agent your signed order form and tell it to "Provision the contract in Stigg"

3. Review the changes, make adjustments if necessary

4. Let the agent do the heavy lifting!

We are excited to announce a new enhancement to our Contract Management workflow: you can now download PDF copies of invoices directly from created contracts!

🆕 What’s new?

You can now retrieve the generated PDF billing documents without ever leaving Stigg. Whether you need to quickly share an invoice with your finance team, hand it off to a customer for a manual wire transfer, or just maintain a paper trail for a highly customized enterprise agreement, you have the exact document ready at your fingertips.

⚒️ Get started

When viewing an active contract that includes invoice generation, navigate to the invoices section of that contract. Next to any successfully generated invoice, simply click the Download PDF icon to save a local copy of the document.

Want to learn more about how to replace custom spreadsheets and unify your enterprise entitlements and invoicing? Check out our Contract Management Overview.

🍿 See it in action

Expanding globally often means managing localized pricing for numerous countries. For the Eurozone - 21 member states sharing the Euro (EUR) - maintaining separate pricing configurations for every single country can be tedious, repetitive, and prone to errors.

We're excited to announce Unified Eurozone Pricing, a streamlined way to handle price localization for countries that pay in EUR!

🆕 What’s new?

Stigg now supports a dedicated eu country code (labeled European Union with an EU flag in the Stigg app) that can be used to represent the Eurozone as a single region:

• Unified Eurozone Region: Configure a single EUR price for most Eurozone countries instead of adding and maintaining the exact same price 21 times.
• Full Developer Control Over Mapping: Matching a billingCountryCode to a localized price is a simple, predictable exact string comparison. This puts the power entirely in your codebase. You decide exactly which countries are grouped together by maintaining your own list of Eurozone country codes and mapping them to "EU" before passing the parameter to Stigg's widgets (Paywall, Checkout, Customer Portal) or APIs.
• Flexible Granularity: Any country you don't explicitly map to the "EU" code in your application simply keeps its own default or distinct localized price.

💡 Why it matters

• Reduced Maintenance: Say goodbye to the operational overhead of managing duplicate price rows for Austria, Germany, France, Italy, and 17 other member states.
• Faster Rollouts: Update your EUR pricing strategy across the entire region with a single change.
• Ultimate Control: You decide exactly which countries are grouped together. You can easily pull a specific country out of the "EU" mapping later if you decide to charge a different localized price for that specific market.

⚒️ Get started

1. Navigate to the Stigg app and add a new localized price using the European Union (EU) region to your plans or add-ons.
2. In your application's country-resolution logic (via GeoIP, billing address, or preference), maintain a list of Eurozone ISO codes.
3. If a customer's actual country code is in that list, map it to eu.
4. Pass eu as the billingCountryCode on relevant API calls or Snap-in widgets.
5. To move existing subscribers from individual per-country pricing to the unified EU price, follow our step-by-step consolidation guide.

To learn more about setting up unified EUR pricing, code snippets, and how to safely migrate existing customers, check out our Serving countries that pay in EUR Documentation.

📦 Availability

Unified Eurozone Pricing is available now to all Stigg customers using Price Localization.

🍿 See it in action

We've significantly reduced the latency of entitlement checks, active subscriptions and pricing tables queries that are performed using the Stigg Go SDK.

The performance improvement leverages Stigg's high availability and accessible from anywhere architecture - behind the scenes, the data is accessed from 200+ points-of-presence (POPs), which is closest to the location that the request is made from.

The performance improvement is baked into the Stigg GraphQL-based Go SDK v7.0.0 and the Sidecar SDK v8.0.0 or later.

Custom contract terms - like special usage allowances, delayed discounts, or non-standard renewal clauses - often live in signed PDFs or CRM opportunities, separated from entitlement systems and billing platforms. This separation creates operational overhead and causes real-time feature access to drift away from invoice details.

We're excited to announce Contract Management, a single unified solution in Stigg that bridges entitlement provisioning and complex enterprise invoicing!

🆕 What’s new?

A Contract in Stigg represents a signed order form that combines entitlement enforcement with invoice generation:

• Entitlement Provisioning: Grant customers access to features by linking or creating subscriptions to custom plans and add-ons directly from an order form.
• Flexible Billing Contracts: Define payment terms, billing schedules, currencies, and custom line items (including setup fees, support, or catalog items) to automatically generate enterprise invoices.
• Seamless Usage-Based Billing: Connect metered features (e.g., API calls, seats, or tokens) directly to line items. Usage reported to Stigg simultaneously enforces entitlement limits and calculates billed quantities on invoices.
• Multi-Entity & Consolidated Invoicing: Bill through designated legal entities (with custom addresses, logos, and tax/VAT settings) and choose whether line items consolidate onto a single invoice or issue separately with independent billing anchors and payment terms.

💡 Why it matters

• Zero System Drift: Enforce what was sold without manual cross-checks or custom scripts - entitlements and invoices stay perfectly in sync.
• End-to-End Enterprise Flexibility: Support any line item, pricing model, billing cycle (monthly, quarterly, yearly, custom), or payment term (in advance or in arrears) without leaving Stigg.
• Works with Your Existing Stack: Operates natively on top of tools like Stripe Billing and NetSuite without disrupting existing product-led growth (PLG) workflows.

⚒️ Get started

1. Navigate to the Customers > Contracts section and click + Add.
2. Select an existing customer or create a new one.
3. Upload the signed order form (PDF, PNG, JPG).
4. Configure Entitlement Provisioning, Billing Contract terms/line items, and assign the appropriate Legal Entity.
5. Review the financial summary (Total Contract Value, Year 1 Billing, cash inflows chart) and click Publish.

📦 Availability

Contract Management is now available in Public Beta to all Stigg customers.

To learn more about setting up contracts and usage-based billing rules, check out our Contract Management Documentation.

🍿 See it in action

The Stigg Governance Skill gives your AI coding assistant the exact context it needs to help implement Usage Governance correctly, from modeling entity hierarchies and assigning usage limits to reporting usage and enforcing budgets.

It eliminates setup friction by training your agent on Stigg's Governance concepts, API patterns, and edge-case handling, taking you from initial hierarchy design to working enforcement in minutes.

🆕 What’s New

With the Governance Skill, your AI coding assistant can help you:

• Model entity types and hierarchies: Define multi-level parent-child structures across organizations, departments, teams, users, and AI agents using natural language.
• Assign contextual limits: Configure independent usage limits and reset cadences for features and credit wallets at any node in the hierarchy.
• Attribute multi-dimensional usage: Implement usage events that count against multiple entity levels simultaneously.
• Integrate real-time checks: Write robust entitlement checks that pass contextual metadata (like workspaceId or agentId) for precise access decisions.
• Query tree states: Fetch hierarchy structures, child node usage, and remaining credit balances.

⭐️ Why It Matters

Building multi-tiered governance manually usually means digging through dense API docs and wrestling with complex schema design.

By embedding Stigg's governance architecture directly into your AI assistant's memory, you can simply describe your desired domain model (e.g., "Set up a 1,000 credit monthly cap for Workspaces, with a 50 credit daily sub-limit for AI Agents"), and let your agent generate production-ready code instantly.

📦 Availability

The Governance Skill is available now across Stigg's AI-assisted development tools and MCP server integration.

If you're participating in the Usage Governance Private Beta, update your local Stigg AI skills to start using run: npx @stigg/terminal

Configuring custom contract terms just got simpler and error-free. We’re excited to announce subscription metadata suggestions in Stigg, designed to streamline setting up termed subscriptions when integrated with Zuora!

When creating or editing a subscription in Stigg, relevant Zuora metadata keys and allowed values will now automatically be suggested, taking the guesswork out of contract term configurations.

🆕 What's new?

We’ve updated the Stigg Console to automatically surface metadata key-value suggestions specific to Zuora’s termed subscription model:

• Contextual Auto-Suggestions: As soon as you add metadata during subscription creation or editing, Stigg automatically suggests key names (e.g., zuora_initialTerm, zuora_renewalSetting, zuora_termType) and valid options directly in the UI.
• Built-in Validation: Ensure metadata key names and values match exact Zuora specifications before saving, avoiding configuration typos or sync failures.
• Full Termed Subscription Support: Easily configure parameters like initial term length, renewal term length, period types (days, months, years), and renewal behaviors (auto-renew, convert to evergreen, or out-of-term) with instant UI guidance.

⭐️ Why it matters

• Faster Operations: RevOps, Sales, and Customer Success teams no longer need to copy-paste or memorize technical metadata keys from documentation.
• Eliminate Integration Errors: Prevent failed contract syncs or misconfigured Zuora amendments caused by missing or misspelled metadata tags.
• Seamless Contract Flexibility: Easily convert evergreen subscriptions to termed agreements (or vice versa) straight from the Stigg UI using accurate, pre-populated metadata fields.

⚒️ Get started

1. In the Stigg app, open a subscription.
2. Scroll down to the Metadata section and start typing to see automatic key and value suggestions for Zuora termed subscriptions.

For a full list of supported metadata keys and detailed examples, check out our Zuora Termed Subscriptions Documentation.

📦 Availability

Metadata suggestions are available out-of-the-box for all Stigg accounts integrated with Zuora Billing.

🍿 See it in action