Contact Varve
Varve publishes a separate email address for each kind of inquiry, so your message reaches the right place the first time. These addresses are public project channels maintained by Varve's maintainer.
General inquiries
General questions about Varve, and the right address when no other channel fits.
- General questions about the project
- Initial business contact
- Anything you are not sure where to send
Product support
Help installing, launching, or using Varve, including platform-specific problems.
- Installation and download problems
- The application will not start or misbehaves
- Questions about how to do something in Varve
- Private support questions you would rather not post publicly
Product feedback
Suggestions, feature ideas, usability feedback, and interest in user research.
- Feature ideas and workflow suggestions
- Usability and interface feedback
- Interest in taking part in user research
Security
Private reports of security vulnerabilities in Varve, its build pipeline, or its releases.
- Vulnerability disclosures
- Supply-chain concerns
- Signing or update-integrity problems
- Suspected credential exposure
Privacy
Questions about what Varve collects, analytics and crash-reporting consent, and data handling.
- What a build does or does not collect
- Analytics, diagnostics, and crash-reporting consent
- Update-check and model-download network behaviour
- Privacy-related requests
Press and media
Media inquiries, interviews, review requests, and brand assets.
- Interview and review requests
- Product coverage questions
- Logo, wordmark, and screenshot requests
Partnerships
Integration, distribution, education, and organisational inquiries.
- Integrations and interoperability
- Packaging and distribution
- Education and organisational use
- Sponsorship conversations
Email, GitHub issues, or Discussions?
Three channels, three different jobs. Picking the right one gets you a faster answer.
- Open a GitHub issue
- For a reproducible, non-sensitive bug or a concrete feature request. Public issues let other users find the problem, add detail, and see the fix land.Varve issue tracker
- Ask in GitHub Discussions
- For questions, workflow advice, and ideas that benefit from other users answering. Discussions are public.Varve Discussions
- Email support@varve.studio
- For installation help, general questions, and anything you would rather not post in public.
- Email security@varve.studio
- Required for security vulnerabilities. Please do not put vulnerability details in a public issue or discussion.Varve security policy
What to expect
Varve is built by a very small team, so email is answered as soon as it reasonably can be rather than on a service-level agreement. There is no phone line and no 24/7 desk. Security reports are prioritised; the security policy describes the private disclosure process.
Email works from anywhere in the world. Varve is currently able to correspond in English only.
Common questions
- How do I contact Varve?
- For general inquiries, emailhello@varve.studio.
- How do I get help with Varve?
- Emailsupport@varve.studio, or read the Varve support documentation.
- How do I report a Varve security vulnerability?
- Report vulnerabilities privately tosecurity@varve.studio, or useGitHub private vulnerability reporting. Please avoid posting sensitive vulnerability details publicly.
- How do I send feedback to Varve?
- Emailfeedback@varve.studio.
- Who do journalists contact about Varve?
- Press inquiries can be sent topress@varve.studio. Logos, screenshots, and product facts are on thepress and brand assets page.
- How do I discuss a partnership with Varve?
- Emailpartnerships@varve.studio.