Questions that come up before the first project starts.

VENARO is an engineering workspace for vehicle development. Architecture, requirements, components, the engineering BOM, derivatives, networks and change decisions sit on one platform and stay connected to each other, so a change in one place remains traceable in the others.

The engineering BOM is the mature area and the one we are actively polishing: multi-level structures, variants and derivatives, mass and cost roll-ups, controlled revisions and a governed release path from working BOM to baseline. You can try it in the live demo without an account.

Vehicle architecture is next once the BOM area is complete. Requirements, change and release management, and network and CAN tooling exist in the product but are still being built out. We do not publish dates for these.

The product is in active development and ships without a fixed release schedule. Interfaces and screens can change between versions. Engineering data, roles and approval records are already handled as production data — they are not reset between updates.

Through the contact form on this site, or through the support system inside your workspace. For anything touching your data or your subscription, the in-product support system is the faster route because it carries your workspace context.

Yes, as CSV. Part number, parent assembly, quantity, mass, cost, supplier, make-or-buy, maturity and revision are read as structured fields, and variant quantities can be carried in the same file. Imports are previewed before anything is written. Excel workbooks are not supported at the moment; export your sheet to CSV first.

Yes. The BOM, variant assignments and the change history export to CSV at any time, for as long as your workspace is reachable — including while it is in read-only mode.

STEP, CATPart, CATProduct, IGES, GLB, GLTF, STL and OBJ are accepted as uploads and stored against the component.

GLB renders directly in the browser today. STEP, CATIA and the other formats are stored and prepared for conversion, but they do not display in the viewer yet. Upload GLB alongside the native file if you want a component to be visible now.

No. The viewer is read-only, and CAD editing is not planned. VENARO holds the geometry as evidence against a component revision; authoring stays in your CAD system.

We prepare the workspace and you nominate one contact. That person receives a single invitation link and uses it to create the first administrator account. There is no public sign-up, and we do not create user accounts on your behalf.

Seven days, and it can be used exactly once. After that the link is dead and an administrator issues a new one.

If an administrator account already exists, they simply issue a new invitation. If the very first invitation expired and nobody has an account yet, contact us: the workspace has to be reset and set up again, because we cannot create the first account from our side.

Administrators hold the same permissions as the owner, so day-to-day work is not blocked. Ownership itself cannot currently be transferred, and we cannot reassign it for you. Contact support and we will go through the options for your workspace.

A Pro user is a named, paid seat that can create, edit and delete engineering data, within the limits of their role. A Viewer is a named, free, read-only seat. Shared logins are not supported: every permission check runs server-side against the individual account.

The number of Pro seats follows your order. Viewer seats are unlimited and free.

Five: Owner, Administrator, Project Lead, Engineer and Viewer. They cover the usual split between administration, release authority and day-to-day engineering work. Defining your own roles is not possible yet.

Yes. Roles are assigned per project, so someone can be Engineer in one vehicle programme and Project Lead in another. Access is evaluated per project on every request.

Read-only access for people who need to see engineering data without changing it — suppliers, adjacent teams, management. How you use them is your decision; the seats are free either way.

Customer workspaces run on dedicated machines in European data centres. If your order specifies a different arrangement, that takes precedence.

Customer-hosted deployments are planned but not yet offered. We want installation, upgrade, backup, restore and rollback to be reproducible several times over before we hand the operation to a customer. Until then, hosting runs through our service.

Your workspace database is encrypted at rest and we do not access its contents in normal operation. For a hosted workspace, our operations team is technically able to reach it — that is inherent to running the environment — and does so only when you ask us to, for support or recovery. In a customer-hosted deployment the question does not arise. If you need this in contractual form, ask us for the data processing agreement.

Every request is authenticated against a server-side session and authorised against your role in the specific project. Passwords are stored as PBKDF2-HMAC-SHA256 hashes and never in recoverable form. Session cookies cannot be read by scripts, accounts lock after repeated failed logins, and logins and logouts are recorded as immutable events.

Backups are encrypted and checksummed, and a restore verifies the checksum before it touches anything. The encryption key is held separately from the archive: a backup without its key cannot be restored — by us or by anyone else.

There is no automatic updater and no fixed schedule; a version ships when it is ready. Each package includes the steps for backing up your encrypted data beforehand and for rolling back if an update goes wrong.

During Early Access, pricing is per Pro seat per month. Viewer seats are free and unlimited. The seat count for your workspace is the one agreed in your order.

Open a support ticket and we will process it. There is no minimum term during Early Access.

The workspace switches to read-only for one month. Everything stays visible and exportable during that period. After the month, the data is deleted and cannot be restored, so export what you need while the workspace is still reachable.

The usual reason is that a subscription has ended and the one-month export window has started. It can also follow a seat or billing issue. You receive an email whenever a workspace switches to read-only, stating the reason and what to do about it.