---
title: "Contact Caveman"
description: "One address per reason to write. Everything reaches a person; nothing here is a"
canonical: https://caveman.so/contact
last-updated: 2026-08-29
---

# Contact Caveman

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](mailto:contact@caveman.so) — product questions, pricing,
invoicing, design-partner and OEM enquiries, and anything without a better
address below. If you are evaluating Caveman Platform 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](https://cal.com/caveman/chat) — a scheduled call for
Cloud and Enterprise evaluations. Caveman Platform is in private development, so
this is also the fastest way onto the waitlist with context attached.

## Security

[contact@caveman.so](mailto:contact@caveman.so) with "security" in the subject.
Include the affected version, reproduction steps, impact, and any logs with
secrets redacted. We confirm receipt and keep you updated through the fix; we do
not pursue researchers acting in good faith.

## Open source

[github.com/JuliusBrussee/caveman](https://github.com/JuliusBrussee/caveman) —
bugs, feature requests and pull requests for the MIT skill, the extension and the
benchmarks.

## Privacy and data requests

[contact@caveman.so](mailto:contact@caveman.so) with "data request" in the
subject. What we hold, and what we never hold, is set out on
[/data-use](https://caveman.so/data-use) and
[/privacy/cloud](https://caveman.so/privacy/cloud) — prompt and response bytes
are not in that set.

## For agents

Start at [/llms.txt](https://caveman.so/llms.txt), then
[/openapi.json](https://caveman.so/openapi.json) for the API surface and
[/api](https://caveman.so/api) for base URLs and authentication.