Loading…
One page that names every place to reach Osyra by purpose. No phone tree, no contact form — pick the alias that fits your reason for writing. Response targets are shown where the team has defined one.
The five primary contact addresses. Each routes to a rotation rather than an individual so vacation, attrition, or an out-of-office never leaves a request unowned.
Enterprise demos, proof-of-concept scoping, contract negotiation, custom integrations. Routes to the inbound sales rotation. Prefer the structured form at /demo for new opportunities — it pre-routes the lead to the right rep.
Customer support — bug reports, billing questions, account issues. Routes to the support rotation; include your workspace and, where relevant, a request ID so we can trace it.
Vulnerability reports, coordinated disclosure, incident communications. Full responsible-disclosure policy at /legal/security and the RFC 9116 record at /.well-known/security.txt.
Data-protection requests, subject-access requests (GDPR Art. 15, CCPA right to know), deletion requests, processor / sub-processor inquiries. Routes to the privacy officer.
Pre-release Data Processing Addendum review requests. The package is designed to incorporate applicable EU SCCs and UK transfer terms; customer-specific review and execution are required before production processing.
Press inquiries, analyst briefings, embargoed releases. Includes Osyra Labs research-paper coverage requests.
Integration partners, technology alliances, channel programs. Currently scoping V1.1 partner program — expect a slower response while the framework lands.
Open roles, interview prep questions, recruiter introductions. The canonical careers page lives elsewhere — this address is for direct contact when nothing fits the listed roles.
Office-hours interest, real-time chat platform vote, contributor questions. The public community surface lives at community.osyra.ai.