YPCad
English
Request a demo

How it works

The tool you have does not change. What changes is who reaches it, when, and with which version.

  1. Package the tool

    Upload your LISP and DLL files. The server reads them: it works out which commands they register and which AutoCAD releases they target, and writes the package definition itself. Your code is untouched, and no hand-maintained mapping is left behind.

  2. Publish

    The archive is extracted, validated, its SHA-256 computed on the server and its signature checked. A new version always lands in DEV: no upload goes straight to the whole company.

  3. Promote through channels

    First a pilot group (three to ten engineers), then everyone. A problem found in the pilot never reaches hundreds of people. If you want, promotion to the whole company can require a second administrator’s approval.

  4. Grant entitlements

    Who sees which package, who may use which feature — per person or per group. An engineer without an entitlement does not see the tool in the catalogue at all, so there is no disabled button to argue with.

  5. The engineer installs

    The catalogue opens inside AutoCAD and the tool installs with one click. Installation is atomic: it either completes or it never happened. There is no such thing as a half-installed tool.

A rollback is not a new release

Pulling a version back from the whole company means moving that version to a narrower channel — a single action. No repackaging, no republishing, nobody to wait for. Even with the four-eyes rule switched on, a rollback never needs approval: a control must not get in the way at the very moment speed matters most.

Loaded on demand

AutoCAD does not load tool code at startup; it reads a small registration that says “this command lives in that package”. The code loads the first time the command is called. Your catalogue can grow without slowing startup.

No network request is ever made on the AutoCAD startup path — a binding rule in this product, enforced by a test.

Offline operation

Installed tools live on the engineer’s machine and do not depend on the server. During maintenance, with the network cut, or out on site, the tools keep working; only new installs and updates wait.

The server being completely down means “no new tools can be installed”, not “engineers cannot work”. That distinction is an architectural property worth protecting.

Updating is a separate process

While AutoCAD is running, a loaded file is locked and cannot be replaced in place. Updates are handed to a separate updater program: it does the work, reports the result and steps aside.

A loaded assembly is never updated in place — a silently half-finished update becomes a tool that does not open the next morning.

Failures arrive with a number

When a tool stops unexpectedly the user sees a correlation number and sends it to you. The whole event — which package, which version, which AutoCAD — is already recorded.

It removes the “could you send a screenshot” traffic: diagnosis starts from the record, not from what the user remembers.

Let us do it with your tool

Send us one of your LISP or .NET tools. We will package and publish it together, install it on a test machine and roll it back. About an hour.

Request a demo