Build the automation once. We handle everything that isn't engineering.
Licensing, payments, installers, updaters, deployment, analytics, marketing, enterprise distribution. The parts that stop good AEC tools from ever reaching the people who need them.
Revenue
You keep 70% of every transaction
No listing fee, no monthly platform charge, no fee for updates. The commission is the whole business model, it is stored on each order as charged, and it is the same number for everyone unless you have negotiated otherwise in writing.
- Set your own prices and intervals
- Issue discounts and private customer rates
- Monthly payouts with a reconcilable statement
- Company and enterprise buyers you would not reach alone
Payment processing fees are absorbed by the platform share, not deducted from yours.
Getting your tool in
Three ways to submit, depending on how much you want to declare
Adapt, don't rewrite. We never touch your business logic.
Source upload
Best for a tool that already exists
Upload what you already maintain. We read it, build it, and ask you to confirm.
- Automatic inspection and isolated build
- Detected inputs and outputs
- Confirmation screen before anything is published
Guided package
Best for production deployment
Declare the contract yourself. More predictable than detection.
- Explicit contract
- Version-specific builds
- Reproducible releases
Routines SDK
Best for deep integration
Implement IToolOperationHandler. A new operation is a new class.
- Handlers discovered by reflection
- Transactions opened only when you modify
- Cancellation and structured responses
Runtimes
What you can publish today
C# / .NET
.csx .zip- Execution
- Loaded into an isolated AssemblyLoadContext inside the host process.
- Protection
- IL obfuscation, strong-name + package signing, encrypted delivery.
Python
.py .pyw .zip- Execution
- Runs in a Hub-managed virtual environment or the host's IronPython/CPython bridge.
- Protection
- Bytecode packaging, encrypted package store, in-memory loader.
Dynamo
.dyn .zip- Execution
- Executed headlessly through the Dynamo engine with Hub-supplied inputs.
- Protection
- Graph never written to disk in clear text; opened from an encrypted stream.
Grasshopper
.gh .ghx .zip- Execution
- GHX definitions run in Revit 2024 through Rhino.Inside and Rhino 8, with inputs in Hub V2.
- Protection
- Signed encrypted definitions; the release key requires an active license and authorized device.
What you stop building
The infrastructure tax, gone
Most AEC automation never gets commercialised because the surrounding system is a bigger project than the tool itself.
Questions developers ask first
Ready to see what your tool is worth?
Create an account, upload what you already have, and the inspection report will tell you what the platform detected before you commit to anything.
Create a developer account