# Operations

> What the kit gives you to run the app in production: logs, client error reports, rate limits, a health check, analytics, and where to tune the Worker.

*Canonical: https://makerkit.dev/docs/void-cloudflare/operations/overview*

---

The kit runs on your own Cloudflare account and ships no monitoring vendor. What you get instead is small, and all of it is yours to read and change.

## What the Kit Ships

| What | For | Where | Page |
|---|---|---|---|
| Structured logs | Finding errors, in Cloudflare's Workers Logs | `@kit/shared/logger` | [Logs and Client Errors](./logs-and-client-errors) |
| Client error reports | Browser errors that never reach your server logs | `@kit/client-errors`, `apps/web/routes/api/client-errors.ts` | [Logs and Client Errors](./logs-and-client-errors) |
| Rate limits | Public routes that answer anyone | `apps/web/config/rate-limits.config.ts` | [Rate Limits](./rate-limits) |
| Health check | "Is it up, and which version runs?" in one request | `apps/web/routes/api/health.ts` | [Health Check](./health) |
| Analytics registry | Your own analytics, with no vendor in the kit | `apps/web/config/analytics.config.ts` | [Analytics](./analytics) |
| Worker tuning | CPU time, database distance and caching | `apps/web/void.config.ts` | [CPU Time and Database](./cpu-and-database) |

## What the Kit Does Not Ship

- **No error tracking or analytics vendor.** Workers Logs is the one place to look, and you register an analytics provider yourself.
- **No readable client stack traces.** Browser stacks are minified, because the kit does not upload source maps.
- **No alerting.** Point an uptime monitor at the [health check](./health).

## Check Production

```bash
SITE_URL=https://your-site.com pnpm kit:doctor --prod
```

Run it in your own terminal. It reads your live site and says whether `/robots.txt` and `/api/health` answer as they should. It changes nothing.
