Building a 3D configurator for stairs and balconies: geometry, data, mobile and privacy
Technical choices for stair and balcony configurators: parametric geometry or CAD, tables as data, units, languages, mobile, accessibility and privacy.
Short answer: stairs and balconies change shape with every input. So a configurator for them generates the variable parts, such as the helix, treads, landing, platform and railing runs, in the browser from parameters, and uses fixed models only for parts that never change, such as brackets or handrail sections. Riser tables and size limits belong in data files, not in code. Add units and languages per market, controls that work on a phone, and a clear label on every check saying it is guidance, not approval.
This guide is for technical marketing, product management and IT at manufacturers of stairs, railings and balconies. It draws on the two example configurators in this group, the spiral stair configurator and the bolt-on balcony configurator. Both are example configurators with fictional products and example values.
Parametric geometry or a CAD model?
For many products, it is enough to show an existing model and swap colours or options. That does not work here. A spiral stair with a different floor height has a different number of treads, a different rotation and a different landing. A balcony with a different depth has a different platform, different railing lengths and a different shadow. One model per variant would be unmaintainable.
| Part | Approach | Why |
|---|---|---|
| Helix, treads, landing, balusters | generated from parameters in the browser | shape depends on height, diameter and step angle |
| Platform, railing panels, privacy screens | generated from parameters | width and depth are free inputs |
| Brackets, connectors, handrail sections, fittings | fixed model from drawings or CAD | shape is fixed and the detail matters |
| Context: floor slab, opening, facade | simple, from parameters | context, not product |
In both demos, all geometry is generated in code, with no third-party models. For a real range we recommend a mix: variable parts parametric, the characteristic details from your data. Fixed parts suit glTF, a royalty-free specification for the efficient transmission and loading of 3D scenes [1]. How STEP and other CAD data become a light web model, and what is lost on the way, is covered in from CAD to a web 3D configurator.
Generic geometry or yours?
Our demos show generic types: a spiral stair of a common kind, balcony types common in the trade. For your configurator we model your product with your sections, connections and details. That is where a buyer tells your product from a competitor's, and it is where most of the modelling effort goes.
Where do tables and limits live?
In data files. In the stair example, riser tables, diameter lists, product lines and guide values sit in their own file, separate from the logic. In the balcony example, the same goes for facade dimensions, limits per type, railing heights, colours and every label in both languages. Three things follow:
- A new riser table or a changed size range is a data change, not a programming job.
- Every number can be traced to a source: your table, your sign-off.
- Acceptance test cases can be derived straight from the tables.
For stairs and balconies the second point matters most. Every limit the configurator checks needs your sign-off as the manufacturer. Whether a value meets a standard or regulation is the responsibility of the manufacturer and the structural engineer; we implement what you approve. The model-level detail is in spiral staircase configurator rules and balcony configurator logic for facades.
Units and languages
- Units: the stair demo calculates in one internal unit and shows inputs and results in either feet and inches or millimetres. The balcony demo works in metres and accepts a decimal comma in the German version.
- Languages: the balcony demo runs in English and German, including the enquiry text and the PDF. The stair demo is English only. In a project we set up the languages you need.
Both choices reach beyond the interface into the enquiry: your sales team should receive it in the units and language it works in.
Phones and loading
When an enquiry starts on a phone, for stairs and balconies that means dimension inputs that work with a thumb, and a 3D view that does not get in the way of scrolling. On the library pages, the 3D view starts only when the visitor opens it. Both demos also handle the case where the device pauses the 3D view, for example when graphics memory runs short: they say so and rebuild the view, and the configuration is kept.
The balcony demo has an independent test record: across seven emulated screen sizes from a small phone to a desktop, the full user journey completed at every size, with no control smaller than 44 pixels. The test used emulated devices, not real phones.
Accessibility
A 3D view on its own is hard for many people to use. The balcony demo shows one way round it: next to the 3D model there is a facade grid in which every cell is a button with a text label, such as "Storey 3, axis 2: Bolt-on, cantilevered". All values also appear as text in the review. Accessibility requirements for e-commerce differ by market; for the German and EU context, our German guide on accessibility in 3D configurators covers the details.
Privacy
A stair or balcony configurator collects project data: dimensions, a location, often a company. Settle three questions early:
- Where are the text and PDF created? In the balcony demo, only in the browser; entries are neither sent nor stored.
- What is measured? In the balcony demo, only which features were used, never what people type.
- Which third parties load? In the balcony demo, fonts and libraries are self-hosted; the independent test recorded no requests to other servers.
How is a stair or balcony configurator accepted?
With test cases that come from your tables, not from our intuition. For these products we recommend four kinds:
- Table boundaries: every height exactly at a boundary of the riser table, every diameter at the edge of its range, every balcony depth at the limit of its type.
- Rules: every condition once met and once not, with the expected message.
- Geometry against calculation: do the dimensions in the 3D model match the values in the summary, such as tread count, rotation or platform area?
- Enquiry against summary: does every summary row appear unchanged in the text and the PDF?
You get the results before the configurator goes live, and you test on your own devices through a private link. The technical correctness of the approved values remains your responsibility as the manufacturer; we check that the configurator applies them correctly.
Maintenance and labelling
A configurator for safety-relevant products needs one rule that outlasts the launch: every check is labelled as guidance, not approval. Both demos do that at each check and in the PDF. When your tables change, the data file changes and the test cases run again. Hosting and care can be part of the order; what scope goes with which price is in what a stair or balcony configurator costs. For how we work overall, see custom 3D configurator development.
Common questions
Does a stair or balcony configurator need WebGPU?
No. Both demos run on WebGL using the three.js library. The geometry of these products is modest; what matters for performance is redrawing only when something changes.
Do we have to supply CAD data?
No. Size tables and drawings are enough for the parametric parts. CAD helps for fixed parts such as brackets or handrails; we check whether it suits the web before we start.
Sources
- Khronos Group: glTF (read 14 November 2026): khronos.org/gltf
- Demo features: library pages and the demos (read 14 November 2026): spiral stair, bolt-on balcony
- Balcony demo test: independent check of 14 November 2026 (internal record, emulated devices)


