Laydyne

For venue and event teams

You lay out the same hall for each client, seated one week and a standing reception the next, revise the plan after their comments and send it again with the seat and equipment counts, and sometimes need to know whether registration will queue at the doors.

What Laydyne does for it

Open a recorded example

What the published records produced

The fictional 30 × 20 m hall has four columns and a stage. Separate layouts hold 344 chairs or 14 standing tables and six booths. The handover contains the layouts, quantities, inventory and editable project. In the separate registration study, five options use the same arrival wave and seeds 7 to 9. Six staffed counters give a mean counter wait of 1m 10s. With 85% pre-registration and eight kiosks, the mean wait per visitor is 11s. These are simulation results for those inputs, not venue capacity or service guarantees.

These recorded projects use synthetic inputs. Photos and drawings show what was produced; site accuracy, business effects and photorealistic reconstruction are not established.

What it does not do

  • Guests do not choose seats or paths in this example, and nothing here checks occupancy limits, sight lines, sound, exit capacity or fire and accessibility rules. The reception queue is a count-and-capacity calculation, not crowd physics. Laydyne does not manage guest lists or table assignments. Table numbering, seat assignment and shared links are not part of this example; what Laydyne produces here is the plan, its revisions and the proposal packet.
  • This is a count-and-capacity simulation, not crowd physics, egress analysis, occupancy certification or a fire-safety check. Visitors do not collide, switch lines or give up, and waiting visitors do not take up physical queue length. The keynote has no seat limit in this example.
  • A seating row or a bench is one part, not its capacity, so the seat figure is a part count, not a headcount; the model records no room type, so meeting rooms and offices are not told apart in the table.

Price

Building and editing the model with your own AI over MCP, route checks, saving in this browser and JSON import and export are free, with no count limit; a free account is needed only to create an MCP link (3 per account). Running simulations, the built-in AI and cloud saving need Pro ($29 a month or $278.40 a year) or Max ($89 a month or $854.40 a year). Prices are in US dollars before tax; your AI provider bills its own usage separately.

What is free, and what Pro and Max add

Common questions

Can I keep a seated and a standing plan of the same hall?
Build the hall once with its fixed columns, exits and stage locked, as a 2D plan and a 3D model, and save a seated plan and a standing plan as independent layouts.
What does the client receive?
Export one proposal packet with the drawings, counts, changes and assumptions that prints to PDF, and scaled 2D drawings with an area table.
Does it check occupancy limits or exit capacity?
Guests do not choose seats or paths in this example, and nothing here checks occupancy limits, sight lines, sound, exit capacity or fire and accessibility rules. The reception queue is a count-and-capacity calculation, not crowd physics. Laydyne does not manage guest lists or table assignments. Table numbering, seat assignment and shared links are not part of this example; what Laydyne produces here is the plan, its revisions and the proposal packet.
What does it cost, and what is free?
Building and editing the model with your own AI over MCP, route checks, saving in this browser and JSON import and export are free, with no count limit; a free account is needed only to create an MCP link (3 per account). Running simulations, the built-in AI and cloud saving need Pro ($29 a month or $278.40 a year) or Max ($89 a month or $854.40 a year). Prices are in US dollars before tax; your AI provider bills its own usage separately.