> ## Documentation Index
> Fetch the complete documentation index at: https://nightwatch.laravel.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQs

> Frequently asked questions about Nightwatch

## The basics

<Accordion title="Can Nightwatch support any PHP application?">
  Nightwatch is purpose-built for Laravel and deeply integrates with the
  framework's internals — from queues and events to the request lifecycle. This
  tight integration is what allows us to offer zero-config setup, rich
  telemetry, and smart insights. Supporting generic PHP would mean compromising
  on that experience, so we've chosen to go deep rather than broad.
</Accordion>

<Accordion title="What is an event in Laravel Nightwatch?">
  An event in Nightwatch covers anything you'd need to monitor your application:
  requests, outgoing requests, notifications, jobs, queries, mail, commands,
  cache, scheduled tasks, and exceptions. For more information, see
  [Events](/events).
</Accordion>

<Accordion title="How much overhead does Nightwatch add?">
  Nightwatch is designed to add minimal overhead to your application, typically
  less than 3ms per request. The agent runs separately from your application
  process to ensure minimal impact.
</Accordion>

<Accordion title="Will Laravel continue supporting Telescope and Pulse?">
  Yes, Telescope and Pulse are free, lightweight open source packages that we
  will continue to support. If you're curious on the difference between each
  product check out our Telescope and Pulse comparison pages.
</Accordion>

<Accordion title="What happens when I hit my plan quota limit?">
  Once you’ve consumed all of the events included in your plan, Nightwatch will pause event ingestion from your application.

  To continue sending events, you have two main options:

  * [**Upgrade your plan**](/subscriptions#upgrading-a-subscription) to a higher tier. This increases your quota immediately for the remainder of the billing cycle.
  * [**Enable Additional Events**](/additional-events), which lets you continue ingesting beyond your quota. These are billed per 100k events, up to the limit you set in your billing settings and are invoiced at the end of your current billing cycle.

  To avoid hitting your limit unexpectedly, we recommend experimenting with [sampling](/filtering#sampling) to reduce event volume while maintaining meaningful visibility.

  If your organization requires 1B+ events, please get in [contact with us](/support) and we'll be happy to help you.
</Accordion>

## Setup and integration

<Accordion title="Does Nightwatch work with any hosting provider and setup?">
  Yes, Nightwatch supports the majority of hosting providers and setups. We've
  published guides for [Laravel Cloud](/guides/cloud), [Laravel
  Forge](/guides/forge), [Laravel Vapor](/guides/vapor), and [other
  providers](/guides/other-providers) including Linux servers and Docker. If you
  have a serverless setup, like Laravel Vapor, you'll need to create a virtual
  machine on another server to run Nightwatch. If you're using something else,
  let us know — we're happy to help.
</Accordion>

<Accordion title="Can I use Nightwatch in local development?">
  Yes, you can use Nightwatch in development environments. We strongly recommend
  creating a dedicated environment for development to keep your metrics clean.
</Accordion>

<Accordion title="How do I temporarily disable monitoring?">
  Set `NIGHTWATCH_ENABLED=false` in your `.env` file to temporarily disable
  Nightwatch without removing the package. For more information, see the [GitHub
  package documentation](https://github.com/laravel/nightwatch) for all
  available configuration options.
</Accordion>

<Accordion title="Can I use both Nightwatch and another APM tool at the same time?">
  Yes, you can use Nightwatch alongside other APM (Application Performance
  Monitoring) tools simultaneously. There are no technical limitations
  preventing you from running multiple monitoring solutions in parallel. That
  said, running multiple monitoring tools will have some cumulative performance
  impact that will need to be mitigated.
</Accordion>

<Accordion title="Does Nightwatch support monitoring multiple apps on a single server?">
  Yes! Nightwatch can monitor multiple apps on a single server. Each app simply
  needs its own agent process. For detailed setup instructions, see [Running the
  Agent](/start-guide#running-the-agent) in our Quick Start guide.
</Accordion>

## Business and compliance

<Accordion title="Can I set spending caps on my account?">
  By default, the maximum amount you'll be charged each month is your
  subscription fee. If you choose to enable [Additional
  Events](/additional-events), you can set a spending cap by defining the
  maximum number of additional events you'd like to ingest beyond your plan's
  limit. Once that limit is reached, Nightwatch will automatically stop
  ingesting new events to prevent further charges.
</Accordion>

<Accordion title="What data residency options are available?">
  Nightwatch currently offers data storage in the US, EU and Australia. We're
  working on supporting additional regions. Please [contact us](/support) if you
  require data residency in a specific region.
</Accordion>

<Accordion title="How long does Nightwatch retain data?">
  By default, we store data for 90 days, but longer retention windows are
  available on our enterprise plans. Get in touch if you need a custom retention
  window.
</Accordion>

<Accordion title="Is Nightwatch SOC 2 or ISO 27001 certified?">
  Nightwatch is actively pursuing SOC 2 Type 1 and Type 2 certifications.
</Accordion>

<Accordion title="Do you have self-hosting options?">
  Nightwatch is a fully-managed product.
</Accordion>