Ship a complete .env.example in minutes, not guesswork.

Paste a GitHub URL or connect your account. We scan real source files for `process.env.*` usage, dedupe variables, and generate contributor-ready descriptions so your setup docs stop drifting.

Generate My .env.example See Pricing

No repo cloning required

Private repo support

AI-assisted variable docs

Sample Output

# Generated by Env Example Generator
# Public API base URL used by browser requests.
NEXT_PUBLIC_API_URL=

# Secret used to verify webhook signatures from Stripe.
STRIPE_WEBHOOK_SECRET=

# Token used for authenticated GitHub API access.
GITHUB_TOKEN=

The Problem This Solves

Stale .env.example files break first-run setup

New contributors clone your repo, run install, and hit immediate runtime errors because required variables are undocumented.

Maintainers spend time answering the same setup questions

Each release adds integrations, but docs lag behind. The support burden lands on maintainers and slows shipping.

Hidden env dependencies create fragile deployments

Variables buried in feature flags or edge routes only fail in production when no one expected them.

How It Works

Step 1

Provide Repository Access

Paste a public repo URL or connect GitHub to scan private codebases with your account permissions.

Step 2

Static Scan + Deduplication

The scanner traverses repo files, extracts every environment variable reference, and merges duplicates.

Step 3

Generate Commit-Ready Output

OpenAI drafts practical descriptions from usage snippets, then you copy the generated `.env.example`.

Simple Pricing for Maintainers

Pay once to unlock quickly, or choose a low monthly team license for ongoing shared maintenance.

Maintainer Plan

Perfect for open-source projects that need cleaner onboarding and fewer setup questions.

One-time starter unlock

or $7/mo

Team license

Scan public and private repos for `process.env.*` usage
Generate .env.example with practical one-line descriptions
Merge duplicate variables from multiple files and contexts
Copy-ready output for immediate commit

Buy Access

After checkout, enter the purchase email below to unlock scanning in this browser.

FAQ

Can it scan private repositories?

Yes. Connect GitHub on the dashboard and the scanner uses your OAuth token to inspect repositories your account can access.

How are descriptions generated?

The app sends variable names plus nearby code snippets to OpenAI and asks for maintainer-focused descriptions. If no API key is configured, it falls back to deterministic heuristics.

Does this replace human review?

No. It accelerates the first draft and catches missing variables, but maintainers should still review final descriptions before commit.

How is paid access handled?

After Stripe checkout, webhook-confirmed purchase emails can unlock access in-browser, and scanning APIs require a signed paid cookie.