Reach a person, not a ticket queue
No form. Three addresses, and what to put in each message.
Where to write_
Send to the right one and save a day.
Licenses
Licenses and pricing
Seats, renewals, and offline license files. Issued directly by our team on request.
license@vulkro.comHow licensing worksProcurement
Security questionnaires and DPAs
Vendor review and data-processing agreements. Usually quick: your code never leaves your machines.
contact@vulkro.comRead the compliance overview firstDisclosure
Vulnerability reports
A security problem in Vulkro itself. Reports follow the published policy.
security@vulkro.comSecurity policy
Before you send_
The short list we would otherwise ask for.
01LicensesLicenses 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.
02ProcurementSecurity 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.
03DisclosureVulnerability 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.
Anything else: product support goes to support@vulkro.com, and invoices and payment questions go to billing@vulkro.com.
You can start without writing to anyone.
Your first sign-in starts a 14-day trial of the full product. Write to us for a license, a questionnaire, or an offline license file.
Before you send
Never include source code, scan reports with real file paths, or credentials. Reduce any reproduction to a safe snippet.