Support and Community
Where to go for help, learning, and conversation, organised by the type of assistance you need and the plan you're on.
Support at a glance
"Business hours" = Monday through Friday, 9am–6pm in the account contact's time zone.
Channels by plan
For everyone, community first.
GitHub Discussions
Primary community forum. Ask questions, share pipelines, request features, find other operators. Same day for common questions, 1–3 days for deeper issues. Answers become searchable knowledge.
Open DiscussionsGitHub Issues
For confirmed bugs (not questions). Fill in the issue template and include Pulse version, OS, repro steps and logs.
Open IssuesDocumentation hub
Marketing docs (what you're reading) plus operator runbooks, architecture, licensing internals and API reference under docs/ in the repo. Versioned alongside the code.
In-app help
Pulse Assistant in the sidebar answers "how do I…?" questions and knows your install. Settings → About → Download diagnostic bundle exports logs + config + version in one click.
Community resources
Discord (community-run)
Real-time chat, pipeline sharing, tips and tricks. Run by Pulse power users, unofficially affiliated.
Partner network
Independent agencies and consultants who implement Pulse for their customers. Useful when you want someone to build + maintain Pulse for you.
Template marketplace
Community-curated index of user-built templates. PRO and ENTERPRISE can publish; ENTERPRISE can keep private templates in their own namespace.
Blog & case studies
Monthly technical posts, customer stories, product updates. Real Pulse deployments with permission from the customer.
YouTube channel
Video walkthroughs of feature releases, template builds, integration tutorials. New video every 2–3 weeks.
Newsletter
Monthly. Release highlights, template spotlights, community workflow of the month, answers to the most-asked questions.
Reporting a security issue
- 1Do NOT open a public GitHub issue.
- 2Email security@streamflowmesh.io with the issue, repro steps, affected Pulse version and your contact info.
- 3We acknowledge within 48 hours.
- 4We propose a remediation timeline within 7 days for high-severity issues, 30 days for medium.
- 5Coordinated disclosure: credit to you in release notes (if you want), no public disclosure until a fix ships.
Giving feedback
- Product / feature requestsGitHub Discussions → Ideas category.
- Docs feedbackOpen a PR or file a docs issue.
- Pricing feedbackfeedback@streamflowmesh.io.
- UI/UX feedbackGitHub Issues with the "ui" label.
What we ask of you
- •Read the docs before asking. Most common questions are already answered.
- •Include enough context. "Pulse is broken" is harder to help with than "after upgrading from 0.1.5 to 0.2.0, my job-matcher pipeline stopped emitting events; logs say X".
- •One issue per request. Multiple unrelated problems in one email slows everyone down.
- •Be patient with FREE support. The community volunteers, respect their time.
A note on sustainability
We're a small team. Our ability to keep supporting FREE users at the current level depends on community members helping each other on GitHub Discussions, on PRO and ENTERPRISE customers funding development and support, and on us volunteering some evenings because we love this product. When PRO or ENTERPRISE customers ping us for something a FREE user could answer on Discussions, we usually redirect, not to punish but to keep the forum vibrant and searchable.