Contact
Describe the problem; an engineer reads every message.
Let's Get Started
The most useful first message names your stack (Elasticsearch or OpenSearch, version, roughly how big), the pain (cost, latency, relevance, stability, or a looming migration), and what triggered it. A paragraph is plenty — we'll reply with a concrete next step, and the first conversation is free.