[01]
Building code compliance is too important to live outside the model, and far too costly when errors are made. Kestrel brings it in with one-click code compliance checks.
[ About Kestrel Labs ]
A rule set that runs against your model.
[01]
Building code compliance is too important to live outside the model, and far too costly when errors are made. Kestrel brings it in with one-click code compliance checks.
[02]
Architects still cross-reference PDFs, mark up drawings, and catch expensive problems at plan check, after decisions have already compounded. That's what Kestrel is built to prevent.
[ What We're Building ]
Kestrel translates building code into structured, machine-executable logic. That's what lets compliance run directly in the model, rather than getting resolved in a stack of markups the week before submittal.
Interface
[01]
Kestrel Compliance Analysis runs inside Revit, evaluating your BIM models against jurisdiction-specific requirements, tying every flagged issue directly to the element in your model with a cited code reference.
Kestrel Compliance Chat answers in-the-moment compliance questions specific to your project.
Workflow
[02]
Checks take one click, about 30 seconds. Teams run them continuously during design, not once at the end. The earlier issues surface, the less there is to fix.
Visibility
[03]
Results surface in a project dashboard that gives principals and project managers a real-time view of where the model stands, by discipline and by issue, without waiting on a redline, or opening the model.
Foundation
[04]
Built on official code data through our collaboration with the International Code Council. Always updating, always current.
[ Why Now ]
BIM standardized building geometry. Kestrel is structuring the regulatory layer to match.
[01]
BIM is now the standard substrate of practice, which means compliance can be evaluated against structured geometry instead of static drawings.
[02]
At the same time, advances in AI have made it possible to translate large bodies of regulatory text into executable logic at scale. Kestrel's rule library has grown from dozens of checks to tens of millions in under a year.
[03]
The industry is shifting. In a 2026 survey of the QA/QC landscape, the architectural firm /slantis placed Kestrel in the first tier of model-side compliance tools: "Instead of treating accessibility, fire separation, or zoning review as something that only happens at the end, these tools surface issues while the model is still being developed."
Therefore — what we believe
[ What We Believe ]
Four principles behind Kestrel's compliance engine.
[01]
Compliance happens during design, not after.
[02]
Every requirement ties directly to the element in your model.
[03]
Every issue comes with a cited source.
[04]
The tool handles the tedious work. The architect makes the decisions.
[ Founders ]
Long before Kestrel had a name, Austin Pulford would come home from work talking about the gap between how architects actually design and the tools available for code compliance. A licensed architect, BIM specialist, and architectural technologist, he had spent nearly 20 years delivering large, technically complex commercial and mixed-use projects, coordinating teams and navigating code from early design through construction. Yet code analysis remained largely manual and disconnected from the model as it evolved. He began imagining a system that could make code part of the design process itself.
Marian recognized the foundation of a company in those conversations. Her own career had already placed her at the intersection of the built environment, public process, and emerging technology. She led the $5 million capital campaign for a nationally recognized adaptive-reuse arts center, working across architects, contractors, permitting agencies, state funders, and community stakeholders, and later led operations at an early AI-native company. She knew how to turn an ambitious idea into an organization and move it through institutions that are difficult to change.
Starting Kestrel meant placing both careers and their family behind the same conviction. Austin left the architecture profession he had spent nearly two decades building. When Kestrel was accepted into Techstars Boston, they packed up their young son and moved across the country to go all in.
Kestrel grew from two deeply complementary forms of expertise: Austin's command of architectural practice, BIM, and code, and Marian's ability to build the team, capital, partnerships, and momentum required to transform an industry.
[ Team ]
Creating the shared language between building code and computational design.
The Kestrel Labs team, Denver
[ Recognition & Ecosystem ]
Kestrel is already being recognized, distributed, and backed by some of the most important organizations across AEC.
[01]
Kestrel licenses official building code content from the International Code Council, publisher of the model codes used across most of the United States.
[02]
Kestrel is an Autodesk AECO Technology Partner and is available in the Autodesk Design and Make Marketplace.
[03]
Kestrel was selected as a global top finalist in Trimble's 0–60 Challenge and is now available in the Trimble Marketplace.
[04]
Architosh cited both the attack on the code-review problem and the quality of the 1.0 implementation.
[05]
Kestrel joined Perkins Eastman, SketchUp, and Trimble on The Productive Architect, a panel hosted and covered by Dezeen.
[06]
Techstars, New Stack Ventures, FirstMile Ventures, Denver Ventures, and Avesta Fund.
Building this from Denver, and always glad to meet people who think code should be computable
hello@kestrellabs.com