01
Support
Threads with statuses, tags, agent replies and a public reporter lookup.
plurism.support
Services
One key. Ten services.
Every service speaks the same envelope, shares the same auth, and ships with its admin already built. Add one and you've learned the shape of all ten — cherry-pick what solves today's pain, wire up the rest when you need them.
02
Analytics
First-party traffic plus a visit → signup → activation → paid funnel.
plurism.analytics
03
Feedback
1–10 ratings with an optional comment, and a stats endpoint per project.
plurism.feedback
04
Feature Flags
On/off flags with a stable rollout percentage on user_id. KV hot path.
plurism.flags
05
Waitlist
Capture → invite, with status moving pending → invited → joined.
plurism.waitlist
06
Content
Blog, news, FAQ and how-to as embeddable HTML with schema.org JSON-LD.
plurism.content
07
Changelog
A public JSON feed with a 60-second cache. Admin CRUD, publish events.
plurism.changelog
08
Files
R2-backed uploads, streamed in and out, allow-listed types with SVG scrub.
plurism.files
09
Webhooks
HMAC-verified inbound, Stripe-style signed outbound, retries up to 20.
plurism.webhooks
10
Notifiers
Rule-based email, Discord and generic HTTP fan-out, SSRF-guarded.
plurism.notifiers
Soon
Transactional mail from your own DKIM-verified domain. Sending opens soon.
plurism.emails
One SDK, one key
Start with two. Add the rest when you need them.
Plurism is invite-only while I stress-test it on real traffic. The waitlist gets first access.