Questions, answered plainly.

xeoVision is a framework for creating BIM business solutions from Creoox AG. It combines xeokit SDK for visualization, xeokit Data Engine for supported engineering-file processing, reusable application foundations, and advice and integration services.

The working xeoVision application demonstrates selected viewing and data workflows. A solution built with the framework has its own agreed components, branding, integrations and deployment. Explore the framework and its scope.

xeoVision is made by Creoox AG, registered in Triesen, Liechtenstein. Creoox AG also maintains the open-source xeokit SDK and the xeokit Data Engine, which xeoVision is built on.

xeokit SDK provides the visualization foundation within xeoVision. xeokit Data Engine supplies selected engineering-file processing. xeoVision brings these technologies together with a ready-made application framework, reusable workflows, advice and integration services to help you deliver a business solution.

Developers can work directly with the SDK’s JavaScript API and plugins to shape interfaces and functionality. The framework gives your team and partners an assembled starting point while preserving access to the underlying technology. Explore how the framework fits together.

The xeoVision framework supports IFC 2x3, 4 and 4.3, Autodesk Revit RVT and RFA, STEP, Autodesk Navisworks and AVEVA E3D and PDMS workflows through selected xeokit Data Engine processors. xeokit SDK loaders handle supported point-cloud and web-ready formats, including LAS/LAZ, OBJ, STL, CityJSON and glTF/GLB. The full matrix, including which processors are announced but not yet available, is on the formats page.

Yes. xeoRVT reads Autodesk Revit RVT and RFA files directly and produces GLB, JSON and XKT. The processing step does not require a Revit installation, an Autodesk Platform Services subscription, or an intermediate IFC export. This covers viewing and processing files you supply; it is not a statement about Revit authoring rights.

xeoRVT is the xeokit Data Engine processor for Autodesk Revit files. It reads RVT project files and RFA family files and extracts geometry and model information into GLB, JSON and XKT, without an intermediate IFC conversion.

The xeokit Data Engine outputs JSON for object properties and metadata, GLB for geometry in a widely supported 3D format, and XKT, xeokit’s compressed format for fast browser loading. All three are open formats your own systems can read without going back through xeoVision.

Yes. Solutions built with the xeoVision framework can use a managed service operated by Creoox AG, dedicated infrastructure, or an environment you control. Agree where the application, selected processors and project data run. xeokit Data Engine also provides a standalone command-line binary so supported file processing can stay inside your network. Review deployment options.

The xeokit Data Engine standalone binary runs on Windows AMD64, Linux AMD64 and Linux ARM64.

Not necessarily. With a self-hosted or standalone deployment, the xeokit Data Engine processes files inside your own environment, so there is no requirement to send project files to an external conversion service. With the managed service, processing runs on infrastructure operated by Creoox AG.

A closed-network deployment has to be verified end to end for the specific case — identity, processors, licensing, telemetry, fonts and assets, installation and updates. Creoox AG can describe how each part behaves and work through it with your security team. No blanket air-gap guarantee or security certification is claimed.

The xeokit SDK within the xeoVision framework is open source under AGPL-3.0, with commercial licensing available from Creoox AG where those terms do not fit. The framework combines components with their own terms; the SDK licence does not apply automatically to the whole solution. Source code for the application foundations is available as an add-on to a xeokit SDK licence, with the delivery scope defined by agreement.

The xeokit SDK is licensed under AGPL-3.0, with a commercial licence available from Creoox AG for organizations that cannot work within AGPL terms.

Source code for the xeoVision framework’s application foundations is available as an add-on to a xeokit SDK licence. The agreement defines the delivered code and development rights, so your team or partner can brand and extend the application and manage its roadmap. Source-code access does not convey ownership of third-party intellectual property.

An iframe embed places a live project view inside your own page, with authentication and project permissions configured for your audience. A branded deployment runs the application in your layout and identity. The underlying xeokit SDK gives developers direct access to the visualization API and plugins to shape interfaces and functionality. Creoox or your integration partner can help define and implement the scope that fits your product.

Yes. A business application built with the xeoVision framework can carry your layout, palette and identity. With agreed application source-code access, your developers or partner can extend the interface and functionality further.

Yes, as a data integration. The xeokit Data Engine writes object properties and metadata as JSON, which Power BI can consume. Power BI is a separate application: the data preparation and the connection itself depend on your workflow, and no Power BI connector ships with xeoVision.

Model object data can be connected to ERP systems including SAP, project management tools and document management systems. These are development possibilities built against those systems’ APIs and your access policies, not preconfigured connectors that ship with the product. The open JSON output is what makes them straightforward to build.

No. The xeoVision framework does not bundle an AI model. xeokit Data Engine provides extracted project data for a scoped integration with an agent your organization has approved. You decide what data may leave the project and where inference runs. Generated answers should be reviewed against the source project information.

Yes. In xeoVision, project visibility and source-file access are separate controls, so a client can review a project without being given the authored IFC or RVT behind it. Restricting file access does not prevent viewers from taking screenshots or recording information visible on screen.