7 min read · game technologyBuying an SDK, plugin or game-tech company: diligence beyond the code
An SDK’s value depends on customers, integrations, licences, build systems and specialist knowledge—not simply access to its repository.
Game technology is usually sold for its integration footprint, recurring revenue, performance, documentation and specialist know-how—not just a repository. Reconcile customer contracts to billing, versions, engine compatibility, support commitments, security history, service-level promises and concentration risk.
Map every dependency: open-source components, commercial libraries, cloud services, patents, data licences, developer certificates, package registries, marketplace listings and build infrastructure. Confirm the seller can transfer or continue each input and that customers permit assignment or change of control.
Require a reproducible build, clean deployment, key rotation and customer-support handover. Measure the burden of maintaining multiple engine versions and customer forks. A technically impressive SDK can lose most of its value if its licences, signing pipeline or two key engineers do not transfer.