ThreeUI open-sources 160 Three.js components for agent-built sites

• Free access arrived as an editable catalog: the 160+ components in MengTo's launch post cover procedural 3D hero sections, icons, and motion designs.
• MengTo's early preview described each template as 100 to 200 KB of procedural JavaScript, built to be copied as code or prompts and reshaped by an agent.
• The public catalog keeps free variants and controls, while the launch post places MCP, skills, and more components in Pro.
• Pro has an unsettled-looking count: MengTo's launch post says 50+, while MengTo's Pro count puts the number at 60; MengTo's commercial-use reply also directs commercial use to Pro.

In MengTo's explanation, he says ThreeUI began as a tool built for him before other people asked for it. The public ThreeUI repository includes the source bundles behind its Code tab, while the live catalog is the browser for the components themselves.

The launch advertises 160+ free components. The Community README gives a more precise inventory, where 164 is a count of browse results built from several layers:

• 50 Community parent components
• 111 Community routes
• 141 free variant records
• 23 singleton components

The free edition retains the main product's application shell, search, themes, responsive behavior, live renderers, controls, variant picker, and source tabs. Each Community component keeps its free variants and controls.

MengTo's early preview says the templates are written entirely in procedural JavaScript, at roughly 100 to 200 KB apiece. The launch post defines the handoff as a short sequence:

1. Copy a component's prompt or source.
2. Give it to an agent.
3. Change the theme, lighting, motion, or layout.

That makes the visual treatment editable after the initial selection, rather than leaving creators with a rendered reference alone. The Community repository ships the complete implementation source and required assets for its included catalog.

Alongside Three.js, MengTo says the library uses regular CSS and shaders in MengTo's rendering note. He describes some Three.js treatments as vector-like 3D work that can stay lightweight, and has also said he uses the medium for motion design in a reply about motion design.

MengTo's stated rendering and tuning model has three parts:

• Rendering: Three.js, CSS, and shaders can coexist.
• Visual target: some 3D treatments can resemble vector work.
• Device adaptation: when asked about older hardware, MengTo said an agent could improve performance or make a component adaptive in MengTo's performance reply.

The Community source has a deliberately narrow publication boundary:

• It includes Community implementation code and required assets.
• It excludes authentication, account state, checkout runtime, and Pro and Beta implementations.
• Its license documentation identifies the application code, Community component code, and ThreeUI-authored Community imagery as MIT licensed. Bundled fonts and the Three.js runtime retain their own licenses, and remote catalog previews are not redistributed.

The paid offer is described in three different places: the launch says Pro adds 50+ components, MCP, and skills; a later reply says 60 components are Pro; and MengTo's commercial-use reply says commercial use is covered by Pro. The README does not spell out how that commercial-use answer maps onto the MIT-licensed Community code.