Creating the service, watching the deploy, reading the logs when it fails and querying the database behind it are usually four places; here they are one session, with the workspace named on each call so the account being touched is explicit. The read side is the stronger half — logs with real filters, metrics with quantiles and aggregation — while configuration changes past environment variables still route back to the dashboard.
Render's own server for the resources in your account: web services, static sites, cron jobs, Postgres databases and key-value stores, plus deploys, logs and metrics for all of them.
- Services listed and read in detail, with previews included when you ask for them, and the workspace passed explicitly on each call so which account is being changed is never a guess
- A web service created with its runtime — node, python, go, rust, ruby, elixir or docker — plus build and start commands, repo, branch, plan and region; static sites and cron jobs created the same way
- Environment variables replaced as a set on an existing service
- Deploy history per service, one deploy read in detail, and a deploy triggered by hand — with the build cache cleared if you ask
- Logs filtered the way an incident actually needs: by resource, severity, type, instance, host, status code, method, path, text and time window, plus the values a given log label takes
- Metrics for any resource — CPU, memory, instance count, bandwidth, HTTP request counts and latency at a quantile you choose, active connections for databases — over a window up to 30 days back
- Postgres created, listed, described and queried with read-only SQL, and key-value instances created with their eviction and persistence policies
A Render account, connected as described in Render's own setup documentation. Creating a web service takes a runtime, a build command and a start command; the region defaults to oregon and auto-deploy to yes. One thing to know before planning around it: the update tools for a service, static site or cron job do not change anything — they hand back a link to that resource's settings in the dashboard, so edits beyond environment variables happen there or through the REST API. Apache-2.0.