Platform

How a Grasshopper definition becomes a web app

ShapeDiver runs the Grasshopper definitions you already build on our servers and turns their inputs and outputs into an app anyone can use in a browser - no Rhino license, no plug-ins, no web development. This page is the map: how you get from a definition to a running app, and everything the platform handles for you underneath.

14-day trial. No credit card.

Diagram: your Grasshopper definition runs in the ShapeDiver cloud (Rhino and Grasshopper servers, caching, permissions, security), gets an interface built with App Builder or in code, and reaches people by link, embed, or API

The idea in one place

One definition, running in the cloud, usable by anyone

Everything below follows from a single idea. Your Grasshopper definition already holds the logic - the geometry, the rules, the outputs. What it’s missing is a way for other people to use it without Rhino or your plug-ins, and without you in the loop for every case. ShapeDiver supplies that: it runs the real Rhino and Grasshopper on our servers, exposes only the inputs and outputs you choose, and puts them behind an interface your colleagues, clients, or customers open in a browser. You keep building in Grasshopper; ShapeDiver makes the result available online.

The author workflow

From a Grasshopper file to a working app, in four steps

Set up your first model in your workspace
  1. 01

    Prepare.

    Install the free ShapeDiver plug-in and build your definition following our guidelines - the guidelines are what let the same definition run unattended in the cloud. Want a running start? Our library of example models gives you working Grasshopper definitions to open, upload, and adapt, from basic inputs and outputs to full App Builder apps.

  2. 02

    Upload.

    Drag the file into your browser, or send it straight from the Grasshopper canvas with the plug-in. If it follows the guidelines, it becomes a working online model in seconds.

  3. 03

    Configure.

    Set up how the model looks and behaves - the viewer (lighting, camera, AR, post-processing), which parameters people can change and in what order, and who is allowed to see it. You do all of this in your workspace on the platform, where you manage and share everything you upload.

  4. 04

    Share or embed.

    Send a link, embed the model in your own site, or drive it from your own application through our APIs. Update the definition later and everyone using it gets the new version.

Prefer to have the definition built for you? Our team can do that, and you own the result. Professional services

What you don't have to build

The hard part is already running

Serving a Grasshopper definition to real users, reliably, is a platform in its own right - and it’s the part you don’t have to build or maintain. Behind every model, ShapeDiver runs:

Auto-scaling Rhino and Grasshopper servers.

Compute spins up to meet demand, whether one person or a few thousand are using your app.

Caching.

Results that have been computed before come back instantly instead of being recomputed.

A permissions system that keeps your definition private.

The logic runs on our servers and is never exposed to the people using the app - they see only the inputs and outputs you chose.

Security and uptime.

SOC 2® Type II audited infrastructure, with cloud regions in the EU, the US, and Asia, and a 99% uptime record.

Compared with hosting Grasshopper yourself on Rhino.Compute, the difference isn’t mainly the running cost - it’s the implementation and ongoing maintenance you no longer take on.

Security & Trust

Two ways to build the interface

Build the front end your way

The app your users see (its controls, layout, and behavior) can be built two ways. Most people pick one and can mix in the other later.

Diagram: one model on the platform, two ways to build its interface - App Builder with no code in Grasshopper, or in code against the Viewer API with a coding agent; both drive the same ShapeDiver Viewer

Which one fits depends on your use case and your team - the deep pages help you choose.

Ways to deliver

Put the app where your users are

However you build the interface, the same model can reach people three ways:

Send a private link that anyone can open in the browser, no ShapeDiver account required - optionally carrying a saved parameter state so it opens exactly as configured. Or share the model with specific ShapeDiver users and your team, granting each only the access you choose: view, export, download, and more. The definition itself stays hidden either way.

Embed it.

Drop the model into your own website or app with an embed code or a model ticket, so it lives under your brand.

Drive it with your own code.

Use our backend and viewer APIs, with SDKs for TypeScript, .NET, Python, and PHP, to run computations and pull results into your own application, store, or ERP.

Selling online? The same delivery layer connects to Shopify and WooCommerce, and to tools like Speckle, Autodesk Forma, VIKTOR, and iJewel3D.

APIs, SDKs & integrations

The whole platform, at a glance

Explore the platform

This page is the overview. Each part below has its own page with the detail.

From the blog

How the platform works, in more depth

All posts

Platform

See it with one of your own definitions

The fastest way to understand ShapeDiver is to upload a definition and watch it become an app. Start a free trial (no credit card) or talk to us if you’d like help deciding whether it’s the right fit.

Not sure which solution you’re building? Start from your problem instead: Scan-to-print, AEC, Product configurators or Consultants & studios.

Talk to our team

Your Business

How can we help?