Enterprise
Run it on your own servers, with nothing leaving your network
The public cloud suits most teams. Take this route when models must not leave your network, seats are counted per company, or availability and response times have to be in a contract.
Three shapes; pick the one your constraints allow
They differ only in where the data sits, who operates it and how far the commitments go. The product itself is the same.
Fully on-premise
Installed on your own servers or in your own data centre; model files never leave your network.
- Works fully offline — the server does not need internet access
- Models, accounts and logs all stay on your machines; we have no access
- Annual licence including upgrade packages and upgrade support
- Can be wired into your existing single sign-on
Dedicated instance
We deploy and operate a separate environment for you, with resources reserved for you alone.
- Separate servers and storage; conversion capacity is not shared with other customers
- Choose where the data lives; bring your own domain
- We handle operations, backups and upgrades — you do not need to staff it
- Contractual SLA with availability and response commitments
Enterprise on the public cloud
Use this site as it is, with seats, quotas and support terms agreed as a company contract.
- One invoice and central seat management for the whole company
- Higher per-file upload limits and storage quota
- Named contact and priority support
- Fastest to start — no infrastructure needed on your side
What the private deployment includes
The same product as the public cloud — nothing cut out. The difference is how it is deployed and what we commit to.
Every feature
Viewing, sharing, model health checks, clash and clearance detection, part drawings, quantity take-off, version comparison, project and element progress.
White label
Your company name and logo throughout, so what your client opens carries your brand, not ours.
Seats by contract
Member limits are agreed for your headcount rather than capped by a public plan.
Your existing accounts
Standard single sign-on, so staff use their existing corporate account and access ends when they leave.
Capacity follows hardware
Storage and conversion concurrency depend on the machines you provide, not on cloud quotas.
Rollout and training
Includes deployment, one training session on site or remote, and conversion tuning for your first batch of models.
Service levels we can put in a contract
These are commitments we can make per project — not terms already in force for every user. The exact numbers depend on the deployment shape and the cover you need, and carry remedies once signed.
- Monthly availability
- Up to 99.9% for a dedicated instance. For an on-premise install, availability depends on your own data centre and network, so responsibility is split at an agreed boundary.
- Response times
- Tiered by severity: two hours for a blocking incident, with round-the-clock cover available.
- Named escalation path
- A named contact and a direct channel, rather than a shared support queue.
- Upgrade windows
- Upgrades scheduled in an agreed window that avoids your project milestones, with a rollback plan.
- Data residency
- Where the data lives is your choice, or entirely inside your own facility.
- Backup and recovery
- Agreed backup frequency, retention and recovery time objective, proven with a real restore drill.
None of this applies to the public cloud version; its availability target, maintenance windows and response practice are set out in the Service Level Statement. Service Level Statement →
How it goes
- 1
Tell us the constraints
Use the form below or contact us directly: whether data may leave your network, how many people, how big the models are.
- 2
Proposal and quote
Within three business days you get a deployment plan, hardware requirements and a quote — plus a technical write-up for internal review if you need one.
- 3
Pilot
We run one or two of your real models through it to confirm conversion quality and performance before any contract.
- 4
Deployment and training
Remote or on-site installation, one training session, an operations handbook and the upgrade procedure.
- 5
Ongoing support
Upgrade packages and technical support under the contract, with advance notice of major versions.
Tell us what you need
We reply within one business day. Only the company, a contact name and one way to reach you are required.
Scan to reach us on WeCom and just describe what you need — there is a person on the other end.
Scan with WeChat to add
Common questions
- Can it be installed on a network with no internet access at all?
- Yes. The deployment package is self-contained; the server needs no internet access to install or to run. Upgrades are delivered as offline packages.
- What server does it need?
- It depends on your models and how many convert at once — conversion is the CPU- and memory-hungry step. We size it against your actual models in the proposal rather than quoting a generic minimum.
- Can we try it first?
- Yes. Most customers run real models on the public cloud first to confirm the fit, then discuss deployment. A pilot installation is also possible.
- Do we still get new features after going on-premise?
- Yes. The annual licence includes that year's upgrade packages; you decide when to apply them.
- Does any model data come back to you?
- An on-premise deployment sends us no model data at all. For the public cloud, how data is handled — including what happens after you delete a model — is set out in the Privacy Notice.