Technology Licensing
No storefront, no pretend instant SDK.
If one of our systems looks close to a problem you are solving, we start with the project, not a checkout page. We look at fit, maturity, support needs, and whether source access, package integration, or co-development actually makes sense.
How evaluation works
- 01
Request technical brief
Send the project shape: target platform, Unity version, expected scale, and the toolkit that looks relevant.
- 02
Evaluation call
We talk through fit, maturity, integration risk, and whether the next step belongs under NDA.
- 03
Technical review
Your team gets the useful parts first: architecture notes, integration shape, and benchmarks where they matter.
- 04
License or co-development
If the fit is real, we define source access, package handoff, assisted integration, or co-development.
Possible Models
- Source license for the parts of a toolkit your team needs to own.
- Unity package integration with a real technical handoff.
- Benchmark validation for scale, determinism, or networking needs.
- Assisted integration when the first weeks matter.
- Co-development when the project needs deeper adaptation than a package drop.
What To Include
- Target platform and Unity version.
- Expected player count, entity count, or animation scale.
- Networking, simulation, rendering, or math constraints.
- The toolkit that caught your eye, and why.
- Whether we should talk under NDA before details get specific.
Start with a technical brief request.
Send enough context for an engineer to understand the shape of the problem. We will tell you if the fit is promising, too early, or simply wrong.