We Built the Platform We Couldn't Find: The Story Behind CERQA

Why BIMstream built its own governed building data platform and what it means for owners and AEC partners who are tired of stitching systems together.

Most software companies build a product, then find customers for it. We did the opposite. CERQA exists because BIMstream needed it first.

For years, our teams were producing some of the most accurate and detailed building data in the industry. Including laser scans, structured BIM models, 360-degree documentation, coordinated as-builts, and then shipping it through three or four disconnected platforms. BIM models went through Autodesk Construction Cloud. Walk-throughs lived in NavVis IVION. Field imagery moved through StructionSite, and later GroundDeploy. Each platform did its piece well. None of them spoke to each other. And none of them treated what we were delivering as a single, coherent body of work.

The result was that our clients, enterprise real estate owners, institutional asset managers, and large AEC firms, were bouncing between systems to access content we'd produced as an integrated dataset. Their architects and operators were paying real time and money to assemble a picture of their own buildings. We were producing infrastructure-grade data and shipping it into a deliverables-grade workflow.

"We were producing infrastructure-grade data and shipping it into a deliverables-grade workflow. CERQA is how we closed that gap."

We looked hard at what the market offered. We found great viewers, solid file managers, capable FM tools. What we didn't find was a platform that could host the full range of work we produce and treat building data as governed infrastructure rather than a collection of project outputs. So we built one. The first customer was BIMstream itself. Every architect, engineer, field specialist, and project team in our organization has used CERQA in their daily work. What we ship to clients has survived contact with our own delivery reality first.

THE FIVE PROBLEMS CERQA SOLVES

What Enterprise Owners and AEC Teams Are Actually Dealing With

CERQA was designed around the problems our clients brought to us repeatedly, across different portfolios, asset classes, and project types. Five of them came up so consistently that they became the architecture of the platform.

• Fragmentation. Building data is scattered across legacy drawings, partial BIM models, consultant packages, BMS panels, work order systems, and shared drives. Most owners can't readily locate half of what they already own, let alone use it. CERQA pulls those sources into one governed platform without forcing anyone to abandon the systems they use today. The search ends.
• Decay. The model delivered at handover was accurate on day one. Without a mechanism to keep it current, it degrades continuously as the building changes. CERQA is built around continuous synchronization and freshness signals, so users always know what they're looking at and how current it is.
• Access. Architects, engineers, contractors, and operators need different views of the same building data, on different devices, with appropriate permissions. CERQA was engineered around granular, role-based access from day one, not bolted on after the fact.
• Secure sharing. The industry default has been to email files or grant full folder access to vendors. That's not how infrastructure should behave. CERQA gives owners precise control over what is shared, with whom, and for how long.
• Integration. A digital twin only earns its keep when it connects to the systems actually running the building: BMS, CMMS, IWMS, GIS. CERQA Connections is the API and SDK layer that enables this, structured through Fabric™ so integrations don't break the underlying data model.

These aren't five separate feature requests. They're five symptoms of the same underlying problem: building data has been treated as a deliverable when it needs to be treated as infrastructure. CERQA is the infrastructure layer.

THE ARCHITECTURE UNDERNEATH

CERQA Fabric™: The Part That Makes It Infrastructure, Not Just a Viewer

Most platforms in this space are sophisticated viewers. They make it easier to look at building data. CERQA is built to govern it. The difference lies in what sits underneath the interface.

CERQA Fabric™ is our patent-pending spatial architecture — the connective tissue underneath every product in the platform. It comprises five components working together: a unified data model so building data speaks one language across systems; synchronization so the twin doesn't decay; a spatial graph that captures relationships, not just geometry; governance rules that determine which source is authoritative when data conflicts; and an extension surface so the platform connects to whatever operational stack a client already runs.

"Every seam between systems, vendors, and project phases is where time and money leak. CERQA is built to close those seams."

Three patents were filed in 2026 to protect the Fabric™ architecture, with more in progress. But the competitive significance isn't just in what's patented. It's in the vertical integration. BIMstream controls the full pipeline from reality capture through processing, modeling, platform, and continuous updates. No other company in the built environment owns all those layers. The seams between vendors are exactly where digital twin initiatives fail. We removed the seams.

WHO CERQA IS BUILT FOR

Three Audiences. One Platform. The Same Fabric™ Underneath.

CERQA serves three distinct audiences, each with different needs, all operating on the same governed infrastructure layer.

BIMstream delivery teams use CERQA as our production and delivery environment. Studio modelers, field teams, project managers, and QA all work in the same system, against the same data, with the same standards. What this means in practice: new team members get up to speed in weeks rather than quarters, project handoffs become structured publications rather than folder dumps, and every deliverable we produce meets the same standard because it flows through the same pipeline.

