Skip to main content

Contact

Three addresses. Pick the right one.

There is no form on this page. A form that cannot tell you where your message went is worse than an address that works, so this page does the routing instead: who to write to, and what to put in the message so the first reply is an answer rather than a request for more detail.

Start the 14-day trialEnterprise and air-gapped →

01 / Where to write

Three routes, three inboxes.

Sending to the right one saves a day. All three are read by our team, so a message in the wrong inbox still gets an answer, it just takes longer.

Licenses

Licenses and pricing

Seats, renewals, offline license files, and anything about what a license covers. Licenses are issued directly by our team on request, and pricing is quoted the same way. You do not need to write here to start: a 14-day trial of the full product begins on your first sign-in from the command line.
[email protected]How licensing works →

Procurement

Security questionnaires and DPAs

Vendor review, data-processing agreements, and the questions your security team has to see answered before a tool gets installed. Most of them come down to one fact (your code never leaves the machines you own), so these are usually quick.
[email protected]Read the enterprise page first →

Disclosure

Vulnerability reports

A security problem in Vulkro itself: the scanner, the console, the way vulnerability data is published, or this site. Reports go to the security address and follow the published policy. Please read the policy before you send, so you know what is in scope and what to expect back.
[email protected]Security policy →

Anything else: product support goes to [email protected], and invoices and payment questions go to [email protected].

02 / Before you send

What to put in the message.

None of this is a form to fill in. It is the short list of things we would otherwise have to ask for, which is the difference between a reply today and a thread that runs all week.

Licenses

Licenses and pricing

  • How many seats, and what you need reviewed: your codebase, your Salesforce build, or both.
  • Whether any of those machines are air-gapped, so we issue a license file instead of a sign-in.
  • The contracting entity and country, which is what the quote is built against.
  • If you already ran the trial, the account details the product shows you on your own machine, which tell us which seat to look at.
[email protected]

Procurement

Security questionnaires and DPAs

  • The questionnaire itself, or a link and a login if it lives in a portal.
  • Your deadline, and which questions are blocking so we answer those first.
  • The entity name and jurisdiction for any agreement you need signed.
  • Whether any evaluation machine will be air-gapped, which changes several answers.
[email protected]

Disclosure

Vulnerability reports

  • The affected version and the platform it runs on.
  • The exact command, and the smallest input that reproduces the behaviour.
  • What you expected to happen and what happened instead.
  • If the detail is sensitive, say so in the first line and hold the specifics until we reply.
[email protected]

One thing never to include: your source code, a scan report with real file paths in it, or a credential. We do not need any of it to answer a question, and Vulkro is built so that none of it reaches us in the first place. If a reproduction needs code, reduce it to a snippet that is safe to send.