> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stigg.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Bring Your Own Cloud (BYOC)

<Note>
  BYOC is currently in **early access**. [Contact us](mailto:support@stigg.io) to learn more or join the program.
</Note>

Stigg BYOC (Bring Your Own Cloud) is a fully-managed solution that deploys Stigg's usage and metering back-end infrastructure into your own cloud environment — on AWS, GCP, or Azure. Stigg provisions and operates the entire stack using IaC; you retain data sovereignty and control without taking on any operational burden.

BYOC is purpose-built for large-scale, high-throughput deployments in enterprise environments with strict security, data residency, or limited external network access requirements.

## Stigg Cloud vs. BYOC

|                               | Stigg Cloud                        | BYOC                                                      |
| ----------------------------- | ---------------------------------- | --------------------------------------------------------- |
| **Infra ownership**           | Stigg-managed, multi-tenant        | Customer VPC, Stigg-managed via IaC                       |
| **Data residency**            | Stigg's cloud (AWS)                | Your cloud — end-user data stays in your environment      |
| **Usage metering throughput** | Up to 1,000 events/sec per account | Up to 1,000,000 events/sec                                |
| **Compliance**                | SOC 2 Type II, GDPR                | SOC 2 Type II, GDPR + your own cloud's compliance posture |
| **Setup**                     | Zero-config SaaS                   | Provisioned by Stigg into your cloud                      |
| **Upgrades**                  | Automatic                          | Managed by Stigg, deployed into your environment          |
| **Pricing model**             | Per-usage                          | License fee + your cloud infrastructure costs             |

<Note>
  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.
</Note>

For Stigg Cloud architecture details, see [High-availability architecture](/documentation/high-availability-and-scale/high-availability-architecture).

## 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:

| Component                  | Required | Description                                                                       |
| -------------------------- | -------- | --------------------------------------------------------------------------------- |
| **Usage metering**         | Yes      | Ingests, buffers, and aggregates usage events at scale entirely within your cloud |
| **Governance enforcement** | Optional | Evaluates entitlement checks against locally-held subscription data               |
| **Credits wallet**         | Optional | Manages credit balances and consumption within your cloud                         |
| **Full Stigg**             | Optional | All Stigg functionality runs entirely within your VPC (long-term roadmap)         |

## 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:

1. [Contact us](mailto:support@stigg.io) to discuss your requirements and cloud environment
2. Stigg will provision your environment using IaC
3. Configure your SDKs to point to your BYOC endpoint instead of the Stigg Cloud API