Skip to main content
BYOC is currently in early access. Contact us to learn more or join the program.
Stigg provides an IaC stack that you deploy into your own cloud account. Once deployed, Stigg manages ongoing operations and upgrades.

​
Prerequisites

Before Stigg can provision your environment, you need:
  • A dedicated cloud account (AWS, GCP, or Azure — confirm with your Stigg contact which providers are supported for your configuration)
  • A VPC for Stigg components to be deployed into — you can use an existing one or Stigg can create a new one
  • Outbound network access from your VPC to Stigg Cloud (for catalog sync and billing rollups)

​
Provisioning process

Stigg follows this process to set up your BYOC environment:
  1. Scoping call — Stigg works with your team to decide which optional components to enable (governance enforcement, credits wallet, or full Stigg)
  2. Stack deployment — Stigg provides you with an IaC stack; you deploy it into your cloud account, which provisions all required permissions and infrastructure
  3. Connectivity verification — Stigg validates that the sync channel between your environment and Stigg Cloud is operational
  4. SDK configuration — you update your SDK initialization to point to your BYOC endpoint

​
SDK configuration

Once your BYOC environment is live, update your SDK to report usage and check entitlements against it instead of the Stigg Cloud API: 
import Stigg from "@stigg/node-server-sdk";

const stigg = await Stigg.initialize({
  apiKey: "YOUR_SERVER_API_KEY",
  baseUri: "https://YOUR_BYOC_ENDPOINT",
});
Your Stigg contact will provide the BYOC endpoint URL after provisioning is complete.

​
Verifying the deployment

After provisioning, Stigg will confirm:
  • All services are healthy (health check endpoints return 200)
  • The inbound sync channel from Stigg Cloud is active
  • A test usage event reported through the SDK reaches the BYOC metering pipeline
See Observability and debugging for how to monitor your environment after go-live.