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

# Railway

> Connect a Railway workspace to deploy and manage its services and databases.

Hoista finds the services and databases in the projects of a Railway workspace. It deploys services, redeploys or rolls back through Railway's own deployments, adds databases and buckets, and can run your [remote](https://docs.hoista.dev/guides/remote.md).

## Connect

In Desktop, open **Accounts**, choose Railway, and paste a token:

1. Open [Tokens](https://railway.com/account/tokens): **Account Settings → Tokens → Create token**. Name it Hoista and pick your workspace. **No workspace** gives the token every workspace.
2. Copy the token and paste it into Hoista.
3. If Hoista asks for the workspace ID, press ⌘K in Railway and choose **Copy active workspace ID**.

![Railway’s New Token page](https://mintcdn.com/mirt-lab/bTbgaR1vteaGCpS-/assets/tokens/railway-token.webp?fit=max\&auto=format\&n=bTbgaR1vteaGCpS-\&q=85\&s=a677b116ee69762b9822b9c45ca2bd0e)

Railway’s New Token page, captured November 2026. Personal details are blurred. If yours looks different, the names in the steps still match.

From the CLI:

```bash theme={null}
hoist accounts add railway
```

It asks for the token in a hidden prompt and finds the workspace from it. In scripts, use `hoist accounts add railway --name NAME --token-stdin`, and add `--account <workspace-id>` if the token reaches more than one workspace.

## What you can do

* Deploy a service from a folder, a GitHub repository or a container image.
* Redeploy or roll back a service through Railway's deployments.
* Add a database or a bucket to a Railway project.
* Read and change variables on the **Variables** tab.
* See logs for the service's latest deployment, metrics, and daily usage with `hoist usage`.
* Use the **Railway** tab for Railway's own settings and operations.
* See what Railway has billed the workspace so far this period on **Billing**.
* Run your remote on Railway with `hoist remote create railway --account <account> --repo OWNER/NAME`. Until Hoista publishes a server image, `--repo` is needed; see [Set one up](https://docs.hoista.dev/guides/remote.md#set-one-up).
* Delete a service or database at Railway after you confirm it by name.

## Bring in existing resources

Hoista looks for services when you connect. In Desktop, add them as described in [Bring in an existing project](https://docs.hoista.dev/guides/import-apps.md). From the CLI:

```bash theme={null}
hoist import --list
hoist import <resource-id> --new my-app
```

Projects start in **watching** mode. Run `hoist projects manage my-app` when you want Hoista to make changes. To look again, run `hoist accounts refresh <account>` with the name or ID from `hoist accounts`.

## Related

> [card] [Providers](https://docs.hoista.dev/providers/overview.md)
>
> What Hoista supports on each provider.

> [card] [Connect hosting accounts](https://docs.hoista.dev/guides/accounts.md)
>
> Connect, check and rotate accounts.

> [card] [Bring in a project](https://docs.hoista.dev/guides/import-apps.md)
>
> Add what an account already runs.


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