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

# Render (unsupported archive)

# Render (unsupported archive)

Fased does not currently support running the full Gateway on Render. The
`deploy/hosting/render.yaml` Blueprint is retained as historical reference and
is not a maintained, release-tested installation path.

<Warning>
  Do not create a new Fased service from the archived Blueprint. It does not provide the
  root-managed native signer/updater, separate signer application and control sockets,
  Tailscale-first host hardening, coordinated rollback, or cold-reboot validation required by the
  supported Hosting profile. Wallet, Vault, and SAT mining must not be enabled on this path.
</Warning>

## Supported alternatives

* For an always-on server, provision a normal Linux VPS and run the maintained
  [VPS Hosting installer](/install/vps):

  Follow the [one-command VPS Hosting guide](/install/vps) from the provider
  root console.

* For a containerized Gateway on your own computer, use the supported
  [Local Docker](/install/docker) guide.

There is no `install.sh --hosting-docker` mode. A Render private service or
persistent disk does not make the archived deployment equivalent to the
Hosting security and update lifecycle.

## Migrating an existing Render deployment

1. Stop changes to the existing service.
2. Export the configured Fased state directory and every Agent workspace.
3. Treat the export as sensitive because it can contain provider, channel, and
   session credentials. Do not copy signer or wallet material through an
   unreviewed migration script.
4. Install Fased on a clean VPS with `install.sh --hosting`.
5. Restore only reviewed, compatible non-custody configuration and workspace
   data, then re-enroll wallet custody through the native signer workflow.
6. Verify `fased health`, Gateway status, plugins, signer health, and each
   channel before deleting the old Render disk or secrets.

Remove the legacy service, public endpoint, disk, and secrets only after the new
VPS is verified and backed up.