That Open Components
That Open Components is a free MIT-licensed JavaScript toolkit from That Open Company that pairs Three.js with web-ifc so developers import, display, navigate, edit, and export IFC models inside custom web, Node.js, Electron, or React Native apps.
The introduction at docs.thatopen.com states every library in the suite is free and open source, then lists IFC import, display, navigation, editing, and export alongside storage, measurement, annotation, documentation exchange, and integrations with systems such as SharePoint, Power BI, Google Drive, Cesium, and Mapbox (That Open documentation intro, accessed 2026-04-19).
Getting-started material identifies @thatopen/components as the main npm workspace inside the ThatOpen/engine_components monorepo and requires matching three and peer packages @thatopen/fragments plus web-ifc, reflecting a Three.js-first rendering stack for BIM components (That Open documentation, accessed 2026-04-19).
Compatibility notes spell out deployment on vanilla browsers, major frameworks, Node backends, Electron desktops, and React Native or iframe-based mobile shells, which matches how teams embed the same BIM logic across field tablets and office workstations (That Open documentation, accessed 2026-04-19).
The root package.json in ThatOpen/engine_components on GitHub carries an MIT license string and describes the repo as a collection of tools to author BIM apps, which gives a concrete licensing anchor for procurement reviews (GitHub ThatOpen/engine_components package manifest, accessed 2026-04-19).
Specifications
Pricing
Platforms
Used for
Used by
Tasks
Pros and cons
Pros
- MIT-licensed core according to the published `engine_components` package manifest on GitHub.
- Documentation-driven workflow with live examples deployed from the same repositories you install.
- Explicit peer dependency on `web-ifc`, signaling native IFC parsing inside the browser runtime.
Cons
- You must align `three` and `@thatopen/fragments` versions manually as described in the getting-started guide.
- Some roadmap items such as full 3D authoring are still labeled work-in-progress in the intro.
- Building production-grade BIM products still demands security, hosting, and change-management work outside the libraries themselves.
Key features
IFC round-trip in the browser: Intro docs highlight IFC import, visualization, navigation, editing, and export as first-class goals for custom apps.
Component architecture: Documentation frames everything as composable components with global access patterns and explicit Three.js memory lifecycle hooks.
npm distribution:
npm i @thatopen/componentsplus alignedthree,@thatopen/fragments, andweb-ifcversions are the documented install path.Cross-surface deployment: Same components target web clients, Node services, Electron shells, and React Native or iframe mobile integrations.
Ecosystem hooks: Intro copy lists connectors toward common enterprise and geospatial stacks without forcing a hosted viewer SaaS.
Pricing
MIT open-source components
Contact sales
MIT license recorded in `ThatOpen/engine_components/package.json` on GitHub (accessed 2026-04-19). Optional paid accelerator programs are separate vendor offerings.
Frequently asked questions
What license covers That Open Components in our product?
The
ThatOpen/engine_componentsrepositorypackage.jsonon GitHub listslicense: MIT(GitHub manifest, accessed 2026-04-19). Capture the exact commit you ship and keep notices required by MIT alongside your bundle.Which runtimes can host That Open Components besides a public website?
The intro documentation names web stacks, Node.js servers, Electron desktops, and React Native or iframe-based mobile delivery as supported targets (That Open documentation intro, accessed 2026-04-19). Pick the packaging that matches your deployment security model.
Does the toolkit still rely on IFC files or only proprietary meshes?
The intro explicitly promises IFC import, display, navigation, editing, and export, which presumes IFC SPF workflows remain in scope (That Open documentation intro, accessed 2026-04-19). Additional loaders cover other 3D formats mentioned in the same section.
What graphics stack should our team expect to integrate?
Getting-started instructions require
threeplus@thatopen/fragmentsandweb-ifcas peer installs alongside@thatopen/components(That Open documentation, accessed 2026-04-19). Plan for WebGL-capable browsers and GPU memory limits typical of Three.js scenes.Can we connect models to Microsoft 365 or GIS viewers?
The intro lists SharePoint, Power BI, Google Drive, Cesium, and Mapbox among example integration targets for data and geospatial workflows (That Open documentation intro, accessed 2026-04-19). Each connector still needs your own authentication and deployment code.
Where should we report defects or request features?
The introduction directs readers to file issues on GitHub, explicitly naming the
ThatOpen/engine_componentsissues tab when the failing package is unclear (That Open documentation intro, accessed 2026-04-19). Minimal reproducible examples speed triage.