Skip to content

Your BIM data.
Processed in your environment.

Considering Autodesk Platform Services (APS), formerly Autodesk Forge?

xeoVision is a framework that brings together xeokit SDK, xeokit Data Engine, reusable solution components, and our advice and integration services. Build your business solution around your own infrastructure and requirements.

IFC models. Revit RVT & RFA files. xeokit Data Engine processes IFC models through xeoIFC, and Revit project files (RVT) and family files (RFA) through xeoRVT. [2] [3]

A focused comparison. This page compares the xeoVision framework with the APS cloud Model Derivative and Viewer approach for supplied IFC and Revit files. It does not compare every APS API or Autodesk desktop capability, or imply a drop-in replacement.

Bring the processing to your data.

How does BIM data get from project files to a business solution?

Within the xeoVision framework, xeokit SDK provides model visualization and xeokit Data Engine handles file processing. Reusable application foundations, additional components and our advice and integration services connect these technologies to your business workflows.

Your deployment environmentConceptual architecture
  1. 01 / PROJECT FILES

    IFC + Revit

    Your supplied IFC, RVT and RFA files.

    IFC · RVT · RFA
  2. 02 / PROCESSING

    xeokit Data Engine

    Process with the selected xeoIFC and xeoRVT components.

    Geometry + properties
  3. 03 / OUTPUTS

    Data you can use

    Store model outputs for viewing and downstream workflows.

    JSON · GLB · XKT
  4. 04 / YOUR SOLUTION

    Your business solution

    Built with the xeoVision framework, with model viewing powered by xeokit SDK.

    Your brand + integrations
One possible deployment, configured to your requirements. External integrations, authentication, licensing and operational dependencies are reviewed as part of the complete solution. [2] [3]

Process Revit RVT & RFA files directly

xeoRVT, part of xeokit Data Engine, reads RVT project files and RFA family files without requiring an APS connection, a Revit installation or an intermediate IFC export. Validate supported versions and extraction results with representative files. [3]

Put your operating policies into practice

Design storage, retention, access, backups and update windows around your organization. Your team, partner or an agreed service operates the environment.

Start closer to the application

Combine ready-made project and model workflows with the implementation expertise needed to connect your business systems. Explore the framework →

Compare the approach.
Choose for your requirements.

What is the difference between xeoVision and Autodesk Platform Services?

Both approaches support custom BIM applications. The central distinction here is where processing runs and how the complete solution is assembled and operated.

xeoVision framework and Autodesk Platform Services comparison for supplied IFC and Revit files
Your decisionxeoVision frameworkxeokit SDK + xeokit Data Engine + solution components + servicesAutodesk Platform ServicesAPS cloud Model Derivative + Viewer approach
Where model processing runsIn your own environment. Deploy the selected xeokit Data Engine processors on supported infrastructure, including on-premises. A managed service is also an option. [2]Model Derivative processing uses Autodesk’s cloud service. Autodesk’s current FAQ states that a private-cloud/self-hosted offering is not available. [1]
Application hosting and locationChoose your server, data centre or cloud region. Scope application and processing deployment against supported runtimes, licences and infrastructure requirements. [2]Your custom application can be hosted separately; the processing service remains Autodesk-hosted. Cloud API availability varies by region. [5] [7]
Processed-data storageKeep files and outputs on your infrastructure. Configure storage, access and retention together with the processing and application deployment.Supported derivatives can be downloaded and stored on your infrastructure for local or offline viewing. This does not relocate the original cloud conversion service. [6]
Using the extracted dataWork with JSON, GLB and XKT outputs. Use selected outputs in the application and your reporting or integration workflows, subject to data rights and implementation scope. [2] [3]Model Derivative provides translated models and metadata APIs. Derivative downloads are available; data extraction and reuse are also possible with APS. [4]
Operating responsibilityControl the environment for your solution. Deploy the selected framework components and agree ownership of capacity, security, retention, backups and update windows with your operations team or service partner.Autodesk operates the cloud processing service. You remain responsible for your application, access controls, integrations and relevant data policies. [1]
Starting point and customizationTechnology, reusable foundations and delivery expertise. Scope branding, workflows and integrations together. Application source-code access is a licensed add-on. Framework and source terms →Developer APIs and Viewer SDK, with Autodesk resources and a certified partner ecosystem for custom solutions. [1] [5]
The complete costA solution-specific scope. Include component licences, source-code rights where needed, implementation, infrastructure, maintenance and support.Free and usage-billed cloud API tiers, plus application development, hosting and support costs. Actual cost depends on the APIs and usage. [8]

Self-hosting is an architectural choice, not a security certification or a promise of lower total cost. Compare the complete deployment and operating responsibilities. Sources reviewed on .

