Telemetry

Nextly collects usage data under a random ID from its CLI tools (create-nextly-app and nextly) to understand which features are used, catch regressions, and make data-driven product decisions during alpha.

Telemetry never includes your name, project contents, file paths or secrets. It is opt-out, automatically disabled in CI, Docker, production, and non-interactive shells, and can be disabled permanently with one command or one environment variable. The random ID lasts between runs, and the nextly CLI also sends a hashed project ID with each event, so one install's events can be linked to each other, though never to an account or an email address.

How to opt out

Any of these is enough. The first one you set wins.

# Option 1: one-time command, persists in ~/.config/nextly/config.json
nextly telemetry disable

# Option 2: environment variable, per command (telemetry is sent only by the
# `nextly` and `create-nextly-app` CLIs, never by your running app)
NEXTLY_TELEMETRY_DISABLED=1 nextly migrate

# Option 3: community standard (also respected by other tools)
DO_NOT_TRACK=1 nextly migrate

What we collect

Every event includes this base context:

create-nextly-app events

nextly command events

error_code taxonomy

Errors map to a fixed enum. Raw error messages and stack traces never leave your machine.

• install_failed, install_network, install_permission, install_disk_full
• template_download_failed, template_parse_failed
• config_generation_failed
• db_connection_failed, migration_conflict
• unknown

What we never collect

• Project name, directory name, or any file path.
• Git remote URL, username, email, or hostname.
• IP address. We set disableGeoip: true on PostHog so the server does not derive one either.
• File contents, schema names, collection names, or field names.
• .env values, API keys, database URLs, or auth secrets.
• Raw error messages or stack traces.
• Next.js or Nextly config file contents.

How the random ID works

On first run, Nextly generates two random values:

• anonymousId -- 256 bits of entropy, stored in your user config directory (~/.config/nextly/config.json on Linux; OS-appropriate paths elsewhere). Sent with every event as the distinct_id. Never linked to any account or email.
• salt -- 128 bits of entropy, stored alongside the ID. Used to hash your project paths. The salt never leaves your machine.

You can rotate both with:

nextly telemetry reset

This will also re-show the first-run notice on your next CLI invocation.

When telemetry is disabled automatically

• DO_NOT_TRACK=1 is set.
• NEXTLY_TELEMETRY_DISABLED=1 is set.
• NODE_ENV=production.
• CI is detected (CI=1, GITHUB_ACTIONS, GITLAB_CI, CIRCLECI, TRAVIS, JENKINS_URL, BUILDKITE, VERCEL, NETLIFY, RENDER).
• Docker is detected (/.dockerenv present).
• Stdout is not a TTY (e.g., output is piped to a file).

Source code

Every line of telemetry code is open-source. Audit it yourself:

• packages/telemetry/src/events.ts -- the full event catalog
• packages/telemetry/src/is-disabled.ts -- disable resolution order
• packages/telemetry/src/client.ts -- PostHog client wrapper
• packages/telemetry/src/index.ts -- the public API