Contact
Demo requests, procurement questions, and technical follow-up all start here. The more specific the request, the shorter the first call.
Demo requests
Four things make the first conversation useful. Send them to sales@snyte.ai and the reply can be specific.
01
Database engines, warehouses, event feeds. Names are enough; the connector catalog says what each one can do.
02
A single host on Docker Compose, a Kubernetes cluster, or something else. Snyte is self-hosted, so this shapes the walkthrough.
03
Name the provider you sign in with, so the login path can be shown the way your users would see it.
04
Two or three real ones. A walkthrough against your questions is worth more than one against ours.
Then
Someone reads the request and writes back to confirm the sources, the deployment target, and the identity provider. If a connector in your list is an event-ingestion mapping rather than a SQL connector, that is said up front.
The demo runs the questions you sent: ask, read the plan, read the trace. If the path holds up, the rest of the evaluation is a conversation about rollout.
Procurement and security reviewers usually want the written posture before the call. It is published, including the controls that are partial or absent.
Other requests
Write to support@snyte.ai with the affected route, the data source, and the time window, so logs can be matched to what you saw. Never include passwords or API keys.
Requests to access, correct, or delete personal information go to privacy@snyte.ai, the contact named in the privacy policy.
security@snyte.ai is the incident contact named in the data processing agreement. Your operator is the first call for anything inside your perimeter; include Snyte when the incident touches the application itself.