Contact Cygan Labs
Need to reach Jacob/Cygan Labs? Email [email protected]. This page is for useful questions, corrections, project notes, and practical technical conversations with enough context to act on.
Cygan Labs is a personal tech lab, not a staffed support queue. Clear, specific, human messages have the best chance of getting a useful reply. Generic outreach, vague pitches, and automated “just checking in” sequences are unlikely to get much attention.
Good reasons to reach out
- You found something broken: a bad link, outdated guide, tool bug, typo that changes meaning, or a project page that needs a correction.
- You have a real question: especially around self-hosting, Plex help, small tools, AI workflows, or systems that are misbehaving in boring but irritating ways.
- You want practical technical help: start with Technical Help & Contact if the question is about troubleshooting, setup, servers, media stacks, or AI workflow review.
- You want to discuss a project: mention the specific project, tool, or page from Projects so the conversation starts somewhere useful.
- You have a relevant collaboration idea: useful, specific, and grounded ideas are easier to evaluate than broad pitches or vague partnership language.
What to include
The best first email is short but specific. Include:
- what page, project, tool, or problem you are writing about,
- what you expected to happen,
- what actually happened,
- what you already tried, if this is a troubleshooting question,
- any relevant device, browser, Plex app, server, or tool details.
You do not need to write a novel. Just give enough context that the reply can start with the actual issue instead of basic clarification.
What probably will not get a reply
- generic link-building pitches,
- generic SEO audits,
- guest-post offers that do not appear to have read the site,
- AI-generated outreach with false personalization,
- messages asking for free emergency support with no useful detail.
Response expectations
This is a personal site, so replies are best-effort. Clear technical questions, legitimate corrections, and specific project notes are the most likely to get attention. Vague outreach, automated pitches, and messages without useful context may not receive a response.
If your question is more about the site itself, start with Start Here or About. If your message involves privacy or editorial standards, these pages may help too: Privacy Policy and Editorial & AI Use Disclosure.
Send the email
Email: [email protected]
Useful subject line examples: “Broken link on Plex Guide,” “Question about SimpleQR,” “Self-hosting backup question,” or “AI workflow review inquiry.” Specific subject lines make it easier to understand and route the message.