What is coming, and in what order
Taken straight from the roadmap we actually work to. There are no dates on this page, because we do not have dates we would be willing to be held to. Items move onto the rest of this site only when they are done and the feature list says so.
NowIn build
Deployment, and the first service
The panel mesher, form-finding with forces and patterning move to the server; the browser keeps a draft mesher so the app still works on a plane. Every response carries its engine version, and the drawing records it.
Solver and mesher performance
Profile first, then a sparse direct solver, a proper flattener and warm starts. Target: this canopy meshed, solved and developed in under a second.
NextRuled and ready
Named views, narrative, decks and brochures
One publish pipeline, three templates — deck, brochure, website — emitting one self-contained file that is a screen deck and, through print CSS, a vector PDF.
Spaces and the space schedule
A space is a closed outline on a level with a use and a name. Area and volume are derived; unit mix and area per level fall out.
Lights, and direct illuminance
Photometry from IES files, with a parametric fallback. Direct illuminance is first-principles and exact, and labelled direct; interreflection comes later.
The command log
The model as a tree of commands, so a drawing can be replayed, branched and compared — with the reason for an edit recorded beside it.
LaterRuled, not yet scheduled
Ground from a DEM, refined by survey
One spatial frame the model actually stands in: levels, camera walk and footings on real terrain.
Walls and openings
A wall as a role on a line, openings hosted on it, cutting its solid, with leaf, frame and glazing from one catalogue.
Codes as data, and computed checks
A project’s jurisdiction resolves its governing codes; each check is data with a published worked example, and every check returns the governing constraint.
Roads, and services networks
Alignment and profile taken from the ground; services as nodes and edges hosted on the roads.
Forces verified against RFEM
Our numbers and the exact inputs to reproduce them are published. The independent run has not happened yet, and the comparison columns say so.
How we work
Two rules govern what this site says. The first: available and coming are visibly different, everywhere, and a claim only becomes available once the thing is finished and the feature list says so.
The second is the asymmetry — the site describes less than the product does. Benchmarks quoted here are the measured floor and not the best run; capacities are what was proven, not what was hoped. If something surprises you on first use, we would rather it surprised you upward.
A feature that has shipped and is missing from this site is a defect of the site, not a marketing decision.
Want something on this list sooner?
The order changes when someone with a real job in front of them explains why. Tell us what you are trying to do.