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

# Overview

After you’ve built and tested your Resource Server, the next step is to configure your **instances** for production readiness.

Configuration is managed per instance in the **Fiskil Console**. Each instance (staging or production) has its own settings for domains, branding, security, and optional compliance profiles.

***

## What You Can Configure

* **Custom Domains**
  Use your own DNS name (e.g., `consent.yourcompany.com`) for hosted consent flows.
  See: [Custom Domain](/docs/configure/custom-domains)

* **Branding**
  Control how consent screens and dashboards are presented to your customers with your logo and display name.
  See: [Branding & Consent Screen](/docs/configure/branding)

* **Resource Server Settings**
  Define the base URL, JWKS validation, optional mTLS, and firewall allow-lists.
  See: [Resource Server Settings](/docs/configure/resource-server-settings)

* **Compliance Profiles** (optional)
  Apply pre-configured scopes, headers, and behaviors aligned with standards such as CDR or FDX.

***

## Where Configuration Happens

All configuration is available in the **Console → Instance Settings**.

Each instance has:

* Its own **domains** (staging vs production)
* Its own **keys and secrets**
* Its own **logs and metrics**

***

## Best Practices

* **Separate environments** — Keep staging and production instances isolated with their own DNS, keys, and secrets.
* **Migrate safely** — Test configuration changes in staging before applying them to production.
* **Lock down production** — Use strict firewall allow-lists, DNS validation, and change control for live traffic.

***

## Related

* [Instances](/docs/get-started/instances)
* [Custom Domain](/docs/configure/custom-domains)
* [Branding & Consent Screen](/docs/configure/branding)
* [Resource Server Settings](/docs/configure/resource-server-settings)