You Own Everything
FlareWatch is a deployment/control-plane app. The runtime it deploys is yours inside your Cloudflare account.
Ownership model
- Your account resources: workers, KV namespaces, optional DNS records/secrets
- Your runtime data: status/history state in your KV
- Your URLs/domains: workers.dev URL and optional custom domain
Finding your resources in Cloudflare
Navigate to the Cloudflare dashboard and go to Workers & Pages then Overview. Your monitor
worker is prefixed with flarewatch-monitor-, and your status-page worker is either
flarewatch-status-* or your custom name from the wizard.
Viewing Worker logs
To see real-time request logs for your workers:
- Go to Workers & Pages in the Cloudflare dashboard.
- Select your worker (e.g.
flarewatch-monitor-*orflarewatch-status-*). - Click the Logs tab.
- Click Begin log stream to see live request and error logs.
This is useful for debugging monitor check failures or verifying that your status page is receiving traffic.
If flarewatch.app is unavailable
Existing deployments continue serving from Cloudflare because the runtime workers are already deployed in your account.
What the wizard provisions
- Status page worker
- Monitor worker
- KV namespace
flarewatch-config - KV namespace
flarewatch-state - Optional basic-auth worker secrets
- Optional custom-domain DNS CNAME updates
Lifecycle controls
- Update by rerunning the wizard and loading existing config.
- Delete from the post-deploy flow (with optional KV deletion).
- Manual deletion is still possible in Cloudflare dashboard if needed.