Skip to content
Provider · Analytics

Plausible — Ashlr Stack Provider

Plausible: Privacy-friendly web analytics. API key verified against the stats API. Wire it into your project with one command via Ashlr Stack.

Analytics · API key KEY-ONLY · v0.2 adds provisioning
Plausible — Privacy-friendly web analytics. API key verified against the stats API.
Dashboard ↗

One command

Add Plausible to any Ashlr Stack project with a single command. Stack runs the auth flow, verifies the credential, and writes every secret slot into Phantom.

stack add plausible

Or describe what you're building and let Claude pick it up via stack recommend:

stack recommend "product analytics and feature flags"

Auth flow

Paste a long-lived API key once. Stack verifies it against the provider's API before writing to Phantom.

How-to: Generate an API key at https://plausible.io/settings and note your site ID.

Secret slots

stack add plausible writes these 2 secret slots into your Phantom vault:

  • PLAUSIBLE_API_KEY
  • PLAUSIBLE_SITE_ID

The values never leave Phantom in plaintext. Your .env file references slot names, and stack exec -- <cmd> swaps them in at process-spawn time via Phantom's local proxy.

  • 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?

Yes — Stack provisions Plausible on your behalf, but it authenticates as you. Paste a long-lived API key once. Stack verifies it against the provider's API before writing to Phantom. If you don't have a credential yet, create one at https://plausible.io and paste it once.

Where does Stack store my Plausible credentials?

In Phantom Secrets, an E2E-encrypted local vault. Stack writes the secret slot names (PLAUSIBLE_API_KEY, PLAUSIBLE_SITE_ID) into .stack.toml — the actual values live only in Phantom and never touch disk in plaintext.

Can I rotate or revoke this integration later?

Yes. Run `stack remove plausible` to pull the Plausible service back out (Phantom secrets deleted, MCP entry removed, .stack.toml cleaned up). Rotate the underlying Plausible credentials in their dashboard — https://plausible.io — and Stack's next `doctor --fix` will pick up the new values.

Outbound