Help
Frequently Asked Questions
Practical answers for the current launch build. This page avoids promising integrations or automation that should still be verified.
What should Product Hunt visitors click first?
They should click Live Demo. That starts a separate demo session and sends them into a seeded workspace with Slack and GitHub sample data.
Is Google sign-in the same as the demo?
No. Google sign-in is for real authenticated workspaces. The live demo is isolated and now clears existing Supabase auth cookies before entering the demo workspace.
Why not ask visitors to connect Slack or GitHub?
OAuth setup is too fragile for a public launch walkthrough. The demo proves the product story with read-only sample sources, then real integrations can be verified in configured workspaces.
What data is shown in the demo?
The demo uses seeded Slack messages and GitHub issues covering authentication friction, API reliability, dashboard UX, onboarding, positive feedback, and mixed feedback.
What parts of the product should I show?
Show dashboard health, feed ranking and filtering, pattern detail, signal volume, and generated epics. That is the strongest end-to-end story.
Are Linear and Jira exports ready for the public demo?
Treat them as configured-workspace features. For Product Hunt, show the generated epic content instead of attempting a live export to a third-party account.
Does the API exist?
Yes. The current public API exposes signals, patterns, pattern detail, and analytics summary endpoints under /api/v1. It requires a workspace API key.
Can demo visitors change data?
The demo is designed to be safe for public visitors. Source setup is read-only, and the sample data can be reset without connecting external accounts.
What should be documented later?
Add full integration guides only after each OAuth flow, permission model, ingestion job, reconnect flow, and export path has been verified in production.
Still unsure what to show?
Use the launch guide. It keeps the demo focused on the flows that are reliable today.