On your infrastructure
Deploy application services, processors and storage on the servers your organization operates.
- Keep data and processing in your environment.
- Apply internal network and operating policies.
- Connect to your internal systems.
Plan where your BIM application, IFC and Revit processing, and project data run. We help shape the deployment around your infrastructure and operating requirements.
Application hosting, file conversion and data storage are separate decisions. With the xeoVision framework, selected xeokit Data Engine processors can prepare IFC and Revit RVT/RFA files inside your environment, while xeokit SDK provides visualization in the browser. Agree the complete processing and access boundary for the solution.
Deployment concept. You define identity, network policies, backups, updates and the connections to other systems.
Deploy application services, processors and storage on the servers your organization operates.
Choose a provider and hosting location that fit your requirements, with a dedicated environment and agreed operating responsibilities.
Plan for independent operation by validating every required service and component against the project’s isolation requirements.
Public-sector organizations, defense projects, critical infrastructure and enterprise platforms can shape the environment around their own access, jurisdiction and operational requirements. A restricted-network deployment is evaluated against the specific project; the framework itself is not a security certification.
Yes, with selected xeokit Data Engine components deployed in your environment. xeokit Data Engine supports a Creoox-managed service, dedicated infrastructure, your own servers and a standalone command-line binary. Runtime targets include Windows AMD64 and Linux AMD64 / ARM64. Selected processors can run inside the agreed environment without sending project files to an external conversion service.
Selected processors produce JSON properties and metadata, GLB geometry and XKT models for viewing with xeokit SDK. Define where those outputs and the original files are stored, which application can reach them, and who operates each part. View formats, processors and deployment options.
With agreed application source-code access, you can adapt the interface, extend functionality, choose your development team and manage your roadmap. The agreement defines the source delivery, licences, third-party terms and responsibilities for maintenance. For an asset with a long operating life, plan how your team will retain usable model data and maintain the application as requirements or delivery partners change.
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.
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.