​
Organizations

An Organization is the top-level container for everything in Nightwatch — including applications, environments, events, teams, and billing. Each organization typically represents a single company. You can be a member of one or more organizations and can switch between them at any time.

​
Applications

An Application represents a single Laravel application, such as your web app, API, or internal tool. When creating an Application, you’ll choose a data region, which determines where all telemetry data for that Application is stored. All environments within the Application will share this region.

​
Environments

An Environment represents a specific deployment context within your Application, such as Production, Staging, or Development. Each agent you install will be configured to send data to a specific environment, which determines how events are categorized and filtered within Nightwatch.

​
Query Bindings

When viewing database queries in Nightwatch, you may notice question marks (?) used in place of actual values. These are called query parameter bindings, which represent the values that were bound to the query at runtime. Nightwatch does not capture or display these bound values by design. This is a deliberate decision made to protect your application from unintentionally leaking sensitive or personally identifiable information. Security and data protection are core principles in how we designed Nightwatch. If you need to troubleshoot a specific query and want to see the values being used, a recommended approach is to log the data manually using Laravel’s Log facade as contextual information. These logs will appear alongside the query in Nightwatch, giving you better context while still providing greater control over the data that is sent. Example: 
select * from users where email = ?
In this example, the ? represents the email address passed at runtime, which Nightwatch intentionally redacts.