Choose which optional cookies and similar storage we may use. Strictly necessary storage is always on, because the site cannot work without it.
Talk to us
Beta

Gateway Assay: code review and technical due diligence

Know what you are buying before you sign.

Gateway Assay is Gateway Global's code review and technical due diligence product. It is built for investors and acquirers who need to understand a technology company's code, risks and potential before they invest or buy. The beta runs privately.

Request a code review Or have our team run the due diligence

Last updated

Code under review, with one finding flagged: a concept drawing.

Who it is for

  • Investors. Venture capital and other investors assessing a company before they invest.
  • Private equity and acquirers. Deal teams and corporate development assessing a company they plan to buy, including the use cases its technology can support.
Draft (D4): Founders preparing to raise (vendor due diligence) is a proposed offer to confirm.
  • Founders. Founders who want to find and fix issues before investors do.
Draft (D4): What Gateway Assay examines: list only what the product does.

What it examines

[TO CONFIRM: the confirmed list from D4]

Two ways to work with us

Use Gateway Assay yourself, or ask us to carry out the due diligence for you.

Use Gateway Assay yourself

Your team runs it and reads the output.

  • Your team runs it.
  • Your team reads and interprets the output.

Choose this when your team has the engineering time to read the output and act on it.

We run the due diligence for you

Our engineers use Gateway Assay and add expert review, interviews and a written report.

  • Our engineers run it.
  • We add expert review and interviews.
  • You receive a written report.

Choose this when you want an independent assessment, or your team has no engineers free to do it.

Draft (F5): How an engagement runs: confirm each step.

How an engagement runs

  1. Scope and non-disclosure agreement

  2. Secure, read-only access

  3. Automated analysis

  4. Expert review

  5. Report

  6. Debrief with your team

Draft (D4): What you receive (deliverables) and how we handle your code.

What you receive

[TO CONFIRM: deliverables, for example executive summary, risk register, scores, remediation estimate, use-case map]

How we handle your code

[TO CONFIRM: read-only access, encryption, retention and deletion, where processing happens, and whether client code is ever used to train models]

Beyond risk

Due diligence is not only about what could go wrong. We also look at the use cases a company's technology can support, to inform value creation and integration planning.

Draft (F5): Sample report: a synthetic, clearly labelled example, once produced.

Sample report

[TO CONFIRM once produced]

Questions people ask

What is technical due diligence?

Technical due diligence is an independent assessment of a company's technology before an investment or acquisition: how its software is built, what risks it carries, and what it could support in future.

Draft (D4): Turnaround.
How long does it take?

[TO CONFIRM: Turnaround.]

Draft (D4): How client code is accessed and handled.
Do you need access to the source code?

[TO CONFIRM: How client code is accessed and handled.]

Draft (D4): Answer "No" only if true.
Is our code used to train AI models?

[TO CONFIRM: Answer "No" only if true.]

Draft (D4): The vendor due diligence offer for founders.
Can founders use it before fundraising?

[TO CONFIRM: The vendor due diligence offer for founders.]

Draft (D4): Pricing.
How is it priced?

[TO CONFIRM: Pricing.]

Know what you are buying before you sign.

Request a code review See our technical due diligence service