About Mathyra
The intelligence layer
between drawings
and models.
Mathyra is an AI-powered civil engineering drawing intelligence platform. It takes 2D plan sets — the contract documents civil projects actually run on — and turns the information inside them into structured, machine-readable engineering data.
Not another PDF reader.
Plenty of software extracts something from a drawing — text, lines, quantities. Mathyra is built around a different question: what does the plan set actually say?A cross-section is not a picture; it states elevations against a datum, offsets against an alignment, at a station on a roadway. Those relationships are the engineering — and they are exactly what flattening a design into PDF destroys. Mathyra reads geometry, text, structure, relationships, and context together, and reconstructs the drawing as data a machine can compute on and a human can audit.
The long-term direction runs from 2D documentation all the way to spatial engineering workflows: drawings → understanding → validation → machine-readable models → eventually 3D. Each step ships only when the step beneath it can be trusted.
What we believe about engineering data.
REFUSAL OVER GUESSING
When the ink is ambiguous — a label that could be two things, a datum that cannot be corroborated, two readings that disagree — Mathyra flags it for review instead of silently picking one. A refusal is a result; a guess is a defect.
EVERY VALUE HAS A SOURCE
Each extracted coordinate carries a trace to the sheet, the location, and the drawn objects that produced it. A value that cannot cite its source does not ship.
DETERMINISM WHERE IT COUNTS
Geometry and calibration are computed, not sampled: the same plan set produces the same model, byte for byte. AI is reserved for what genuinely needs perception.
THE DRAWING IS THE AUTHORITY
Scales come from the sheet’s own rulers, datums from its own gridlines, names from its own captions. Mathyra reads what the drafter stated — it does not assume conventions the document never declared.
Where Mathyra stands, honestly.
Every claim on this site carries one of three labels, and this is the full accounting. Nothing here is inflated: what is built is built, what is coming is coming, and the difference is stated.
Working today — in private development
- Geometry extraction from vector plan sets, calibrated by each sheet’s own rulers and scale statements
- Stationed cross-sections exported as structured, machine-readable engineering data
- Per-value provenance: every coordinate traceable to its sheet and band
- The refusal system: ambiguity flagged in a registered vocabulary, never silently resolved
- Deterministic re-runs and revision-aware comparison of plan set versions
In development
- Cross-sheet reconciliation: the same station checked across plan, profile, and section
- Alignment attribution: every value tied to the roadway whose stationing it belongs to
- Survey-control reading: coordinate systems and datums resolved from the sheets that state them
The vision
- Surfaces and corridors assembled only from validated geometry — a 3D model whose every vertex can cite its sheet
- Exports into the CAD, GIS, and machine-control tools the industry already runs on
- Downstream workflows — takeoff, QA, as-built comparison — running on evidence instead of re-keyed data
Built with the industry, not at it.
Mathyra is in private development against real DOT plan sets. Early access will be shaped by the engineers, surveyors, estimators, and contractors on the list — the people who know what a wrong elevation costs.