Available Now. V2.0.0

Bridge.

Move Rhino geometry into Revit family workflows without asking the project team to rebuild the same design work.

Free trial

Open the trial form and share the Rhino and Revit version context needed to route the setup.

Read the docs
Loose black ink sketch of a hand moving a small model card between a curved design sketch and a plan drawing.

Capabilities

Move Rhino design work into Revit families.

Bridge helps teams carry geometry, coordinates, and family intent into Revit without turning the handoff into a manual rebuild.

01

Create native families.

Bridge moves Rhino geometry into Revit family workflows so the output can carry parameters, schedules, and BIM context.

02

Preserve coordinates.

Geometry lands where the team expects it, so setup work is easier to review before documentation continues.

03

Keep iteration open.

Teams can refine design work in Rhino, then bring the next pass back into the Revit family workflow.

Workflow

Choose the family workflow that fits the geometry.

Start with standard families, add parametric structure when needed, or use adaptive components for more complex placement.

Licensing

Choose the license path that fits the team.

Bridge keeps monthly, annual, perpetual, and student routes visible so teams can decide before starting setup.

$19
SGD per month for commercial teams getting started.
$200
SGD per year for annual commercial access.
$400
SGD one-time perpetual license option.
Free
Student route remains separate from commercial trials.

Access

Start with the versions your team uses.

Bridge setup starts with Rhino and Revit version context so the trial can be routed to the right installer path.

What Bridge keeps close

Native Revit family output
Coordinate preservation
Two-way design iteration

What trial setup asks

Name and email
Rhino version
Revit version

Trial path

Open the trial form.

Share your Rhino and Revit versions when the team is ready to test the Bridge workflow.

Return to trial access

FAQ

Common Bridge questions.

These answers cover Rhino.Inside.Revit, Grasshopper knowledge, two-way iteration, supported versions, and licensing.

What is the difference between Senibina-Bridge and Rhino.Inside.Revit?+

Rhino.Inside.Revit requires Grasshopper expertise and runs both applications at the same time. Bridge is a standalone Revit add-in for teams that need the handoff without making every user a computational designer.

Do I need Grasshopper knowledge?+

No. Bridge is designed around layer selection, family intent, and production output, not scripting or node-graph setup.

Can I export back to Rhino for iteration?+

Yes. Bridge supports a two-way workflow so design refinement can continue in Rhino after Revit output has been created.

What Revit and Rhino versions are supported?+

Bridge supports Rhino 7 and 8, with Revit support across current .NET 4.8 and .NET 8 add-in targets.

Is there a perpetual license option?+

Yes. Bridge keeps monthly, annual, and perpetual commercial options, with student access kept separate.