Roll it out to the whole team.

Single sign-on, directory sync, one drawing standard applied by every engineer, and a dedicated tenancy under zero-retention handling.

Fits the way your team already signs in.

Single sign-on over OIDC

Entra ID and Okta are what customers bring, and any provider publishing an OpenID Connect discovery document is configured the same way. There is no SAML, no WS-Federation and no LDAP.

Directory sync with SCIM 2.0

Joiners get a seat and leavers lose one, from the directory you already run. One endpoint serves every provider.

Roles, seats and an audit trail

Owners, admins and members, with domain verification and an activity log that names whether a person, a SCIM sync or a first SSO sign-in made each change.

What your team gets.

One drawing standard, every engineer.

Upload your title block and drawing rules once. Drawings Mode produces sheets on that standard, so output does not vary by who was assigned the job.

A dedicated tenancy, under zero retention.

Enterprise runs in its own cloud tenancy. Prompts and model context are processed to answer the request and kept on no CADABRA server. Your vault is never uploaded wholesale.

Find the part instead of redrawing it.

Ask across the models your team has indexed, filtered to the account that wrote them, and reuse what exists.

Configured to how your team works.

Modeling rules, naming, materials and libraries are set per organization, so the copilot follows your conventions rather than generic defaults.

Who it is for.

  • Engineering teams where output has to look the same whoever produced it.
  • IT and security owners who need SSO, provisioning and a straight answer on data handling.
  • Organizations under review that must document where CAD data goes and who reached it.

Questions from IT and security.

Where does CADABRA process our CAD data?
CADABRA runs as an add-in on your workstation and reaches a hosted processing environment for inference. It does not run offline. Enterprise runs in a dedicated cloud tenancy under zero-retention handling, so prompts and model context are processed to answer the request and kept on no CADABRA server. Your vault is never uploaded wholesale: what leaves the workstation is the context a given prompt needs.
Is CADABRA secure for company data?
CAD content is encrypted in transit and at rest, under a key held in a hardware-backed vault separate from the data. Indexed content is filtered to the account that wrote it. CADABRA does not sell customer data. Enterprise adds single sign-on and zero-retention handling; on every other plan you can turn training off in dashboard settings.
Will the drawings follow our company standards?
Yes, once you have set a standard up. You upload drawings you have already released and CADABRA extracts your title block fields, projection angle, units, text height and standing notes from them. That standard is then applied to every drawing it generates.
Do you train on my CAD files?
By default on Free, Student, Standard and Professional, yes: the EULA and privacy policy state that CAD geometry, prompts, and metadata may be used to operate, maintain, and improve CADABRA and its AI models. You can stop it at any time with the data setting in your dashboard, which takes effect from the moment you turn it on rather than retroactively. On Enterprise, zero-retention handling is configured as part of the agreement.
Does CADABRA integrate with PLM or PDM?
No PLM or PDM connector today. CADABRA works on the files you have open and the drawing standards you upload, and your PDM rules around those files keep applying. If a connector matters to your team, tell us which system.
What security controls does CADABRA have?
CADABRA answers a security questionnaire directly, against the controls in place today. Single sign-on and role-based access on Enterprise. Encrypted in transit. A second at-rest layer under a key held in a hardware-backed vault separate from the data, one setting on every plan. Indexed CAD content filtered to the account that wrote it. Only the context a given prompt needs is loaded at run time. A 90-day expiry on the operational logs CADABRA keeps about the service. Zero-retention handling on Enterprise, configured per organization.

Talk to us about a pilot.

A short call on your standards, your identity provider and how a rollout would run.