The Rhino model stays on the machine that drew it, where sun studies run for free. Files and agreed facts are kept in your organization’s private area on Wrengler, under its roles. You direct the work: ask the project a question, and the assistant, in Pro preview, answers with its sources.
In preview, for architecture and engineering practices, in Rhino 8.
A practice's work lives in several places: the model on a desk, files and agreed facts with the project, rules with the organization. Wrengler keeps each one in its place and lets work pass between them as requests and results.
Run a sun study on the model you are drawing. It runs on your own machine, and the model stays there.
Compute · Sunlight
Keep briefs, reports and drawings with the project, in your organization's private area on Wrengler, under its roles.
Projects · files
Editors propose a fact, a lead approves it, and each project picks the agreed facts that apply to it.
Knowledge · the workspace
Set a goal, such as which studies contradict the design statement, and come back to an answer that cites every study, file and conversation it read.
Goals
Your organization's file rules check names, duplicates and stale files, and a person applies each proposed fix.
Always on · housekeeping
Sunlight: Available, free. View, Radiation, the assistant, goals and images: Pro preview.
In a federated model, each discipline keeps its own file and coordination happens where they meet. Wrengler treats the rest of a practice's work the same way: each part is kept in its place, work starts from a person, and whatever comes back can be traced to its source.
The model stays in Rhino on the machine that drew it, and studies run there. Files, conversations and agreed facts are kept in your organization's private area on the Wrengler platform, under its roles. Between them travel requests and their results: a measured area, a rule, a finding. Never the geometry.
A question, a goal or an approval starts the work, and nothing destructive runs without a person. The answer quotes numbers as the project stores them and links each one to the study, file or conversation it came from.
Studies are the part of the workspace that runs beside the model, in Rhino on your own machine. Check hours of direct sun on courtyards, streets and facades. See how much of a landmark can be seen from each point. Compare the solar power reaching a roof or a facade. Results appear as a heatmap on your Rhino model, and Sunlight follows the massing as you change it.
Sunlight follows the sun across the day you choose and counts the hours of direct sun each point receives, so a courtyard, a street or a facade reads at a glance. Move the pointer over the sky, or drag the sun, to run the day again.
Sunlight, view and radiation share one ray-tracing engine. Its reference is checked against closed-form physics, and every faster path is checked against the reference. Faster hardware gives you the answer sooner, not a different answer.
Ask the assistant to select the south-facing facades and measure their area, and it does it in Rhino with the panel's own tools. It never writes code, and anything that deletes waits for your approval. In Pro preview.
Sunlight: Available, free. View and Radiation: Pro preview. Daylight: Planned. Every study can run on the CPU; the GPU path is Available on Apple Silicon, In progress for NVIDIA and Planned for cloud GPUs. Nothing here is an EN 17037 certification claim.
Some questions take more than a reply, such as which of our studies contradict the design statement? Set a goal in the project chat, in your own words. Wrengler works through the project’s studies, documents and conversations and posts an answer with its sources in the same thread. Close the chat; the work carries on.
A goal is split into parts that run side by side, each reading only what it needs. If it is interrupted, the finished parts are kept and only the part in progress starts again.
A goal only reads, with your access, within fixed limits on time and reading. Every number in its answer is checked against the project's recorded facts, and anything it cannot confirm is listed for you to check.
Goals: Pro preview.
A study, a goal or a question can end in what the moment needs: a table in the chat, a report written from a study's results, or an image for a competition board. Each one records how it was made.
Diagrams, sketches, interiors, landscapes, photomontage and more, from a description or the Rhino view. Every image is labeled as imagined, never as a study result, and records how it was made.
Reports are written from a study's results and are marked outdated when the study runs again. Answers quote the saved number itself, so they stay right while a report catches up.
The assistant, goals and images: Pro preview.
Your organization's file rules run on a schedule: names that drift from the convention, duplicates, stale files, reports that fell behind their study, a file in the wrong project. Each finding comes with a proposed fix and goes to the people who can act on it. Nothing changes until one of them applies it, and every applied fix is recorded.
Plain checks run first. Where judgment is needed, such as what kind of document a file is, AI proposes the answer. Findings go to owners, admins and the workspace's lead with the fix ready to apply, and most fixes can be undone.
The project conversation is the same in the Rhino panel and on the web, and a goal's answer lands in it. Findings, invites and proposals appear in the notification center, and the audit log keeps the record.
An organization holds your people, their roles and its rules. Workspaces group the work, for a team or a client, and joining the organization does not open them. Access is checked on every request.
Owners, admins, members and viewers in the organization; leads, editors and viewers in each workspace. Joining the organization opens nothing by itself.
Owners and admins invite colleagues to the organization with a role. An invitation adds the role and opens nothing else.
Editors propose, leads approve. Approved facts are frozen, projects pick the ones that apply, and the assistant quotes them as agreed, not as a guess.
Changes to membership, roles, workspaces, projects, knowledge and applied fixes are written to an audit log automatically. Admins can read it; nobody can edit it.
Usage limits that follow your plan, the assistant on or off for the whole organization, and how long the audit log is kept.
Access is checked on every request, not by the panel. A copied Rhino file or a modified plug-in opens nothing, and a linked file never carries the project's name or its files.
Wrengler is in preview for Rhino 8 on Windows and macOS. Tell us about a live project and the question it has to answer, and we will reply about a pilot. Your model stays on your machine, and the project stays under your organization’s roles.