One command
Run one provider setup from an initialized project. Its adapter may handle auth inputs, run its available credential checks, then attempt persistence through Phantom. Supabase, Neon, Turso and Vercel have source resource-creation branches; other adapters attach accounts or supplied credentials. Inspect actual results.
stack add plausible
Or retrieve catalog matches for what you're building via stack recommend:
stack recommend "product analytics and feature flags"Auth flow
Supply the adapter's API-key inputs. Some checks only validate structure or a limited endpoint; additional credentials and manual setup may be needed.
How-to: Generate an API key at https://plausible.io/settings and note your site ID.
Secret slots
stack add plausible has these 2 catalog secret
slots; verify which values its adapter actually materializes through Phantom:
PLAUSIBLE_API_KEYPLAUSIBLE_SITE_ID
Use stack env export --example for an empty-key skeleton.
Stack does not automatically fill env files or resolve credential placeholders.
stack exec -- <cmd> forwards to installed Phantom exec;
configure and verify the app separately.
Related providers in Analytics
- PostHog — Product analytics + flags. Personal API key stored in Phantom.
- Mixpanel — Product analytics. Project token + optional API secret stored in Phantom.
FAQ
Do I need a Plausible account to use it with Stack?
Use an existing Plausible account and permissions appropriate to the adapter. Creation or attachment behavior is provider-specific. Supply the adapter's API-key inputs. Some checks only validate structure or a limited endpoint; additional credentials and manual setup may be needed. If you don't have a credential yet, create one at https://plausible.io and supply the required inputs; inspect verification and persistence results.
Where does Stack store my Plausible credentials?
Credential persistence uses the installed Phantom Secrets interface. The catalog declares slot names (PLAUSIBLE_API_KEY, PLAUSIBLE_SITE_ID); actual materialized outputs can differ. Stack handles supplied values in memory and records dedicated names in config; manual files and freeform metadata are not generally redacted.
Can I rotate or revoke this integration later?
Use `stack remove plausible` for local Plausible configuration/MCP cleanup and attempted Phantom cleanup; upstream resources remain. Cleanup can refuse or leave keys stored. Rotate or revoke the underlying Plausible credentials through https://plausible.io, then update and verify each consumer separately. Doctor does not rotate tokens and can skip already-stored names.