Questions, asked often.
Answered honestly.

We page a real engineer — not a chatbot. They reproduce the break, identify the root cause, and reply with a plain-English summary plus a recommended fix. On Priority and White-glove, that lands within the hour. You — or your developer, agency, or no-code builder — ships the fix in your platform. We don't push code, log into your editor, or open PRs on your repo: we determine the root cause and recommend a likely fix, no more than that. Every incident gets a written post-mortem the same day.

Deep diagnostic knowledge of Bubble, Lovable, Cursor, Webflow, Softr, Bolt, and Replit — so our recommended fixes are specific to how those platforms actually work. We can also probe anything with a public URL and a documented schema — Wix, Glide, Adalo, FlutterFlow. For custom backends (Node, Rails, Django, FastAPI), we probe the request from the outside and reason about the response. If you can describe how you ship today, we can fit in.

First response within 5 minutes, 24/7 on Priority and White-glove — contractual, backed by the SLA auto-credit. On Baseline, first response within 1 business day. The first response is from a real human — not a chatbot escalating tickets. On Priority, the written root cause + fix recipe within 60 minutes is also contractual (typically ~30 minutes in practice). The canonical SLA table on the pricing page lists every plan's commitments.

Only what you give us read access to: webhook payloads from the flows we probe, response codes and latency numbers, and platform logs scoped to those flows. We don't read your customer database. We don't piggyback analytics. We don't store PII — when a probe turns up email addresses or names, they're hashed before storage. Probes themselves use synthetic test users on synthetic data.

Nightlamp is not currently SOC 2 certified. Data is stored in AWS-managed infrastructure by default, encrypted in transit and at rest where supported, and access is limited to people who need it for operations or support. A DPA and vendor review materials are available on request at hi@nightlamp.app.

Yes — from the settings page, one click, no email-back-and-forth, no exit-survey gauntlet. We pro-rate the unused portion to your next month and refund it. Your data is exported on request as JSON within 24 hours, then purged 30 days after cancellation.

For most no-code apps, yes. URL pings tell you a page is up; we probe whether the actual flow works (login, checkout, webhook contract, scheduled job). And when it breaks, you get a diagnosed root cause and a recommended fix in plain English — not a 500-error and a stack trace to puzzle over at 2 a.m. If a $9 / month URL ping is enough for you, you don't need Nightlamp. If you're paying $80 / month for an enterprise tier and still finding out about outages from your customers, you do.

That's the whole point. The setup wizard walks you through it in plain English: paste your URL, click the platforms you use, describe the flows that matter ("when someone signs up", "when someone pays"). We do the rest. The dashboard is a list of "things that are working" and "things we're handling." No log soup, no severity matrix, no SDKs.

Every diagnosis ships as a step-by-step fix recipe written in plain English for your platform — built so a non-developer can follow it. If you're stuck anyway, reply to the diagnosis email and the engineer who wrote it walks you through the steps. What we don't do: push code, log into your editor, or rebuild your app. For hands-on build work, we'll point you to your platform's developer and agency ecosystem.

One end-to-end user journey through your app: a login round-trip, a checkout, a webhook delivery, a scheduled-job heartbeat, a magic-link email round-trip, a DNS-record check, or a deliverability/blocklist watch. Pinging a single URL is not its own flow — we treat it as part of whichever journey it belongs to. And if you reach your plan's flow count, nothing shuts off and there's no overage charge; we'll ask you to consolidate or move up a tier before adding more.

Read the full flow explainer on the pricing page →

Yes. Beyond your app's pages and flows, we watch the infrastructure email and links quietly depend on: your DNS records (MX, SPF, DKIM, DMARC) for silent drift, your sending IP against email blocklists, and your mail server's TLS certificate for expiry plus a working STARTTLS handshake. These are the failures that stop signup and password-reset emails from arriving — the kind you usually hear about from a customer, not a 500 error.