Ace8 is the modernization practice of AceMQ.24/7 support from AceMQ after go-live
Book an Assessment

Stacks we work in

  • Java
  • Spring Boot
  • Kubernetes
  • PostgreSQL
  • Kafka
  • Docker
  • Terraform
  • GitHub Actions
  • Java
  • Spring Boot
  • Kubernetes
  • PostgreSQL
  • Kafka
  • Docker
  • Terraform
  • GitHub Actions
The short answer

A technical due diligence checklist covers eight areas of a software asset: code, architecture, technical debt, security, licences and open source, infrastructure, delivery process and the team. For each area you request evidence, not statements, and you ask a short set of questions that the evidence should answer. Use it before you sign, and again when the seller's answers change.

Next stepFixed-price assessmentInventory, risk score and a phased roadmap with a fixed price for phase one.Book a fixed-price assessment

01 · Start here

How do you use a technical due diligence checklist?

Send the evidence list to the other side first, then use the questions in interviews.

  1. 01

    Evidence comes before conversation because a claim that no document backs up is the finding. Our technical due diligence service follows this order.

  2. 02

    Read access to the repositories matters more than any presentation. If a seller will not grant read-only access under an NDA, record that as a finding in itself.

02 · The checklist

What should be on the checklist, area by area?

AreaEvidence to requestQuestions to ask
CodeRead access to all repositories; commit history; test resultsWho wrote most of it and are they still here? How much is generated or copied?
ArchitectureDiagrams, deployment topology, data modelWhat breaks first at ten times today's load? Which parts nobody dares touch?
Technical debtDependency and runtime versions; open upgrade ticketsWhich frameworks are out of date? What was started and never finished?
SecurityDependency scan, secrets scan, last penetration test, incident logWhere are keys stored? Who can reach production data?
Licences and open sourceBill of materials, licence list, third-party contractsAny copyleft code in the shipped product? Who owns work done by contractors?
InfrastructureCloud accounts and bills, backup and restore recordsWhen was a restore last tested? What does one outage cost?
Delivery processRelease history, CI configuration, on-call recordsHow often does it ship and how often does a release fail?
TeamOrg chart, tenure, documentation, contractor listIf two named people left, what would stop working?

03 · Code and debt

How do you check code quality and technical debt?

Check code quality by reading a sample, running the test suite and counting what is out of date, not by reading a metrics dashboard. A coverage number says little if the tests assert nothing.

01

Run the build from a clean checkout

If nobody has done that recently, expect surprises.

02

List the runtime, framework and database versions and compare them with what their vendors still patch.

03

Look for code that is copied between projects, generated by AI tools without review, or commented out in large blocks.

04

Ask for the three modules the team fears most, then read them.

04 · Risk

What security and licence evidence should you ask for?

Ask for scan output and the history of fixes, because a clean scan today says nothing about how the team handles findings.

  1. 01

    Secrets committed to the repository, unpatched dependencies and missing access reviews are the usual early findings.

  2. 02

    For licences, ask for a bill of materials and the licence of every component that ships to customers. Copyleft terms and unassigned contractor work are the items that can change a deal's terms. This is an engineering check, not legal advice; your lawyers decide what a licence finding means.

05 · Team and process

How do you assess key-person risk and delivery process?

Assess it from the commit history and the release record.

  1. 01

    If one author wrote most of a critical module and has no backup, that is key-person risk whatever the org chart says.

  2. 02

    Release frequency, failed releases and the time to fix a production bug show how the team really works. Ask to see the last three incidents and what changed afterwards.

06 · Output

How do you turn the answers into a decision?

Rate each area red, amber or green, and attach a cost to fix to every red and amber item so the number can enter the deal model.

  1. 01

    See software acquisition red flags for how to price the common ones.

  2. 02

    If the red items are many or the evidence is missing, a deeper code audit of the whole codebase is the next step. Sellers can run the same list on themselves first; see sell-side technical due diligence.

07 · Newer risk

How do you check AI-generated code in a deal?

Treat generated code like any other code and check whether a person reviewed it and a test covers it.

  1. 01

    Large commits with no review, repeated near-identical functions and missing tests are the signs.

  2. 02

    Ask the seller which tools the team uses, which repositories they touched and what the review rule is. The answer tells you more than the code alone, because it shows whether the process catches mistakes.

08 · Timing

When in a deal should you run the checklist?

Run a light version before a letter of intent and the full version after it, inside the exclusivity window.

  1. 01

    The light pass asks only for repository access, versions and the last three incidents, and tells you whether to continue.

  2. 02

    The full pass adds interviews, a clean build and the evidence list above. Send the request on day one, because waiting on documents is the usual cause of delay. See technical due diligence cost for how timing and price relate.

09 · Next step

Who can run this checklist for you?

Ace8 is the modernization practice of AceMQ, and AceMQ engineers run the review.

  1. 01

    We report in plain English, with evidence and a cost to fix, before close. Details are on our technical due diligence page. Quote on request.

FAQ

Frequently asked questions

Short answers to what buyers ask first. Something else on your mind? Ask an engineer.

Code, architecture, technical debt, security, licences and open source, infrastructure, delivery process and the team. Each area has evidence to request and questions to ask.

Start here

Know the cost before anything moves.

A fixed-price assessment gives you the inventory, the risk score and a phased plan. Scope and cost are fixed before the migration starts.

Inventory
Every application, its stack and what it depends on.
Risk score
Where a change is likely to break, ranked.
Phased plan
What moves first, which tools lead, and the fixed price.

Get in touch

Talk to a modernization engineer.

Tell us what you run today. An engineer, not a sales script, replies within one business day.

305-204-2607info@ace8.io

66 W. Flagler St. 9th Floor
Miami, FL 33130

What are you moving off? *

Fixed price. Scope and cost before any migration starts.