TripoSR License: MIT, Including Commercial Use
Short answer: yes, you can use TripoSR commercially. The project is released under the MIT license, and the official README states that this covers the source code, the pretrained models, and the interactive demo. There is no separate research-only tier, no revenue share, and no commercial add-on to buy. What follows is the part that actually matters once you ship: the one obligation MIT does impose, the usage guideline the model card adds on top, and where the hosted Triposr.org service sits relative to all of it.
The MIT LICENSE file
The authoritative text, in the official VAST-AI-Research repository. If you are making a licensing call for your company, this file is the source of truth and everything on this page is a reading of it.
Model card and weights
The pretrained weights on Hugging Face, carrying the same MIT license tag. The card also states a usage guideline about output, which is a stated expectation rather than a clause of the license itself.
The TripoSR paper
Fast 3D Object Reconstruction from a Single Image, the technical report behind the model. Cite this if you are using TripoSR in academic work or need the attribution details for a research release.
The four questions people actually ask
These are the licensing questions that bring people to TripoSR, phrased the way they get searched. Direct answers first, primary sources linked above.
Can I use TripoSR in a commercial product?
Yes. MIT is a permissive license, and permissive means commercial use is granted by default rather than by exception. You can put TripoSR inside paid software, use its output in work you sell, and ship it to customers without asking anyone for permission.
Does it cover the weights, not just the code?
Yes, and this is the part people get wrong with other 3D models. The README states the MIT license includes the pretrained models, and the Hugging Face card carries the same MIT tag. Many rival models split this, with open code and restricted weights.
What does MIT actually require from me?
One thing: keep the copyright notice and the permission notice in copies or substantial portions of the software. In practice that means shipping the LICENSE text somewhere in your product, usually a third-party notices file. That is the whole obligation.
Does the hosted Triposr.org use the same license?
No, and the distinction matters. MIT governs the open-source model you run yourself. Triposr.org is a hosted service built on it, so your use of this website is governed by our Terms of Service, while what you do with the model on your own hardware is governed by MIT.
Three scenarios, resolved
Most licensing questions are really one of these three situations. Find yours and the answer is already decided by the MIT text.
Ship it inside a paid product
Allowed. Embed TripoSR in desktop software, a game pipeline, or an internal tool you sell. Include the MIT notice in your third-party attributions and you are done. No royalty, no revenue share, no usage cap.
Offer it as a hosted service
Allowed. You can run TripoSR on your own servers and charge users for access. MIT places no restriction on service resale, which is the clause that trips people up under source-available licenses like SSPL or BSL.
Fork, modify, and redistribute
Allowed, including under a different license. MIT lets you relicense derivative work, so a fork can be closed source. You still carry the original notice for the MIT-covered portions you kept.
One honest caveat
This page is a plain-language reading of a license, not legal advice, and we are the operator of a product built on TripoSR rather than a neutral party. Licenses also get amended. Before you commit engineering work or sign a customer contract on the strength of it, open the LICENSE file in the official repository and read the current text yourself. If your situation involves patents, trademark use, or redistribution at scale, talk to a lawyer rather than to a website.
TripoSR licensing FAQ
Licensing settled? Go make something.
You can run the open-source model yourself under MIT, or skip the setup entirely and generate in the browser on cloud GPUs. Both paths start from the same model.
