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

# Deploy the LLM Gateway on Railway

> Deploy the Manifest LLM Gateway with the published Railway template, PostgreSQL, and request-log storage.

<Card title="Open Railway template" icon="external-link" href="https://railway.com/deploy/wild-wild">
  Best one-click path for most users. The template provisions the gateway,
  PostgreSQL, and a bucket for request logs.
</Card>

## Overview

Railway is the fastest hosted path for the gateway. Use the published Manifest template to create a project with the gateway app, a PostgreSQL database, and a storage bucket for [request logs](/llm-gateway/docs/llm-gateway/docs/request-logs), then open the generated domain and create the first admin account.

## Prerequisites

* A Railway account.
* A Railway workspace with permission to create projects and services.
* Billing enabled if your usage exceeds the free included resources.

## Deploy

1. Open the [Manifest Railway template](https://railway.com/deploy/wild-wild).
2. Choose the Railway workspace and project where you want to deploy the gateway.
3. Review the services that will be created.
4. Deploy the template.
5. Wait for the gateway service and PostgreSQL database to finish provisioning.

The template includes the app service, the database, and a `messages-recordings` bucket, so you do not need to create PostgreSQL or recording storage separately.

## Open the gateway

Open the generated Railway domain and create the first account. Fresh installs redirect to `/setup`; the first account you create becomes the admin.

Verify the deployment:

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
curl -fsS https://<your-railway-domain>/api/v1/health
```

## Notes

* Use a custom domain before configuring production OAuth callbacks.
* Keep PostgreSQL backups enabled for production data.
* The template provisions a `messages-recordings` bucket for [request logs](/llm-gateway/docs/llm-gateway/docs/request-logs), so they survive redeploys without extra setup.
* Use the Railway service logs when debugging failed boots or database connection issues.

Relevant Railway links:

* [Railway templates](https://railway.com/templates)
* [Manifest Railway template](https://railway.com/deploy/wild-wild)