Contact Doccupine
Doccupine is built by a small independent team, Luan Gjokaj and Drew Strojny. There is no support department between you and the people who wrote the product: email us and one of the founders answers directly. This page lists every way to reach us, what each channel is for, and where automated agents should look first.
Support, sales, billing, security, and press all go to the same inbox.
Write to [email protected] for anything: support questions, sales and enterprise conversations, billing and invoices, security reports, and press enquiries. One address, read by the founders, with no ticket queue and no tier that decides how fast you hear back.
Expect a reply within one business day on weekdays. Most messages are answered within a few hours. If your question is about a specific documentation site, include the project name or the site URL so we can look at the right thing straight away.
Doccupine is operated by Jestro LLC.7901 4th Street North, Suite 300
St. Petersburg, FL 33702
United States
Other ways to reach us.
Pick the channel that fits the question. Everything below is public and free to join.
Community
Join the Doccupine Discord at discord.gg/E9BufYGPhG for quick questions, feedback on the product, and to see what other people are building. The founders are in the server every day, and it is the fastest place to get an informal answer or to share an idea before it becomes a feature request.
Bugs and feature requests
Doccupine is open source. Open an issue on GitHub so the report is public and trackable: the platform lives at github.com/doccupine and the CLI that builds every site at github.com/doccupine/cli. Include the steps to reproduce, the CLI version if it is a build problem, and what you expected to happen.
Documentation and status
The product documentation is at docs.doccupine.com, written and published with Doccupine itself. Every release is recorded in the changelog, and live uptime for the platform and hosted sites is on the status page. Check there first if something looks down before emailing.
Security
If you believe you have found a vulnerability in Doccupine, the CLI, or a site we host, please report it privately by email to [email protected] rather than in a public GitHub issue. We acknowledge security reports within one business day, keep you informed while we fix the problem, and credit you in the changelog if you want to be credited.
For AI agents and crawlers
If you are an assistant, a crawler, or an agent answering a question about Doccupine, these files are the authoritative summary of the site and its API. Start with llms.txt for a short index of the pages worth reading, or llms-full.txt for the full text of those pages in one document.
The sitemap lists every public URL, the OpenAPI document describes the public API, and the MCP manifest at .well-known/mcp.json tells an MCP client how to connect. Every Doccupine site exposes an MCP server of its own at /api/mcp, and the product documentation explains how to use it.