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

# Self-hosted deployments

> Plan a Silmaril deployment in your cloud account with clear operational ownership.

Silmaril works with your team to deploy Firewall near the workload it protects. [Arrange deployment access](https://silmaril.dev/docs/start/access.md) to agree on the provider, region, networking, and runtime configuration.

## Deployment shape

Your application or gateway sends events to the Firewall runtime in your cloud account. The runtime returns a verdict that the connected integration applies. Agree on evidence storage, dashboard access, and external model dependencies during setup.

Silmaril supplies the images, ports, startup configuration, and release plan for the agreed deployment. Hosted deployment is also available.

## Supported providers

| Provider | Deployment options |
| - | - |
| AWS | ECS or EKS behind your ingress |
| Google Cloud | Cloud Run or GKE |
| Azure | Azure Container Apps or AKS |

Confirm the supported configuration for your workload during planning.

## Responsibilities

| Area | Responsibility |
| - | - |
| Cloud account, region, ingress, and network policy | Your team, with Silmaril's deployment requirements |
| Firewall images and runtime configuration | Supplied by Silmaril for the agreed deployment |
| Credentials and endpoint provisioning | Agreed with Silmaril during setup |
| Integration mode and application failure policy | Your application or gateway owners |
| Release delivery and maintenance | Agreed deployment process and owners |
| Evidence storage, retention, and access | Agreed deployment configuration and service terms |

## Before deployment

Confirm the target platform and region, ingress authentication, outbound dependencies, secret storage, monitoring ownership, and the release and rollback process. Review [data handling](https://silmaril.dev/docs/deployment/data-handling.md) with the team responsible for the workload.

## Connect clients

| Client | Environment variable | Supplied endpoint |
| - | - | - |
| [SDK](https://silmaril.dev/docs/start/quickstart.md) | `SILMARIL_API_URL` | Complete classify URL |
| [LiteLLM](https://silmaril.dev/docs/integrations/litellm.md) | `SILMARIL_GUARDRAIL_URL` | Guardrail URL from the same deployment |

## Verify the deployment

[Verify your integration](https://silmaril.dev/docs/start/verify.md) against the supplied endpoints. Confirm traffic and configured enforcement before expanding production use. Use [troubleshooting](https://silmaril.dev/docs/operate/troubleshooting.md) for authentication, timeout, and transport failures.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.