Deploy on Render
Run the Node backend as a Render web service and bind its environment-specific origin.
Run the Node backend as a Render web service and bind its environment-specific origin.
Use a Render Web Service for a direct HTTPS backend. Start with Scaffold a backend, then push the application to the managed repository.
api/.process.env.PORT;/healthz before fs.middleware() and use it as the health-check path.Create a runtime token:
farthershore backend tokens create my-business --format json --idempotency-key <persisted-backend-tokens-create-attempt-key>
Store the returned one-time value as a secret environment variable named
FS_RUNTIME_TOKEN, then deploy the service. The value belongs to the running
process, never the repository or browser bundle.
After Render prints the service's HTTPS URL:
farthershore backend create my-business \
--name "Render API" \
--slug api \
--transport direct \
--origin-url https://your-service.onrender.com \
--idempotency-key <persisted-backend-create-attempt-key> \
--default
Previews inherit the production Render service. A preview needs its own Render service or equivalent origin plus an override row only when isolation is desired:
farthershore backend create my-business \
--name "Render API" \
--slug api \
--env staging \
--transport direct \
--idempotency-key <persisted-backend-create-attempt-key> \
--origin-url https://your-staging-service.onrender.com
Changing the Render URL later is an operating-state update:
farthershore backend bind my-business api \
--env staging \
--origin-url https://replacement.onrender.com
farthershore backend list my-business --format json
Call the Farther Shore gateway with a subscriber test key. Calling the Render
origin directly without a gateway signature should return missing_signature.
If the service scales to zero, expect the provider's cold-start latency to be part of the route's upstream latency. Set route timeouts in the business contract based on measured behavior; do not disable verification to hide a startup or routing problem.
For secret rotation, create a second matching token, update Render and redeploy, then revoke the old token. The one-command rotate path revokes the predecessor immediately. See Runtime tokens.