Start with your business priorities.

Should you choose xeoVision or Autodesk Platform Services?

Consider xeoVision when…

  • IFC and Revit processing needs to run inside your chosen environment.
  • Your team needs control over application deployment and project-data operations.
  • You want a branded business solution with reusable application capabilities and integration expertise.
  • You need to connect model data to existing asset, project or reporting systems.
Explore deployment & independence →

Consider APS when…

  • Autodesk-hosted model processing fits your requirements.
  • Your solution depends on other Autodesk platform APIs or Autodesk-connected workflows.
  • You want Autodesk cloud design automation, which is outside this xeoVision comparison.
  • Your team or partner plans to build using the APS developer ecosystem.
Explore Autodesk’s APS overview ↗

Planning a solution for critical infrastructure?

Start with the data boundary, access model and operating responsibilities. We can assess a deployment around your security and governance requirements.

Explore the use case →

Evaluate with your files.
Plan the complete solution.

How do you evaluate an APS alternative with your own files?

Bring representative IFC and Revit files, your intended workflow and deployment requirements. Together, we can define a useful first release and the work needed to deliver it.

  1. 01

    Prove the workflow

    Check file versions, geometry, properties, relationships and the user experience with your actual data.

  2. 02

    Confirm the environment

    Validate compute, storage, access, licensing and integrations. Agree security, backups, monitoring and updates.

  3. 03

    Agree the delivery

    Define the application scope, source-code rights, implementation responsibilities and full operating cost.

How does xeoVision relate to xeokit SDK?

xeoVision is a framework for creating business solutions. It brings together xeokit SDK, xeokit Data Engine, reusable solution components, advice and integration services. xeokit SDK remains the visualization foundation within that framework; xeoVision is neither a standalone application nor a replacement for xeokit SDK. The application is the solution you build with the framework.

Can the complete solution run without an external connection?

xeokit Data Engine supports deployment in your environment. An offline or air-gapped solution requires an end-to-end review of licensing, authentication, dependencies, updates and integrations. Agree and validate that configuration before treating it as an operational commitment. [2]

Is this a replacement for every APS API or for Revit?

No. This comparison covers processing supplied IFC and Revit files and using the results in a business application. It does not promise APS API compatibility, Autodesk authoring functionality or automatic migration. Creating or modifying source files may still require the relevant authoring tools and rights.

Are all parts of the framework open source?

No. xeokit SDK offers AGPL-3.0 and commercial licensing. Source code for the framework’s application foundations is available as an add-on to a xeokit SDK licence; the agreement defines the delivered code and development rights. xeokit Data Engine and third-party components have separate terms. Read about the framework and licensing.

What would you like to make possible?

Tell us about the business challenge, your users and the systems you already have. We will help define a practical starting point and how to bring the solution to life.

  • The business outcome and the people you want to serve
  • The ready-made capabilities your solution can start with
  • The systems and data you need to connect
  • A practical scope, deployment and delivery plan
Włodzimierz Kurpiński CCO, Creoox AG

A 30-minute discovery call about your project, with no slides.

Book a discovery call ↗

Prefer to write instead? Send us a message.

Sources & comparison scope

Reviewed

Prepared by Creoox AG, the provider of xeoVision, using the official product materials below and the framework scope described on this website. Products and terms can change; confirm the requirements and current terms for your project.

  1. [1]
    Autodesk Platform Services — overview and FAQs ↗

    Cloud services, hosting options, regional availability, pricing and partner ecosystem.

  2. [2]
    xeokit Data Engine — capabilities and deployment ↗

    IFC processing, outputs, own-environment deployment and runtime targets.

  3. [3]
    xeoRVT — processing Revit data ↗

    Direct RVT/RFA processing, outputs and independence from an Autodesk installation or APS.

  4. [4]
    Autodesk Model Derivative API documentation ↗

    Model translation, derivatives and metadata workflows.

  5. [5]
    Autodesk Viewer SDK documentation ↗

    Browser viewing and custom application development.

  6. [6]
    Autodesk — downloading SVF derivatives ↗

    Downloading processed model data for local or offline viewing.

  7. [7]
    Autodesk — expanded regional offerings ↗

    Regional availability of selected APS APIs, including Model Derivative.

  8. [8]
    Autodesk — APS business model evolution ↗

    Free and paid API tiers and usage-based billing.

This comparison is maintained by Creoox AG, the developer of xeokit and the xeoVision framework. Autodesk, Revit and the other Autodesk product names referenced here are trademarks or registered trademarks of Autodesk, Inc. and/or its affiliates. Creoox AG and xeoVision are not affiliated with, sponsored by or endorsed by Autodesk. Product names identify the products discussed. This comparison applies only to the workflows and deployment options expressly described.