AI photometric engine · parking and roadway lighting

Parking lot lighting, laid out in about a minute.

Give it the site, a luminaire and your criteria. It searches thousands of pole layouts and returns one that passes, with every input on record so you can check it in AGi32.

reading the siteReal engine run on a synthetic 300 × 200 ft lot
Within 3.6 % of AGi32 and DIALuxroadway area averages, 9 zones from real projects
Within 0.5 % on 271 pointsparking lot: min, average and max vs an AGi32 direct-light run
25 of 25 acceptance tests passreal parking project, last run 2026-10-08
first customer · commercial LED manufacturer, California
parking engine · early access · runs on request

Watch it search

Runnax is an AI photometric engine for roadway and parking lighting. Give it a site, a luminaire and your criteria; it returns a pole layout that passes, with every input on record so you can check it in AGi32.

Verified vs AGi32 · one-minute layouts · every input on record

Watch it lay out a 300 × 200 ft lot. Poles may only go on the islands and curbs (teal).

0layouts tried
0rejected
1poles
searching…
0 / 0
run of 2026-10-14·
—
—poles
—heads · — ft
—avg fc
—min fc · max:min —

What it does today

Live

Parking lots

  • Lot boundary, drive aisle and pole areas in; pole positions, heights and head count out
  • Searches regular arrays, up to 16 poles and 3 rows, within your pole-height range
  • Checks minimum and uniformity on a 10 ft grid, plus vertical illuminance at 5 ft on both sides of the aisle
  • Picks the best luminaire from your IES catalog; stops and says why when nothing passes
Calculation

Roadways

  • Single-side arrangement validated against AGi32 and DIALux on real projects
  • Opposite and median arrangements calculate; check their numbers in AGi32 or DIALux for now
  • Roadway and sidewalk grids, each with its own statistics; BUG rating from the IES file
  • Area averages are validated; point values and minimums are not yet, so no roadway pass/fail
Upcoming

Everything else outdoors

  • Site and area lighting with free pole placement
  • Gas-station canopies
  • Sports fields and floodlighting
  • Property-line light trespass · parking structures

Each ships when it passes the same AGi32 comparison the parking engine did.

Your catalog, its choice

Hand it every IES file you would quote. It runs the full search for each one and keeps the luminaire that passes with the fewest poles.

Only where a pole can stand

You mark the islands and curbs, or confirm areas picked from your DXF. Any layout with a pole outside them is thrown out: 18,721 of 24,904 in this run.

Files you can check

Pole table, point-by-point grid, isolux sheet and a summary with every input. Put the pole table on your sheet. Every input is in the summary, so you can rebuild the run in AGi32 for a second opinion.

Callable from your tools and agents

One contract behind a REST API, an MCP server and a CLI, so an AI assistant gets the same numbers an engineer does. Early access runs through us today.

Move the poles yourself

Same lot, same luminaire table the engine used, same point method, running in your browser. Drag a pole along the islands, change the height, watch the grid. This is a preview; the engine's run above is the record.

drag a pole along the islands · double-click to add · right-click to remove
—
—avg fc
—min fc
—max : min
—poles

Luminaire: the one the engine picked for this lot, measured IES. Grid 10 ft, direct light only, same point method as the engine.

What one run looks like

24,904layouts tried for this lot
18,721thrown out for a pole off the islands
64 ssearch, start to finish
1kept: the fewest poles that pass
hover a point: engine vs AGi32

Engine grid, 271 points at 20 ft, 15 heads. Against an AGi32 direct-light run of the same lot, min, average and max agree within 0.5 %.

Real project: a municipal sports-complex parking lot, South Dakota

Customer asked
Eavg ≥ 1.0 fc · Avg:Min ≤ 3.3
Fixture
75 W · 13,000 lm · 25 ft
Delivered design (AGi32)
1.2159 fc · 3.1998 · PASS
Engine, same lot
1.2367 fc · 3.1312 · PASS

The engine reads 1.7 % higher on average than the delivered design; the tighter of the two leaves 3.04 % headroom on uniformity. Direct light only; not an RP-8 compliance statement; headroom is specific to this lot.

Open the case →

Why not the free layout tool?

Manufacturer free-layout serviceRunnax
Turnaround1–3 business days, by a person in AGi32about a minute
Same 300 × 200 ft lot24 × 150 W, no pole positions, 50 % over target8 × 166 W, 8 poles on the islands, on target
Can you check it?No inputs providedEvery input on record; checked against AGi32 on a real parking project

Left: public free-layout tools of two US LED manufacturers, tested 2026-10-08. Their tool optimises average illuminance, ours minimum, so this compares capability, not scores.

How to get it

Early access

Engineers and contractors with a real site
  • We run your site on the engine
  • Four files back within one business day
  • You tell us where it's wrong
Free during early access

Engine API

Software teams and AI agents
  • REST endpoint, one contract
  • MCP server and CLI on the same contract
  • Run record on every call
Usage-based · pricing with the API release

White-label

LED manufacturers
  • Your IES catalog, your brand
  • Instant layouts on your product pages
  • Auvolar is the first customer
Per manufacturer · talk to us

What you need to know

What do you need from me?

The site (a DXF, an AGI file, or the lot dimensions and drive aisle), the luminaires you would quote as IES files, your targets (minimum illuminance and max:min uniformity), a pole-height range, and where poles may stand: the islands and curbs.

How close is it to AGi32?

Parking: on a real lot, the engine's minimum, average and maximum are within 0.5 % of an AGi32 direct-light run of the same lot over 271 points; against the AGi32 design delivered to that customer, its average reads 1.7 % higher. Roadway: area averages are within 3.6 % of AGi32 and DIALux on 9 zones from real projects. Roadway point values and minimums differ more, so we don't quote them on their own.

Does it certify RP-8 compliance?

No. It checks the targets you set, using direct light only. A run is not an RP-8 compliance statement and not a construction approval; the engineer of record still signs the design.

Where can it put poles?

Only inside the areas you mark as allowed, such as islands and curbs. It searches regular arrays of up to 16 poles in up to 3 rows. Any layout with a pole outside the allowed areas is rejected.

What can't it do yet?

Parking: curved or polyline aisles, mixed mounting heights in one lot, several parking zones in one run, obstructions and shadowing, and aiming optimisation (single-head fixtures keep one fixed orientation for now). Roadway: staggered arrangements, three or more roadway lanes in one section, luminance-based criteria, and pass/fail verdicts. Nothing is field-verified against measured light levels yet; all results are simulations.

Do you train on my files?

No. Files are used for your run, deleted after 30 days, and never used for training.

Can my AI assistant call it?

The engine has one contract behind a REST API, an MCP server and a CLI, all shipping with the API release. Until then, early-access runs go through us.

Who is behind Runnax?

Runnax is a photometric engine company founded by Kyan Gao. Auvolar, a commercial LED manufacturer in California, is its first customer.

Request a run on your lot

Tell us about the lot. We reply within one business day and ask for the DXF, AGI file or dimensions by email. Files are deleted after 30 days and never used for training.

Or talk to an engineer

If you'd rather describe the project first, or you're evaluating the API or a white-label deployment, write to the founder directly.

kyan@runnax.com

Replies within one business day, US Pacific.