Docs · Publishes

Render

Every deploy is checked the moment it goes live.

What it watches

Render feeds Publishes — Every deploy gets a verdict within five minutes — as Publish Verification.

What Keelnest reads

API key · read services, deploys, custom domains and variable names.

Render builds previews per pull request, not per branch, so a repair on Render is verified by review.

Read-only, like every connection: Keelnest never refunds, charges, changes a price, edits a setting or an environment variable, merges on its own or runs a migration. The credential is checked with one read call before it is stored, encrypted at rest, and can be revoked at the provider at any time. Security says the whole of it.

How to connect

Create the api key. Render dashboard > Account Settings > API Keys > Create API Key. Open Render.
Paste it into Keelnest. In your workspace, open Integrations, find Render and press Connect. Keelnest makes one read call to confirm the credential works, stores it encrypted, and starts reading on the next five-minute tick.
Link the apps. Under Manage, pick which applications this account watches. An app linked to a host is checked the moment that host reports a deploy; an app linked to a payment or AI account starts building its baseline from that hour.

Deploy notifications

Render can be told to call Keelnest when a deploy finishes, so verification starts within seconds of it instead of on the five-minute poll.

Where to set it up. Render → your workspace → Settings → Webhooks → New Webhook: the address below, and tick the deploy events — “Deploy ended” is the one that matters. Render shows a signing secret as it creates the webhook; copy it before you leave the page.

The address and the secret to paste are shown in Keelnest under Integrations › Render › Manage, one pair per connected account.

How a delivery is checked. webhook-id, webhook-timestamp and webhook-signature (`v1,<base64>`): the Standard Webhooks scheme, HMAC-SHA256 over `<id>.<timestamp>.<body>` with the signing secret Render shows once. A delivery is never trusted on its own: it says which site to look at first, and every fact about the deploy is then read back from Render’s API, so a forged or missed delivery changes nothing the next poll would not correct.

Render's webhooks need a Pro workspace or higher, and they belong to the workspace rather than to one service, so every service in that workspace reports through the one address. Below Pro there is no webhook to create and the five-minute poller is the only route.

Source: Render’s documentation.

Start watching

Create a workspace and connect Render from Integrations, or run the free check on any public URL first. All docs.