Contact
Three addresses. Pick the right one.
No form. Three addresses, and what to put in each message.
01 / Where to write
Three routes, three inboxes.
Send to the right one and save a day.
Licenses
Licenses and pricing
Pro seats, renewals, and offline licence files, issued directly by our team on request. Free needs no account and no request: the prices and the Free / Pro line are on the pricing page.
Procurement
Security questionnaires and DPAs
Vendor review and data-processing agreements. Usually quick: your code never leaves your machines.
Disclosure
Vulnerability reports
A security problem in Vulkro itself. Reports follow the published policy.
Anything else: product support goes to support@vulkro.com, and invoices and payment questions go to billing@vulkro.com.
02 / Before you send
What to put in the message.
The short list we would otherwise ask for.
Licenses
Licenses and pricing
- Seats, and what you need reviewed: codebase, Salesforce build, or both.
- Whether any machines are air-gapped.
- Contracting entity and country.
- Trial account details, if you already ran it.
Procurement
Security questionnaires and DPAs
- The questionnaire, or a portal link and login.
- Your deadline, and the blocking questions.
- Entity name and jurisdiction for any agreement.
- Whether any evaluation machine is air-gapped.
Disclosure
Vulnerability reports
- The affected version and the platform it runs on.
- The smallest input that reproduces it.
- What you expected, and what happened instead.
- If sensitive, say so and hold specifics until we reply.
Never include source code, scan reports with real file paths, or credentials. Reduce any reproduction to a safe snippet.