THE ONTARIO BUILDING CODE, CHECKED AGAINST YOUR SHEETS.

What actually gets checked

Roughly 105 checks against a full drawing set, grouped the way a reviewer thinks about them: building height and storey count, site and setbacks, accessible design, life safety, fire separations, egress and exit widths, ventilation and guards.

Every result is a pass, a warning or a failure with the clause printed beside it — OBC division and article — and the sheet the drawing evidence came from. A finding you cannot trace to a clause is a finding you cannot take to a consultant, so nothing is reported without one.

Where the drawings actually go

Said plainly, because it matters on institutional and government work: the drawing set is uploaded to Marapone-operated infrastructure in Canada or the EU to be read. There is one sub-processor to declare, and it is us. What is not in the path is a third-party AI vendor — the reading is done by our own model, in a workspace scoped to your account, and nothing of yours is used for training. If your contract bars putting tender drawings on a third-party service at all, a plan cannot satisfy that clause, and an enterprise deployment into your own cloud tenant is the only arrangement that can.

The code changes; the file does

Statutory figures, fee schedules and rate tables live in editable JSON rather than compiled into the application. When a number changes it is a data edit, not a release — which is why an amended figure reaches you the same week rather than in the next version you would have had to buy. The data packs are also sold on their own as files, and those you do keep outright.

Built where the code applies

The rate tables, development charges and permit figures that ship with the Ontario data pack are Toronto-area figures with their source and date recorded beside them. Other provinces, US states and European countries are supported by swapping the data pack rather than by rewriting the engine.