AEC firms use CERQA as a project delivery and collaboration platform. They get a structured way to model, share, and hand over building data without losing fidelity at each transition. Owner clients can see work in progress in real time and accept handover into a system that doesn't immediately start decaying. For an industry that has historically lost significant value at every project phase boundary, this is a structural change.

Owners and operators use CERQA as long-term portfolio infrastructure. Not just a system of record, but a system of engagement, that is a governed environment where the operational stack, AI capabilities, and stakeholder workflows connect to the spatial backbone of their assets. The platform isn't only where building data lives. It's where the work happens.

"Different tiers for different needs. Same Fabric™ underneath."

HOW THE PLATFORM EVOLVES

Built by Practitioners. Shaped by the People Doing the Work.

The single most important thing about how CERQA is built is who builds it. Our entire software development team sits inside BIMstream, alongside the architects, engineers, and field specialists who use the platform daily. When a Studio modeler hits a friction point, the engineering team hears about it the same day. That feedback loop, between the people building the software and the people whose work depends on it, is the most underrated competitive advantage we have.

The platform roadmap is shaped by three inputs: our own delivery teams' daily experience, our enterprise clients' operational needs, and the patterns we see across portfolio-scale deployments. The Vision and Field capabilities came directly from client feedback on earlier releases. Most of the major features in CERQA originated with a real operational problem we'd observed on more than one project, not from a feature wishlist or a competitive benchmark.

"If it's not good enough for our own teams to use eight hours a day, it's not good enough to ship."

This discipline matters because building software for buildings is genuinely hard. Buildings don't behave like other enterprise data environments. They're physical, they change constantly, they involve dozens of overlapping systems and stakeholders, and the consequences of bad data are measured in project costs and capital decisions, not just user experience. Software built by people who don't do the work tends to optimize for the demo, not the Tuesday morning field condition. CERQA is built the other way around.

THE NAME

Why the Platform Is Called CERQA and How It Got Named

The name has Latin roots tied to the idea of seeking and finding. We wanted something that phonetically echoes the word 'search,' because so much of what the platform does is help people find their buildings, the right view, the right drawing, the right asset, the right version. CERQA is spelled as a distinct brand, but the meaning underneath is intentional.

What I'm most proud of, though, is how the name was chosen. We didn't hire a branding agency. We ran a company-wide competition among our architects, engineers, Studio teams, field staff, offices across every geography where BIMstream operates. Every part of the organization weighed in. The name came from the people who actually do the work.

That matters beyond the story. CERQA is a platform built by the team that uses it, and named by the team that uses it. The Latin root tells you what the platform is for. The way the name was chosen tells you who it's for.

GETTING STARTED

Two Paths In. One Infrastructure Layer Either Way.

There are two ways to start working with CERQA, depending on where an organization is and how much internal capacity they want to build.

The first is full-service. BIMstream captures the building, processes the data through CERQA Core, models the digital twin through our Studio teams, and hosts everything in the platform. Owners and AEC firms get a fully governed twin with no internal lift required. Studio/X extends this model for enterprise clients at portfolio scale, embedding dedicated BIMstream production teams alongside the client organization so the maintenance loop, the mechanism that keeps the twin current, has dedicated ownership.

The second is direct. A client stands up a CERQA workspace, uploads their existing data, configures their integrations, and operates the platform independently. CERQA is deliberately designed to function without BIMstreamservices attached. If an organization already has BIM models, scan data, drawings, and documentation, CERQA gives them the platform to host, govern, and build on top of that existing investment.

Most clients end up operating somewhere between the two, starting in one mode and adjusting as their portfolio grows or their internal capabilities develop. The platform is the same either way. The work flows through the same Fabric™. That's the whole point: one infrastructure layer that scales with how each client wants to operate it.

THE SHIFT THAT CHANGES EVERYTHING

From Deliverable to Infrastructure: The Moment It Clicks

The owners and AEC leaders who have gotten the most from CERQA share a common inflection point. It's the moment they stop thinking about building data as something that gets delivered at the end of a project and start thinking about it as infrastructure they operate continuously. The platform feels different once that shift happens, not because anything in the software changes, but because the organization starts using it the way it was designed to be used.

Building data that is governed, current, and connected to operational systems is leverage on every dollar an organization spends on its portfolio. Every renovation that starts from accurate data instead of a field investigation. Every capital decision grounded in reality rather than three-year-old drawings. Every new team member who reaches competence in weeks instead of years. Every AI initiative that has something real to learn from.

CERQA is how BIMstream delivers that. It's the platform we needed and couldn't find. We built it because the work demanded it. We're making it available because the industry does too.