Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/amanvarshney01/create-better-t-stack/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

Better-T-Stack collects anonymous usage analytics to help improve the CLI. This page explains exactly what’s collected, why, and how to opt out.
Privacy first: No personal information, project names, file contents, or secrets are ever collected.

​
What is Collected

On successful project creation, the CLI sends a single event (project_created) containing:

​
Stack Configuration

  • frontend - Selected frontend framework(s)
  • backend - Selected backend framework
  • runtime - Selected runtime (Bun, Node, Workers)
  • database - Selected database
  • orm - Selected ORM
  • api - Selected API layer (tRPC, oRPC, or none)
  • auth - Selected auth provider
  • payments - Selected payment provider
  • addons - Selected addons
  • examples - Selected examples
  • dbSetup - Database setup method
  • webDeploy - Web deployment configuration
  • serverDeploy - Server deployment configuration
  • packageManager - Package manager used
  • git - Whether Git was initialized
  • install - Whether dependencies were installed

​
Environment Data

  • cli_version - Version of Better-T-Stack CLI used
  • node_version - Node.js version
  • platform - Operating system (linux, darwin, win32)

​
What is NOT Collected

The following data is explicitly excluded and never collected:
  • Project names or paths
  • File contents or code
  • Environment variables or secrets
  • Personal information (name, email, IP address)
  • Git commit messages or repository details
  • Directory structures beyond what’s implied by stack choices

​
Why We Collect Analytics

Usage data helps us:
  1. Understand popular stack combinations - Focus development on widely-used features
  2. Identify compatibility issues - Detect problematic stack combinations
  3. Improve documentation - See which features need better docs
  4. Plan new features - Understand what the community needs
  5. Track adoption - Measure CLI growth and impact

​
How to Disable Telemetry

Telemetry is enabled by default but easy to disable.

​
For a Single Run

Set the environment variable when running the CLI: 
BTS_TELEMETRY_DISABLED=1 npx create-better-t-stack@latest

​
Permanently Disable

Add the environment variable to your shell profile: 
export BTS_TELEMETRY_DISABLED=1
After adding to your profile, reload it: 
source ~/.bashrc  # or ~/.zshrc, etc.

​
Using CLI Flag

You can also use the --disable-analytics flag: 
create-better-t-stack --disable-analytics

​
Viewing Analytics Data

All analytics are publicly accessible for full transparency:

Analytics Dashboard

View aggregated charts and statistics

Umami Dashboard

Website analytics (self-hosted on Hostinger VPS)

Raw JSON Data

Download raw aggregated analytics

CSV Export

Download analytics as CSV

​
Notes on Public Data

  • Aggregates are periodically regenerated from incoming events
  • Raw individual events are not publicly exposed
  • Only summary statistics are available on the analytics page
  • No personally identifiable information is included

​
Technical Implementation

For complete transparency, here’s how analytics work:

​
Data Flow

1

CLI sends event

After successful project creation, the CLI sends a single HTTP POST request with stack configuration and environment data.
2

Backend receives event

The Convex backend receives the event and stores it in a database.
3

Aggregation

Events are periodically aggregated into summary statistics (counts, percentages, trends).
4

Public export

Aggregated data is exported to R2 storage for public access.

​
Source Code

You can review the exact implementation:

CLI Event Sender

apps/cli/src/utils/analytics.ts

Telemetry Toggle

apps/cli/src/utils/telemetry.ts

Ingest Endpoint

packages/backend/convex/http.ts

Analytics Backend

packages/backend/convex/analytics.ts

​
Frequently Asked Questions

No. All CLI features work with telemetry disabled. Set BTS_TELEMETRY_DISABLED=1 to opt out.
Only once per project creation. The add command and other operations do not send telemetry events.
Yes. Use the --verbose flag to see the exact data that would be sent:
create-better-t-stack --verbose
This shows the full event payload as JSON.
No. Telemetry is only sent automatically on successful project creation. You cannot manually trigger it.
Nothing. If the analytics endpoint is unreachable or returns an error, the CLI continues normally. Failed telemetry never blocks project creation.
No. Once your project is created, Better-T-Stack collects nothing. Your project runs independently.

​
Privacy Commitment

Better-T-Stack is committed to privacy and transparency:
  • No tracking scripts in generated projects
  • No personal data collection
  • Easy opt-out via environment variable
  • Public analytics for full transparency
  • Open source implementation you can audit
If you have concerns or questions about analytics, please open an issue on GitHub.

Build docs developers (and LLMs) love

Get started for freeTalk to us