Building BIM software is largely about making smart use of open standards instead of seeking out vendor lock-in. Our order of preference is clear: open formats wherever possible, vendor APIs where necessary, and parsing native file formats only as a last resort.
Open standards we support by default: IFC (Industry Foundation Classes) for geometry and metadata, BCF (BIM Collaboration Format) for exchanging issues with the modellers, and COBie (Construction Operations Building Information Exchange) for handover to facility management. For those who want to work with open BIM data without an Autodesk stack, we also use Speckle as a data layer.
Vendor platforms we integrate with: Autodesk Platform Services (APS, formerly Forge) for rendering Revit models in the browser and server-side processing, the Tekla Open API for steel engineering, Bentley iModel.js for infrastructure, and the Bricsys API where relevant. For 3D viewers in the browser, we choose between xeokit (open source, performant for large IFC files), Three.js (complete freedom, more custom work) and the APS viewer (the fastest route if you already have an Autodesk stack).
Existing SaaS we explicitly do not replace: Autodesk Construction Cloud / BIM 360, Trimble Connect, RIB iTWO, Bentley ProjectWise, Bricsys 24/7 and Solibri. For large multidisciplinary projects, those packages work well and are expensive to replicate. We build the add-ons, integrations or sector-specific workflows that such a suite doesn't offer out of the box.