简体中文
EnglishWho founded Xeol and how can I contact them?
Updated
Xeol was founded by two technical founders who met during the founding stages of an AI unicorn and have worked together for five years. You can contact them directly at [email protected]. The documentation site also links to their GitHub, LinkedIn, Twitter, and website.
What the documentation says about the founders
The Xeol documentation hub introduces the company briefly and then answers "Who are we?" in a short paragraph. The key facts:
- Two founders, both described as technical.
- They met during the founding stages of an AI unicorn (the company is not named).
- They have worked with each other for five years.
- In past roles they led security, backend, DevOps, and SRE teams.
That background lines up with what Xeol does: it identifies and fixes end-of-life, outdated, and unmaintained open source dependencies — software no longer supported by its publisher and therefore no longer receiving security fixes. Evaluating dependency risk is squarely a security and operations problem, which is the area the founders say they come from.
How to contact Xeol
| Channel | Detail |
|---|---|
| [email protected] | |
| GitHub | Linked from the documentation site |
| Linked from the documentation site | |
| Linked from the documentation site | |
| Website | Linked from the documentation site |
The email address is the only contact method stated explicitly in the documentation text. The social and code links appear in the site's footer under "Data Security," alongside a note that the docs are built and hosted on Mintlify.
What to expect — and what isn't stated
The documentation frames the email as an open invitation: "If you want to chat with us feel free to shoot us a message." It does not specify response times, support tiers, or whether the address is monitored for sales, security reports, or general questions.
If your reason for reaching out is a security vulnerability, note that the docs do not publish a dedicated security disclosure address or process. In that case, it's worth saying so clearly in your first message to [email protected] so it gets routed appropriately.
For background on the product itself before you write, the same page covers what Xeol does; the rest of the documentation hub is the place to check for setup and usage details.