HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
microsoft
TRELLIS
Python2024–2026
microsoft / TRELLIS

TRELLIS

Official repo for paper "Structured 3D Latents for Scalable and Versatile 3D Generation" (CVPR'25 Spotlight).

4Distinct people
7Mentions
0Explicit recommenders
14.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Official repo for paper "Structured 3D Latents for Scalable and Versatile 3D Generation" (CVPR'25 Spotlight).

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month7 dated mentions

Observed mentions: 2024-12-12 16:24:27 UTC to 2026-05-15 21:31:30 UTC.

012342024-12-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 commentsDec 20242025-01-01 00:00:00 UTC to 2025-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-01 00:00:00 UTC to 2025-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-01 00:00:00 UTC to 2025-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-01 00:00:00 UTC to 2025-05-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2025-05-01 00:00:00 UTC to 2025-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-01 00:00:00 UTC to 2025-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-01 00:00:00 UTC to 2025-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-01 00:00:00 UTC to 2025-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsAug 20252025-09-01 00:00:00 UTC to 2025-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-10-01 00:00:00 UTC to 2025-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-01 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-01-01 00:00:00 UTC to 2026-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-01 00:00:00 UTC to 2026-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-01 00:00:00 UTC to 2026-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-01 00:00:00 UTC to 2026-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-01 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMay 2026

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Dec 20242024-12-01 00:00:00 UTC2025-01-01 00:00:00 UTC413
Jan 20252025-01-01 00:00:00 UTC2025-02-01 00:00:00 UTC000
Feb 20252025-02-01 00:00:00 UTC2025-03-01 00:00:00 UTC000
Mar 20252025-03-01 00:00:00 UTC2025-04-01 00:00:00 UTC000
Apr 20252025-04-01 00:00:00 UTC2025-05-01 00:00:00 UTC110
May 20252025-05-01 00:00:00 UTC2025-06-01 00:00:00 UTC000
Jun 20252025-06-01 00:00:00 UTC2025-07-01 00:00:00 UTC000
Jul 20252025-07-01 00:00:00 UTC2025-08-01 00:00:00 UTC000
Aug 20252025-08-01 00:00:00 UTC2025-09-01 00:00:00 UTC000
Sep 20252025-09-01 00:00:00 UTC2025-10-01 00:00:00 UTC000
Oct 20252025-10-01 00:00:00 UTC2025-11-01 00:00:00 UTC000
Nov 20252025-11-01 00:00:00 UTC2025-12-01 00:00:00 UTC000
Dec 20252025-12-01 00:00:00 UTC2026-01-01 00:00:00 UTC101
Jan 20262026-01-01 00:00:00 UTC2026-02-01 00:00:00 UTC000
Feb 20262026-02-01 00:00:00 UTC2026-03-01 00:00:00 UTC000
Mar 20262026-03-01 00:00:00 UTC2026-04-01 00:00:00 UTC000
Apr 20262026-04-01 00:00:00 UTC2026-05-01 00:00:00 UTC000
May 20262026-05-01 00:00:00 UTC2026-06-01 00:00:00 UTC101

What Hacker News says

7 sources
Since they explained that they used an open source model and system https://github.com/Microsoft/TRELLIS, it will be possible for other developers who want to start similar businesses to launch basic competitors within a week or so, if they are ambitious about it. I spent about 10 minutes with my agent running Claude 3.5 Sonnet New and generated most of the core code already: https://github.com/runvnc/img2blender Although I haven't tested that and don't actually know if it will work.
In BlenderGPT
I think that's a fair point that not every company owes the end user a recipe for how to reproduce their product. However, it's also a fair question on Hacker News. Again, fair if they chose not to answer it.. but many people here are programmers. Since they explained that they used an open source model and system https://github.com/Microsoft/TRELLIS, it will be possible for other developers who want to start similar businesses to launch basic competitors within a week or so, if they are ambitious about it. I spent about 10 minutes with my agent running Claude 3.5 Sonnet New and generated most of the core code already: https://github.com/runvnc/img2blender Although I haven't tested that and don't actually know if it will work.
In BlenderGPT
Understandable. For context, the GPT in the name comes from an earlier version of this project (https://github.com/gd3kr/blendergpt) which actually used GPT-4 to write python scripts that Blender would then execute. This would allow GPT-4 to program operations like instantiating primitives with the Blender Python API given only a text prompt (ex. "create 50 cubes") The new version of BlenderGPT (lets call this v2) doesn't use an any autoregressive token prediction for the actual mesh generation part, so I understand why it sounds dishonest. I really just chose to stick with the name because artists really didn't seem to care about how the meshes are generated, and the term GPT became closely associated with AI. As for the technical stuff, I've been working on BlenderGPT v2 for the past several months, and until a week ago, i had been usin
Read the rest
g a custom pipeline I built borrowing and re-implementing bits of Unique3D (https://wukailu.github.io/Unique3D/) and combining it with optimized models (flow matching diffusion models etc) for intermediate steps (text to image generation). My optimizations reduced inference time from >2 minutes to only about 20 seconds. This is the model used in this demo i shared: https://x.com/gd3kr/status/1853645054721606100 And then Microsoft released Trellis (https://github.com/microsoft/TRELLIS), and it seemed to leapfrog my model's capabilities on most things. Integrating it into the pipeline wasn't too hard and so I went forward with it. All of this is just to say that there really was a lot of effort put into the core pipeline, and the landing page was mostly an afterthought. Actively working on a more comprehensive one that covers all the points I talked about.
In BlenderGPT

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.