Start the right conversation.
Use this page for company, partnership, affiliate, press and wider ecosystem enquiries. Product help, bug reports and feature requests have dedicated support routes.
A clearer path leads to a more useful answer.
Use general contact for company, brand and product conversations. Technical requests work better through the dedicated support workflows.
General enquiries
Company questions, partnerships, press, brand conversations and ideas related to the wider Veyra ecosystem.
Contact support
Installation, configuration, documentation and general help using a published Veyra product.
Report a bug
Reproducible defects, unexpected behaviour and compatibility problems that need a technical investigation.
Suggest a feature
Share the workflow problem, the result you need and why the improvement would be useful in real projects.
Tell us what you’re working on.
Share enough context for us to understand the request and direct it to the right part of the Veyra workflow.
A human review, routed by context.
General messages are reviewed manually. Technical requests may be redirected to documentation, a bug report or the dedicated support workflow.
You provide the context
A concise description helps us understand the request without unnecessary back-and-forth.
We route the message
The enquiry is reviewed according to its topic and moved to the most appropriate workflow.
The conversation continues
When a reply or additional information is useful, the conversation continues through the email address you provided.
Technical work stays structured
Bugs and feature requests remain in dedicated channels so they can be documented and reviewed properly.