# Your cron job died on Tuesday.

Render runs your services so you don't think about servers. Polylane watches them so you don't think about dashboards either.

## Supported resources

- Project
- Web Service
- Private Service
- Background Worker
- Cron Job
- Postgres Database
- Key-Value Store
- Custom Domain

## The dashboards stop being your job.

### Every service in one graph

Web services, private services, static sites, background workers, cron jobs, Postgres, key-value stores, disks, and domains: everything lands in one graph with its edges, environments, and history.

### Agents read the metrics and logs

Agents comb each service's metrics and logs on a cadence and judge them against how that service normally behaves. No thresholds to tune, no alert rules to maintain.

### The jobs that fail quietly

Background workers and cron jobs don't page anyone when they break; they just stop. Polylane notices, investigates, and tells you what happened before the backlog does.

### The deploy is the first suspect

Each sync records what appeared, changed, or disappeared. When a service starts failing right after a deploy, the investigation starts from that deploy.

### The key never reaches the agent

Render connects with an API key from your account settings. It's encrypted before it's stored and the agent never sees it. Code changes arrive as pull requests, and any write action waits for your approval.

### Rollback, then the permanent fix

Enable rollbacks and agents restore the last known-good deploy on their own, rate-limited and on the record. When the root cause is a line of code, the permanent fix follows on the repo behind the service.

## Questions

**How does Polylane connect to my Render account?**

With an API key from your Render account settings (Account Settings → API Keys). The key is encrypted before it's stored, and the agent never sees it. Polylane validates it and starts syncing immediately.

**What Render resources does Polylane sync?**

Projects, environments, web services, static sites, private services, background workers, cron jobs, workflows, custom domains, Postgres databases, key-value stores, persistent disks, and environment groups. The full list is on this page.

**Can Polylane change my Render services?**

Agents investigate and explain. Code changes only ever land as pull requests on the repo behind the service, and any write action against Render pauses for your approval first, with the exact request and reason on screen. Rollbacks are off by default: you decide where they're allowed, and you can turn them off at any time. Enabled, agents restore the last known-good deploy on their own, receipted and rate-limited.

**How does detection work without alert rules?**

Agents read your metrics and logs on a cadence and judge them against how each service normally behaves, so regressions get caught without you configuring a threshold. Repeat detections fold into one issue instead of re-paging you.

**Does it work with my observability provider?**

Yes. Datadog, Sentry, Honeycomb, and Axiom join the graph as first-class sources, and their alerts get triaged by an agent the moment they fire.

**What does it cost?**

Pricing is public and self-serve: a free plan, paid plans from $80 a month, and prepaid autofix bundles that never expire. Every plan and limit is published at polylane.com/pricing.

Early access is rolling out through the waitlist: join at https://polylane.com/#join