Anything.com - Secrets · Product Feature Research

What it does

Secrets management for the built app — API keys, env vars, credentials that shouldn't be hardcoded.

Evidence

Anything.com - Project Settings — 🔒 Secrets in the API SETTINGS section.

Target ICP

Any user wiring their app to a paid API (Stripe, OpenAI, Twilio, etc.). Essential for Built-in Payment Acceptance integrations — Stripe secret keys need a secure home.

Why the IA placement matters

Secrets live under "API SETTINGS" — grouped with other backend config. Aligns with Anything's IA-reveals-model-mental-model pattern (see Anything.com - Project Settings).

Implementation details (unknown)

Per-environment (dev/prod)? Unknown.
Scoped to project only, or team-wide? Unknown.
Rotation reminders? Unknown.

Differentiators vs Replit

Replit has Secrets built into the editor / workspace (legacy repls have had this for years, likely unchanged). Replit's is more dev-first (alongside code).

Sources

!raw/anythingdotcom/Project_Settings.png