Docs menu

Getting started

Get started with Lampwick

Create an account and a project, connect your app with the Laravel package or HTTP ingest, then read the data in the dashboard, the API or your agent.

Updated View as Markdown

On this page

Lampwick shows the exceptions, requests, jobs, queries, logs, users and uptime of your web apps in one dashboard at app.lampwick.dev. You need an account, a project and an app that sends data.

Requirements

  • An account on app.lampwick.dev.
  • To see a project's ingest token, you must be an owner of its team. You own the team you get at signup.

Connect your first app

  1. Create an account with your e-mail address and a password of at least 12 characters. Open the link in the confirmation e-mail (valid for 24 hours) and enter your password again.
  2. Create a project: New project on the start page, or ⌘ K (Ctrl K on Windows and Linux) → Create project. You land on its settings page, where the Connect your app card shows the ingest URL, the ingest token and the steps for Laravel and curl.
  3. Send data with the Laravel package, or from any language or script with HTTP ingest.

Check that it works

The project's overview shows the Connect your app card until the first data arrives. With the Laravel package, php artisan lampwick:test checks the token and the agent.

Everything in the dashboard is also in the API and on the MCP server.

Integrations

  • Connect a Laravel app: Install the lampwick/laravel package, add your project's ingest token to .env and run php artisan lampwick:agent next to your app.
  • Send data over HTTP: POST a JSON array of records to https://app.lampwick.dev/ingest with your project's ingest token as a bearer token, from any language or script.

Monitoring

  • Work with issues: Lampwick groups exceptions into issues by class, code, file and line. Resolve, ignore or reopen them; a resolved issue reopens when it happens again.
  • Monitor uptime: An uptime monitor requests a URL every 30 seconds to 1 hour. 2xx and 3xx are up; two failed checks in a row are down and alert the team.
  • Check SSL certificates, domains and DNS: Every uptime monitor also checks its SSL certificate, domain expiry (RDAP) and NS/MX records, and alerts before expiry or when DNS changes.
  • Find broken links and mixed content: Turn on the site crawl of an uptime monitor. Once a day Lampwick follows up to 250 pages, checks every link and reports http:// resources on https pages.
  • Monitor scheduled tasks: Lampwick learns each scheduled task's cron from its runs and alerts when a task misses a run, starts failing or runs longer than you allow.
  • Publish a status page: A public page at app.lampwick.dev/status/SLUG with the status and daily uptime (up to 90 days) of the monitors you pick, plus incident and maintenance notices.

Alerts

  • Get alerts: Lampwick alerts every member of a project's team by push notification and e-mail. Mute alerts per monitor or task, or turn off alert e-mails per account.

API & agents

  • Use the Lampwick API: Everything the dashboard shows or does is in the JSON API under https://app.lampwick.dev/api/v1, described by an OpenAPI 3.1 document.
  • Connect Lampwick to your AI agent: Lampwick runs an MCP server at https://app.lampwick.dev/mcp. Add it to Claude Code, Codex, Cursor or another client with a personal token.

Account & teams

  • Manage teams, members and 2FA: Projects belong to a team. Owners invite people by e-mail and manage ingest tokens, deletes and the team; members use the projects. Plus 2FA.