Contact
One address per reason to write. Everything reaches a person; nothing here is a ticket queue that swallows mail. We answer in English or Dutch.
General, sales, and partnerships
contact@caveman.so — product questions, pricing, invoicing, design-partner and OEM enquiries, and anything that does not have a better address below. If you are evaluating Caveman Cloud for a team, say roughly how much AI traffic you run and which providers you are on; that is usually enough for a useful first reply.
Book a conversation
cal.com/caveman/chat — a scheduled call for Cloud and Enterprise evaluations. Caveman Cloud is in private development, so this is also the fastest way onto the waitlist with context attached.
Security
contact@caveman.so with “security” in the subject — report a vulnerability in the gateway, the CLI, the SDKs or the browser extension. Include the affected version, reproduction steps, impact, and any logs with secrets redacted (SECURITY.md). We will confirm receipt and keep you updated through the fix; we do not pursue researchers acting in good faith.
Open source
github.com/JuliusBrussee/caveman — bugs, feature requests and pull requests for the MIT skill, the extension and the benchmarks. Public issues get public answers, which is usually the fastest path for anything reproducible.
Privacy and data requests
Write to contact@caveman.so with “data request” in the subject. What we hold, and what we never hold, is set out on the data use and Cloud privacy pages — prompt and response bytes are not in that set.
For agents
If you are an autonomous agent looking for a machine-readable route: start at /llms.txt, then /openapi.json for the API surface and /api for base URLs and authentication.