Your data. Your machine.
Your rules.
PawPoller holds nothing on your behalf. It runs where you put it, stores credentials encrypted, and never posts anything you didn't confirm — because the person responsible for your accounts should be you, not a service.
Local-first, always
PawPoller runs on your own machine or your own server. There is no PawPoller-operated service in the middle — no central database, no account, and nothing to leak. Your stories and stats never leave infrastructure you control.
Encrypted credential vault
Platform logins can live in an optional Fernet-encrypted store, keyed against your OS keyring or a dotfile. Your plaintext settings.json stays credential-free, so a stray backup or screen-share never exposes a password.
Nothing posts without you
Every publish action has an explicit confirmation dialog, and live (non-draft) posts require a second confirmation. A full dry-run mode shows exactly what would be submitted to each platform without submitting anything.
Hardened dashboard
The self-hosted dashboard uses bcrypt password hashing and signed session cookies, with optional TOTP two-factor, optional Cloudflare Turnstile, and scoped API keys for automation. Legacy plaintext passwords migrate to bcrypt on startup.
No telemetry
No analytics beacons, no phone-home, no usage tracking. The only network calls PawPoller makes are to the platforms you connect and the polls you schedule.
Open source, auditable
MIT licensed and fully on GitHub. Read exactly how credentials are handled, fork it, or run your own build. Nothing about how your data is treated is hidden.
The questions that actually matter.
Where secrets live and what PawPoller will do on your behalf. Still unsure? Open a thread on GitHub Discussions.
Where do my platform passwords live? +
On your own machine or your own server. The optional encrypted vault (Fernet + OS keyring or a dotfile key) stores credentials separately from your plaintext settings.json. No PawPoller-operated service ever sees them.
Does it post things automatically? +
Only when you confirm. Every publish action has an explicit confirmation dialog; live (non-draft) posts require a second confirmation. There is also a full dry-run mode that shows exactly what would be submitted without submitting it.
Is it free? +
Yes. MIT licensed, no accounts, no telemetry, no feature gates. Fork it, audit it, run it forever.
Own your pipeline end to end.
Free, MIT licensed, local-first. Nothing phones home; nothing posts without you.