CAD tools built around the engineering model.

The visible modeling command is only one part of product development. A mechanical design also carries requirements, dimensions, constraints, component relationships, drawings, review comments, earlier versions, and decisions about what may change or must remain fixed.

When those elements are separated into local copies, exported snapshots, messages, and disconnected review tools, the team spends time rebuilding context. Which file contains the accepted hole pattern? Was the supplier comment applied before or after the latest drawing? Does the assembly include the revised interface? Is the screenshot under review still connected to the geometry that produced it?

These questions affect whether an engineer can trust the design state before making the next change. zCAD is built around a simple response: keep the engineering model close to the project decisions that give it meaning.

An engineering model carries the logic of the design. A dimension controls size. A constraint protects a relationship. A feature records a modeling decision. An assembly defines how components are organized and positioned. A drawing communicates the definition beyond the 3D workspace. A version identifies the state of the project at a meaningful moment.

When this structure remains available, a revision begins from an understood decision rather than an anonymous surface or another file copy. The engineer can find the controlled relationship, inspect the surrounding geometry, update the documentation, and bring the new state into review. The model becomes a shared source for continued work, not an attachment passed between disconnected steps.

That principle shapes both zCAD products. zCAD Online supports direct parametric authoring and connected project work in the browser. zCAD AI begins with engineering intent expressed through prompts and turns it into structured CAD for inspection and revision. The interaction changes; the expectation that the model remains useful through the next decision stays the same.

Desktop CAD established the precision and depth required for mechanical design, but engineering teams often surround that work with transferred files, copied folders, exported screenshots, and separate review environments. Each handoff creates another place where project state can become unclear.

zCAD Online begins with a browser project. Modeling, product structure, drawings, versions, permissions, comments, sharing, and review stay close to the current work. An engineer can author geometry while another participant evaluates a known state of the project. The browser is therefore more than a place to open the software; it is part of an architecture that treats the project as the continuing context for engineering decisions.

This project-first approach makes access and history easier to understand. It gives teams a clearer answer to three practical questions: where the current model lives, which state is under discussion, and what decision created the next revision.

Direct control over sketches, dimensions, constraints, references, and features remains essential for many mechanical-design tasks. zCAD Online keeps that control explicit in the browser so engineers can work at the level of detail their product requires.

Other tasks begin with a requirement that is already clear in engineering terms but still has to be translated into a long sequence of interface operations. zCAD AI moves the starting point closer to that requirement. The user describes the function, interfaces, controlled dimensions, clearances, and conditions to preserve. The product creates structured CAD that can be measured, questioned, and revised through the same prompt-led interaction.

Intent-first modeling expands how people can enter CAD work. It gives domain knowledge a more direct route into geometry while keeping engineering inspection central to the result.

A screenshot can communicate what someone saw. A comment can communicate what someone thinks. Engineering review becomes more useful when both remain connected to the exact model state and product decision they refer to.

In zCAD Online, project history, versions, permissions, comments, sharing, and browser review provide that context around direct modeling. The reviewer can inspect the relevant geometry, identify the version, and return feedback against the design state under discussion. The engineer can then make the next revision with the reason for the change still available.

The result is not simply more conversation around CAD. It is a shorter path between feedback and the editable product definition that feedback is intended to improve.

Mechanical geometry must survive change. A bracket may need two holes held symmetric about a datum. A housing may need stable wall thickness, fastener clearance, and internal space for components. A shaft may need a bearing seat aligned to an assembly reference rather than placed by an isolated coordinate.

Dimensions, constraints, features, references, and assembly relationships make those conditions explicit. They help another engineer understand why the model behaves as it does and give a revision a controlled place to begin. The value appears when a requirement changes: one intended variable can move while the relationships that still matter remain available for inspection.

This is also the standard applied to AI CAD. A generated result becomes useful for engineering when important geometry can be measured, relationships can be identified, and the model can continue through a controlled change. Structured CAD carries the decision beyond the first image.

Consider an electronics housing whose mounting interface changes after supplier review. The new connector position requires two holes to move, but the outer envelope, wall thickness, internal component clearance, and neighboring assembly interfaces must stay fixed.

Choose direct parametric authoring and connected browser workflows with zCAD Online, or begin with written engineering intent and structured CAD generation with zCAD AI.