Monitoring for agencies with many client sites

Put each client in its own Lampwick project, inside one team. Every client site gets uptime, SSL, domain and DNS checks from its URL alone; the apps you build get errors, slow requests and failing jobs as well. Your whole team sees every client, each client's alerts go to that client's channel, and a client can have a public status page.

What you get

• One project per client. Monitors, issues, requests and logs stay apart per client. The project switcher and ⌘ K jump between them; All projects shows them together.
• Site checks from a URL. For every site you look after, also the ones you didn't build: uptime, the SSL certificate, the domain registration and DNS, and, from Pro, a daily broken link and mixed content crawl for up to 10 sites per team. No access to the client's server needed.
• Inside the apps you build. The Laravel package or HTTP ingest adds exceptions, requests, queries and jobs, and Schedule health for the scheduler.
• Alerts per client. Everyone on the team gets push and e-mail. An alert channel can take the alerts of one project, so client A's alerts land in #client-a on Slack, Discord or Microsoft Teams, or in your own ticketing system through a signed webhook. Up to 20 channels per team.
• Status pages for clients (Pro and up). A public page per client at app.lampwick.dev/status/client-name, with its monitors, daily uptime and your incident notices (status pages).
• Roles. Owners manage ingest tokens, status pages, invites and deletes; members work on the projects: issues, monitors, scheduled tasks (teams and roles). Each person can turn on two-factor authentication.
• An agent across all clients. Over the MCP server, ask "Which uptime monitors are down right now?" or "Which scheduled tasks are failing?" across every client project, read-only by default.

Set it up

1. Create an account. The team you get is yours.
2. Create a project per client, and under Uptime add a monitor per site.
3. Invite your colleagues under Teams → Invite people, as Member or Owner.
4. Add an alert channel per client under Alert channels, with Alerts of set to that client's project.
5. For a client status page: Status pages → Create status page, tick the client's monitors, Save and publish.

Which plan fits

Prices are per team per month, excluding VAT. Seats are unlimited from Pro.

Events only count what your apps send (exceptions, requests, logs); monitors for sites you only check from outside use none. Status pages and the site crawl need Pro or higher. See pricing.

What doesn't fit yet

• Client access is per team, not per project. A member sees every project of the team. To let a client log in and see only their own site, give them a separate team, which has its own plan and bill.
• Status pages: up to 10 per team, on app.lampwick.dev/status/…, without a custom domain or your logo.
• Site crawl on up to 10 monitors per team, 20 over all teams you own.
• No client reports. There is no white-label or scheduled PDF uptime report to send to clients; the status page and the API are what you can share.
• Checks from one location, and no SMS or PagerDuty alerts.

If your work is mostly site checks for many client sites, without app monitoring, read Lampwick vs Oh Dear: it says where Oh Dear is the better pick.

Start free with your first client.