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

# Instances

> Deploy and manage Data Provider instances for your environments.

An **instance** is a deployed Data Provider with its own configuration, DNS, keys, and operational logs.
Instances are fully isolated — each has separate secrets, JWKS keys, audit logs, and request logs.

***

## Staging vs Production

Every instance is tagged as either `staging` or `production`.

* **Staging**
  * Flexible environment with Testing tools
  * Supports mock recipients and easier iteration
  * Relaxed change controls

* **Production**
  * Customer-facing and compliance-critical
  * Strict change control and audit requirements
  * Hardened security posture

***

## What You Configure Per Instance

Each instance can be configured independently:

* **Domains** — Custom DNS (see [Custom Domain](/docs/configure/custom-domains))
* **Branding** — Logo, display name, and consent screen identity (see [Branding](/docs/configure/branding))
* **Resource Server settings** — Base URL, JWT validation (JWKS), optional mTLS
* **Compliance profile** (optional) — Pre-configured scopes, headers, and behaviors for standards such as CDR or FDX

***

## Typical Lifecycle

1. Your instances are deployed by Fiskil when you onboard.
2. Integrate your Resource Server with the **staging** instance and validate using Testing tools.
3. Connect your finalised resource server to the **production** instance with locked-down DNS, secrets, and alerting.
4. Promote changes from staging → production using versioned, scheduled releases.

<Note>
  Migrate changes through Staging before Production.
  Keep DNS, keys, and secrets distinct for each instance.
</Note>