Render through Squiid

What Render is

Render is a managed platform that covers the common pieces of a web application in one place: web services built from a repository or a Dockerfile, static sites with a CDN, private services that are not exposed publicly, background workers, cron jobs, and managed Postgres and key-value stores. A render.yaml blueprint declares all of it in the repository, so an environment can be recreated from code, and pull request previews spin up a full copy of the stack. Zero-downtime deploys, health checks and autoscaling are part of the platform rather than something to assemble.

For AI-coded projects Render is attractive because the generated infrastructure can live in the same commit as the generated code. An agent that adds a background worker also adds it to the blueprint, and the change is reviewable as a diff rather than as a sequence of dashboard clicks nobody recorded. The free tier is also enough to put a prototype online before deciding whether it deserves a paid plan. Private services are useful for an internal API that should never have a public URL, which is easy to forget when an agent scaffolds everything as a web service.

Why connect it through Squiid

Render is on the Squiid roadmap. When it lands, Squiid will provision the workspace, hold the API key and route deploys and management calls through https://api.squiid.io/v1/render/... with Authorization: Bearer $SQUIID_API_KEY, with the CLI and API working by base URL swap (gateway convention). Instance hours, bandwidth and managed database cost will bill at Render's listed price on your single Squiid invoice, starting from the free tier at no cost.

• One account, one key, one bill, one dashboard. Render sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Render credentials. Your code carries SQUIID_API_KEY, so RENDER_API_KEY, RENDER_SERVICE_ID never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what Render costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• A provisioned Render workspace with the key held by Squiid
• Web services, static sites, workers and crons
• Managed Postgres and key-value storage
• Infrastructure declared in render.yaml
• Render list pricing, no markup

How to connect Render

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces RENDER_API_KEY, RENDER_SERVICE_ID
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/render/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

Render charges per instance hour by size plus bandwidth and managed database cost, with a free tier, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Render usage, with no markup and no per-request margin.

Render is used on the free tier basis, so there is no fixed monthly plan cost to pass through. You pay for what you use at the provider’s listed price.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so Render usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Export: the app is redeployed from your own source into your own Render account, then domains and environment variables are re-pointed. Squiid never owns your code, your schema or your domain, and the gateway speaks Render's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

Render through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on Render usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.