Standing
The project
It lives in the system rather than in a file, from the brief to the build. Ask it anything, any time — it answers with evidence, not opinions.
Preview · First door: Rhino 8
Direct the work, don’t drive the tools.
Wrengler is a design substrate for the built world. Sandboxes assemble compute, services and AI imagery to answer one question at a time — built so agents can operate every layer. Hands-on control is right there too, on the same rails — for one designer or a whole practice.
- First door
- Rhino 8 · Windows & macOS
- Studies
- Sunlight, view, radiation
- Compute
- On your own machine
- Teams
- Roles, workspaces, audit
The system
Services on one side. Sandboxes on the other.
Expertise lives in services. A sandbox is spun up per question, wired to exactly what it needs, and discarded when the answer lands — with its evidence attached.
Services · growing
- learn platform
- integration tools
- data model
- subject-matter experts
- image router
- consultancy platform
Sandbox
per question
“Where does the courtyard get sun in March?”
- compute
- harness
- sockets
- image pipelines 2d · 3d
spun upanswereddiscarded
Answer · checkable
courtyard · 21 marsunlight hours
- evidence attached
- provenance stamped
- sandbox dissolved
- One contract
- every door calls the same typed commands
- Composable
- a sandbox wires up only what the question needs
- Open
- services can come from anywhere
- Local
- compute stays on your machine
Sandboxes
A sandbox is a project — or a mission.
Disposable
The mission
One specific case, one sandbox. It assembles the services, spends the compute, generates the imagery, returns a checkable answer — then dissolves.
Projects
The project outlives the file.
Every Rhino file you link joins a project that holds everything else the work needs — and you can ask it questions.
Link
Your Rhino file knows its project
Pick or create a project from the panel. The file remembers it — through renames, moves and Save As — and opens already linked.
Gather
One place for the work
Rhino files, drawings and specs, the facts you tag it with, the studies run against it. The same project in Rhino and on the web.
Ask
A chat that answers from the data
Ask the project from Rhino or the browser. Point a question at the project's data or the open scene; numbers are quoted from the data, never guessed.
- Project data — tags, files, studies
- Rhino scene — the file you have open
- Image — generate from the view
Private by default. A copied file carries its link, never its access: only you and the people you add can open a project, and the assistant sees a summary of your scene, not your geometry.
Teams
Your practice, with its boundaries intact.
An organization holds your people and its rules. Workspaces hold the work, and only the people added to them. Projects draw on knowledge the team has already agreed.
Roles
Least privilege by default
Owners, admins, members and viewers at the organization; leads, editors and viewers in each workspace. Joining the organization opens nothing — people see a workspace only once they are added to it.
Invites
Bring the whole team
Invite colleagues by email, including people who don't have an account yet. They land with the role you chose and nothing more.
Knowledge
Facts the team has agreed
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.
Audit
A record nobody can edit
Membership, roles, workspaces, projects and knowledge changes are written to an audit trail automatically. Admins can read it; no one can rewrite it.
Controls
Limits and switches per organization
Usage limits that follow your plan, the assistant on or off for the whole organization, and how long the audit trail is kept.
Portable
Your data, on open ground
Standard Postgres with row-level security as the only authority. Every rule travels with the data, so no single host holds your work.
What a sandbox draws on
One engine. One contract. Room to grow.
Compute
Studies painted onto your model
Ray-based studies painted straight onto your model, on the hardware you already have. Sunlight is free and established; View and Radiation come with Pro; Daylight is planned.
Projects
One project, every door
Rhino files linked to a project, with its documents, tags and studies alongside. A chat answers from that data — from Rhino or the web — and quotes numbers as stored, never estimated.
Organizations
Access by workspace
Workspaces with roles, invites and least-privilege access. Knowledge the team has approved, an audit trail no one can rewrite, and controls set once for the whole practice.
AI imagery
Images that say what they are
Diagrams, sketches, interiors, landscapes and more, drawn from your model in the language of the brief. Every export says it is imagined and records how it was made.
Harness
One typed contract
Every action is a typed command. The panel you click and a headless run call the same contract, so anything a person can do is something a machine can drive.
Your machine
Your model stays on your desk
Analysis runs locally. Your model never leaves the desk it was drawn on, and no run waits in someone else's queue.
Sunlight runs end to end in Rhino today and stays free. View and Radiation come with Pro and are still under validation; Daylight is planned. The project assistant is an early Pro preview. Nothing here is an EN 17037 certification claim.
Open your first sandbox.
Preview for Rhino 8 on Windows and macOS. Analysis runs on your machine — your model never leaves it.