Direct contact
Contact Gitae
Gitae is an independent project built by a single developer. If you have a diagnostics question, found a bug, saw a misleading result, want to discuss self-hosting, or want direct contact with the developer, this page is the right place.
Direct contact
Send a message to the developer
Use the form for technical bugs, result mismatches, self-hosting questions, partnerships, or serious feedback about the diagnostics workflows.
What you can write about
Technical bugs, misleading output, copy corrections, route issues, backend questions, self-hosting interest, partnership requests, or thoughtful feedback from real diagnostic use.
This is also the right channel if a public result looks dangerous, obviously wrong, or confusing enough that it needs review.
For diagnostics issues
The most useful reports mention which tool page you used, what public target you tested, the approximate time, and how the result looked wrong compared with what you expected.
If the issue is intermittent, region-sensitive, or depends on redirects, TLS state, or DNS propagation, say that explicitly.
For self-hosting, licensing, or business conversations
Questions about deploying Gitae, adapting it for an internal environment, licensing discussions, partnerships, or infrastructure collaboration can start here as well.
A short message with the practical use case is enough to begin.
For security and public-signal concerns
If you believe a page exposes something misleading, risky, or operationally unsafe, this form is also appropriate for that report.
Do not send secrets, private credentials, or internal hostnames that should never be disclosed publicly.
Developer
Gitae was created by Sergei Solod, an independent developer who loves programming and building useful products.
To learn more about his background and resume, visit jsvar.com.
Contact and support questions
Can I send a bug report through this page?
Yes. Clear bug reports with the tool name, target, and observed mismatch are one of the best uses of this form.
Is copy and explanation feedback useful too?
Absolutely. Diagnostics products depend on precise wording, so explanation quality, correction requests, and translation fixes are valuable feedback.
Should I include secrets or private infrastructure details?
No. Send only the detail needed to explain the issue. Avoid passwords, API keys, credentials, internal hostnames, and other sensitive information.
Can I ask about self-hosting or partnerships?
Yes. Product, deployment, partnership, and business conversations can all begin here.