render.yaml is a Render Blueprint. It creates one web service from the published
image ghcr.io/the-40-thieves/reliquary-tc:latest with a persistent disk at /data. The image’s
ENTRYPOINT boots the server from RELIQUARY_TC_CONFIG, and the server serves HTTP on the port Render
injects as PORT. Nothing here needs a shell on the host, but the config file must be written to
the disk before the first boot (see step 4 of Create the service).
The Blueprint uses the image rather than building the repository’s Dockerfile, so the release that
CI tested is the one that runs, and Render runs no build.
What the Blueprint creates
Render also injects
PORT, which the server reads as described in
Environment variables. The variable table there applies
here unchanged.
Cost
Render bills a web service by its plan and the disk by its size. As listed on Render’s pricing page on 2026-10-19:
That is about $27.50 per month for the Blueprint as written. Prices change, so check the pricing page
and the plan in the Blueprint review before you create the service.
Create the service
- Click Deploy to Render in the repository README, or open
https://render.com/deploy?repo=https://github.com/The-40-Thieves/reliquary-tc. - Review the service, the plan and the disk, then enter the values Render prompts for:
RELIQUARY_TC_PUBLIC_URL, andOPENAI_API_KEYif you use theopenaiembeddings provider. - Render generates
RELIQUARY_TC_AS_SETUP_TOKEN. Copy it from the service’s environment page now, because you need it for the first-run claim. - Before the first boot succeeds, write the config file to the disk. The disk is empty until then.
RELIQUARY_TC_CONFIGnames this file, so it must exist before the server can be configured from it. Use the same starting point as Railway’s config file, with the paths above:/data/vaultfor the vault and/data/cachefor the cache. Settransports.http.hostto0.0.0.0andtransports.stdiotofalse, as on Railway.
Public URL and custom domain
RELIQUARY_TC_PUBLIC_URL must be https://host or https://host:port, with no path, query or
credentials. Render gives each service a https://<name>.onrender.com address; set the variable to
that origin, or to your own domain once it is attached in the Render dashboard. The value sets
auth.resource (the origin plus /mcp) and is added to allowedHosts, so a custom domain must be
attached and resolve before clients connect. Change the variable and redeploy after any change of
domain.
First-run claim
Withauth.as enabled in the config file, claim the operator account once: open
<public URL>/oauth/setup and enter RELIQUARY_TC_AS_SETUP_TOKEN. Then remove the variable from the
service’s environment. The setup token is for the one claim; leaving it set makes the server warn at
every boot. The full authorization-server flow is in
Authentication, which applies unchanged.
Vault source
The vault on the disk is the only copy the server reads. Seeding it from a laptop is not part of the Blueprint. To keep the vault in step with a Git repository, use the-git image and the variables
in Git-backed vault. Those tags are first
published with the next release, so the -git image is not yet available for the Blueprint’s
image.url.
Limits of a disk
A service with a persistent disk runs as a single instance, cannot scale to several instances, and its deploys are not zero-downtime. Render also refuses some mount paths, such as/, so keep the
mount at /data.
What this does not do yet
- Not yet verified on a live Render service. The Blueprint fields were checked against Render’s documentation, not by creating a service. A live deploy check is still needed.
- The config file is not created for you. The Blueprint ships no template, as Railway does not.