LocalCode · Municipal Code Intelligence

Find the development rules that apply. Verify every finding.

LocalCode connects municipal development requirements to the exact code provisions, cross-references, and ordinances behind them. Development and planning teams can reach source-backed answers faster—and see clearly when additional site facts, professional judgment, or legal review are still required.

Explore AustinRequest a Demo

A code search gives you a section. A decision requires the complete rule.

Development requirements rarely live in one place. A use table may depend on a definition. A setback may change because of adjacency. A height limit may require a separate measurement rule. An adopted ordinance may not yet appear in the published code.

LocalCode follows those connections so you can see the controlling text, the provisions that affect it, and the official record behind the finding.

EXAMPLE · HOW LOCALCODE RESOLVES THIS RULE · AUSTIN, TXnot a live determination for a specific propertyBUILDING_HEIGHT_MAX
Illustrative resolutionWhat is the maximum building height under Subchapter F § 2.2?
Context required

Maximum building height

Context requiredIs the site within a regulated floodplain? — pick an option to see how this rule resolves.

Controlling provision: § 2.2

Evidence — source-backed

Source text: Austin LDC, Supp. No. 173 · current to 2026-04-23

Controlling provision
§ 2.2BUILDING HEIGHT
Source text — verbatim

Except where these regulations are superseded, the maximum building height for development subject to this Subchapter is: (A) 32 feet for development located outside the 100-year floodplain; and (B) 35 feet for development located in the 100-year floodplain. Section 25-2-531 (Height Limit Exceptions) does not apply to development subject to this Subchapter, except for a chimney, vent, antenna, or energy conservation or production equipment or feature not designed for occupancy. Building height shall be measured under the requirements defined in Section 3.4. Ord. No. 20191114-064, Pt. 1, 11-25-19.

Resolver references
resolver§ 3.4 How building height is measured
Excluded references
excluded§ 25-2-531 Not controlling for this determination
Source text: Austin LDC, Supp. No. 173 · current to 2026-04-23

Illustrative example only — not legal advice and not a property-specific entitlement determination. Full determinations with parcel-level resolution stand behind sign-in.

Live Demo

Try it: ask an AI to read Austin's code — with a receipt

Paste this prompt into ChatGPT, Claude, or Gemini. It fetches a real published section of the Austin Land Development Code and returns the verbatim text plus a provenance receipt — not an unsourced summary.

Paste this in GPT, Gemini or Claude to test
Open this Austin LDC section and quote the verbatim building-height provision text. Include the provenance receipt (source PDF link and source-text-as-of date) from the page: https://www.localcode.ai/codes/tx-austin/25-2/subF/art2/2.2

LocalCode is building the layer that resolves how land-use provisions combine across overlays and compatibility triggers — starting with Austin. This demo shows retrieval + provenance on published source text, not a property-specific determination.

Example for demonstration only. Not legal advice and not a determination for any specific property.

Request early access →

Every Finding Comes With The Record

A Code Viewer Built for Entitlement Decisions

LocalCode connects the code section, controlling text, linked ordinances, source history, and verification actions in one research workspace — so teams can move from reading the rule to trusting the finding.

LocalCode Code Library — code hierarchy, section text, and linked ordinances panel

Controlling Text

Read the exact provision supporting the finding — not a generated summary.

Connected Requirements

Follow definitions, exceptions, overlays, measurement rules, and referenced standards without losing context.

Ordinance History

See the ordinances that adopted, amended, recodified, or affected the section.

Clear Answer Status

Know what is supported by the available record, what requires additional project facts, and what remains unresolved.

Who It's For

Built for the decisions municipal code affects

Different teams need the same thing: a faster way to know which municipal rules control the site, where those rules came from, and whether the finding can be trusted.

Development and Entitlement Teams

Identify the written rules that may affect use, yield, timing, cost, and approval strategy before assumptions become commitments.

For CRE & Developers →

Architects and Engineers

Verify dimensional standards, definitions, exceptions, and measurement requirements before drawings advance.

For Architects & Engineers →

Planning and Development Departments

Connect administered code text to adopting ordinances, amendment history, and source-ready citations for daily staff work.

For Local Government →

Not another unsourced AI answer.

General AI can summarize a section. LocalCode structures the provisions, dependencies, and source documents needed to verify what the code actually says.

See How LocalCode Works

Now Accepting Applications

Austin Feasibility Pilot

LocalCode is opening a focused Austin pilot for entitlement, feasibility, and real estate development teams. Approved users can test structured development regulations, source-backed rule findings, ordinance history, and jurisdiction intelligence for Austin, Texas.