BYOC is currently in early access. Contact us to learn more or join the program.
Stigg Cloud vs. BYOC
BYOC deployments are cost-effective at scale: you pay a license fee plus your own cloud infrastructure costs, rather than per-usage charges as with Stigg Cloud.
When to use BYOC
BYOC is the right choice when your organization requires:- Data residency — end-user customer and usage data must remain within a specific cloud region or account under your control
- Enterprise-scale metering — sustained usage event rates exceeding 1,000 events per second
- Compliance — regulatory or contractual requirements that restrict where data can be processed or stored
- Private network enforcement — usage reporting or entitlement checks must not leave your network perimeter
What deploys in your cloud
BYOC components are modular. Usage metering is always included; governance enforcement and credits wallet are optional additions:How it works
Stigg provisions your BYOC environment using IaC templates. Once deployed, Stigg services run in your cloud and are kept up to date by Stigg through a continuous deployment pipeline. Your BYOC environment syncs with Stigg Cloud for catalog changes, credits, and governance updates. Your end-user data — usage events and credit balances — is processed and stored within your cloud and never leaves your environment unless you explicitly configure export.Get started
BYOC is available to enterprise customers in early access. To get started:- Contact us to discuss your requirements and cloud environment
- Stigg will provision your environment using IaC
- Configure your SDKs to point to your BYOC endpoint instead of the Stigg Cloud API
