VicoWang Posted August 13 Posted August 13 (edited) Hi everyone, Vico here. As the VedaCAD ecosystem continues to grow, I wanted to create a dedicated, centralized thread to act as our official support and updates hub on the forum. For those new to the project, VedaCAD (vedacad.com) is a modern cloud package manager and environment synchronizer for CAD: The Client: A unified, pure LISP (.vlx) engine that natively manages all your CAD plugins and environment configurations via an isolated local sandbox (Zero-Install, bypassing traditional APPLOAD fragility). The Cloud Ecosystem: Personal Tiers: A frictionless, unlisted distribution network where developers can share tools instantly using 6-character ShareCodes (VCIDs)—no review bottlenecks, what you code is exactly what is delivered. Enterprise Tiers (B2B): A Zero-Trust infrastructure with granular RBAC for internal employee synchronization, and 'Project Arks' for strict sub-contractor drafting standard enforcement. Open Ticket System Please treat this thread as our open ticket system. If you encounter any bugs, have optimization suggestions, or need usage help, drop a reply here. I promise to respond to every single question within 48 hours. Architecture & Data Sovereignty We take performance and data compliance seriously. VedaCAD spans 6 user tiers (BASE, FREE, PRO, TEAM, CORP, and CORP(DED)). To guarantee low latency and strict data residency compliance globally, our backend is deployed across 5 major geographical data centers (ENAM, WNAM, EU, APAC, and OC), powered entirely by Cloudflare's edge network. Version Updates Whenever the VedaCAD client receives a version update, I will post the official Release Notes and changelogs right here in this thread. Share Your Work! Lastly, this space belongs to the community! If you are a developer and have published your plugins on VedaCAD, you are highly encouraged to share them here. Please drop your VCID, a link to your original forum release thread, and a Demo GIF if you have one. Example: [Codebase Packer] VCID: 0FBGZB @ VedaCAD https://www.cadtutor.net/forum/topic/99202-sharing-a-lisp-codebase-packer-thoughts-on-modern-cad-environment-governance/ Edited August 13 by VicoWang Quote
VicoWang Posted August 13 Author Posted August 13 v1.0 Jul 21, 2026 - Initial version released - Pioneer plan launched VedaCAD V1.0.VLX --- Known items to be optimized in V1.0: Auto-filling Asset Name from File Name (Thanks to zaphod's suggestion, we will add this feature in the next version) Quote
VicoWang Posted August 14 Author Posted August 14 4 hours ago, BIGAL said: OC. No we are Aussies ! AUS. Haha, fair point BIGAL! "OC" (Oceania) is just the boring geographical zone our cloud provider uses on the dashboard. But rest assured, the actual physical node is sitting right there in Sydney, making sure the Aussies get the absolute lowest latency possible! Cheers, mate! Quote
VicoWang Posted August 15 Author Posted August 15 (edited) TIPS： Why is VedaCAD called a modern CAD package management tool? As a developer or curator, you can publish your plugins on the client side, or combine plugins from other developers into a professional bundle for sharing. The web dashboard will provide statistics and displays for these plugins or bundles, allowing you to accurately grasp each asset's downloads. You no longer need to guess whether anyone is using your tools. Your web dashboard will provide you with precise, real-time telemetry data: global download volume, physical device installations, and most importantly—how many enterprises have officially adopted your VCID as their corporate standard, among other data metrics. Even for free-tier users, the web dashboard is fully provided. Edited August 15 by VicoWang Quote
VicoWang Posted August 15 Author Posted August 15 v1.1 Aug 16, 2026 Download link: https://www.vedacad.com - Auto-filling Asset Name from File Name (Thanks to zaphod's suggestion) - Enhanced Network Stability - Fix known bugs Quote
Jeffery2145 Posted 2 hours ago Posted 2 hours ago On 8/13/2026 at 7:34 AM, VicoWang said: Hi everyone, Vico here. As the VedaCAD ecosystem continues to grow, I wanted to create a dedicated, centralized thread to act as our official support and updates hub on the forum. For those new to the project, VedaCAD (vedacad.com) is a modern cloud package manager and environment synchronizer for CAD: The Client: A unified, pure LISP (.vlx) engine that natively manages all your CAD plugins and environment configurations via an isolated local sandbox (Zero-Install, bypassing traditional APPLOAD fragility). The Cloud Ecosystem: Personal Tiers: A frictionless, unlisted distribution network where developers can share tools instantly using 6-character ShareCodes (VCIDs)—no review bottlenecks, what you code is exactly what is delivered. Enterprise Tiers (B2B): A Zero-Trust infrastructure with granular RBAC for internal employee synchronization, and 'Project Arks' for strict sub-contractor drafting standard enforcement. Open Ticket System Please treat this thread as our open ticket system. If you encounter any bugs, have optimization suggestions, or need usage help, drop a reply here. I promise to respond to every single question within 48 hours. Architecture & Data Sovereignty We take performance and data compliance seriously. VedaCAD spans 6 user tiers (BASE, FREE, PRO, TEAM, CORP, and CORP(DED)). To guarantee low latency and strict data residency compliance globally, our backend is deployed across 5 major geographical data centers (ENAM, WNAM, EU, APAC, and OC), powered entirely by Cloudflare's edge network. Version Updates Whenever the VedaCAD client receives a version update, I will post the official Release Notes and changelogs right here in this thread. Share Your Work! Lastly, this space belongs to the community! If you are a developer and have published your plugins on VedaCAD, you are highly encouraged to share them here. Please drop your VCID, a link to your original forum release thread, and a Demo GIF if you have one. On a separate note, I’ve also been looking at the TVRem Remote App as an example of how specialized utilities can centralize device control without adding unnecessary complexity. A TVRem Remote App can be useful for managing compatible TVs and media devices directly from a phone, which fits nicely with the general idea of keeping everyday tools accessible from a single interface. Being able to isolate the local environment sounds useful because one of the recurring headaches with CAD plugins is that a perfectly working setup can break after another application or plugin changes a support file or load path. For the cloud side, I'd also be interested in seeing a little more detail about versioning and rollback. If a developer publishes an updated package and it introduces a problem, can users or project admins pin a specific version, or quickly revert to the previous one? Likewise, for the Enterprise tiers, the RBAC and Project Ark approach sounds useful for subcontractor workflows. The practical test for me would be whether an admin can enforce a known plugin/environment configuration without preventing individual users from keeping their own unrelated CAD customizations. I'll definitely keep an eye on the release notes. Having the changes documented in one thread should make it much easier to tell whether a problem is specific to a new VedaCAD version or to the underlying CAD setup. Quote
VicoWang Posted 1 minute ago Author Posted 1 minute ago 1 hour ago, Jeffery2145 said: Being able to isolate the local environment sounds useful because one of the recurring headaches with CAD plugins is that a perfectly working setup can break after another application or plugin changes a support file or load path. For the cloud side, I'd also be interested in seeing a little more detail about versioning and rollback. If a developer publishes an updated package and it introduces a problem, can users or project admins pin a specific version, or quickly revert to the previous one? Likewise, for the Enterprise tiers, the RBAC and Project Ark approach sounds useful for subcontractor workflows. The practical test for me would be whether an admin can enforce a known plugin/environment configuration without preventing individual users from keeping their own unrelated CAD customizations. I'll definitely keep an eye on the release notes. Having the changes documented in one thread should make it much easier to tell whether a problem is specific to a new VedaCAD version or to the underlying CAD setup. Hi Jeffery, Thanks for the great questions. You have an incredibly sharp eye for deployment architecture, and your questions highlight the exact technical nuances we had to navigate when building our engine. Here is exactly how VedaCAD handles those scenarios under the hood: 1. The Support Path Nightmare (Environment Isolation) We hate path-pollution as much as you do. VedaCAD operates a "Version-Isolated Sandbox" (stored safely in %APPDATA%\VedaCAD\...). When VedaCAD injects enterprise standards (like .CTB or .SHX folders) into AutoCAD's native SupportPath, our LISP microkernel runs a non-destructive prepend algorithm. It parses the existing string, removes only the old VedaCAD sandbox paths, injects the new ones, and leaves every other native or third-party path completely untouched. Your existing CAD setup remains structurally pure. 2. Versioning and Pinning (The Update Strategy) We handle version control via two distinct architectural pathways depending on asset ownership: External Assets (Community VCIDs): Because you don't own the source asset, you cannot mathematically "rollback" the original developer's release. Instead, VedaCAD uses a Freeze Version Policy (Pinning). When an Admin imports an external tool via its ShareCode, they lock it to a specific safe version (e.g., v1.2). If the original developer pushes a buggy v2.0, your enterprise fleet ignores it. Your dashboard simply flags an 'Upstream Patch Detected', giving the Admin the choice to test it first in a sandbox squad, and click 'Deploy Patch' when ready. Internal Assets (Owned by your Enterprise): For plugins your company develops, every single deployment is permanently recorded in a strict "Version Audit Ledger". If a bad script goes live, the Admin simply pushes the corrected version centrally. During their next heartbeat, all CAD terminals will silently hot-swap to the fix in the background. 3. Enterprise Enforcement vs. Personal Customizations This is the most critical balance to strike, and it’s exactly why we split our B2B offering into two distinct operational paradigms: Team Workspace (Hybrid Mode): This is for agile firms. Admins push standard corporate assets, but employees retain their personal CAD autonomy. Their local VedaCAD client still has the 'Manage' card, allowing them to add their own purely local scripts or mount shared VCIDs from the community. However, when a remote kill-switch is triggered by the Admin, our physical shredder will clear all cloud-synced assets (including those community VCIDs), explicitly bypassing and preserving only their pure local scripts. Enterprise Workspace (Zero-Trust Hegemony): This is for strict, defense-level compliance. In the Enterprise tier, user customization is mathematically eradicated. Local installation and external VCID fetching capabilities are completely disabled at the kernel level, and the 'Manage' card physically disappears from the user's interface. They can only see and execute what the Enterprise Foundry explicitly assigns to their Squad. If you’d like to test the sandboxing logic yourself, feel free to sign up for a personal account to try the client. You can also explore the exact enterprise management dashboard we discussed by clicking the 'Get Demo' button on the Team or Enterprise cards on our pricing page (vedacad.com/pricing). I'll keep the release notes updated in the main post. I'd love to hear your thoughts once you've put it through its paces! Cheers, Vico Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.