Revit Server Guard (RSG) is a powerful administrative module that turns the standard Revit Server into a secure and transparent environment for team collaboration.
The solution eliminates Revit Server’s main weakness — the lack of flexible access-rights management. RSG does not merely observe — it actively controls the data-exchange process, preventing mistakes in complex BIM projects.
Choose the license type, users, subscription term, Revit Server versions and license count. For a perpetual license, the term is shown as ∞.
Rules are built from users, groups, roles, projects, sections and operation types: browse, open, write, publish and administration.
The product catalog is now organized by product line: Revit Common Data Environment for server-side BIM infrastructure, then Revit plugins, then the separate 3ds Max plugin line.
The main product line for Revit infrastructure. The first commercial module inside CDE is Revit Server Guard: access rights, users, groups, projects, model sections, RS gateways, proxy servers, audit and routine operations.
Applied extensions for daily BIM work: batch processing, migration, synchronization, element descriptions, model checks and export workflows.
A separate line for visualization and production: BricksMap, FoliageTool, HDREnvironment and UVModifier. Each plugin has its own product card, price and checkout.
We are not saying that someone will intentionally damage another team’s work. In real BIM projects, many participants from different companies have different responsibilities and different levels of training. It is often impossible to teach everyone and then constantly verify that they strictly follow the agreed workflow. RSG solves the problem technically: if an action is not allowed, it is blocked before it can affect the project.
In RS itself there is no transparent way to assign access by user, group, project, model section and action. RSG adds this control layer.
On complex projects, instructions and training alone are not enough: too many companies, roles and temporary participants work in one environment.
The user sees and performs only what is allowed for their role. Accidental and intentional actions outside responsibility are stopped at the proxy layer.
BIM administrators see who requested what, which rule allowed or blocked it, and where rights need to be adjusted.
Install RSG next to the existing Revit Server, connect users and groups, define projects, sections and allowed actions. After that, every request passes through RSG before it reaches Revit Server.
The Revit client connects to the familiar RS address, while the RSG TCP proxy accepts the connection and forwards it only after the check.
Rules are built from users, groups, roles, projects, sections and operation types: browse, open, write, publish and administration.
Set who can see, open, edit, publish or administer each project and model section.
Allowed requests pass through to Revit Server. Forbidden actions are blocked and written to the audit log.
When an admin clicks «Activate via the internet», RSG.Server sends a short JSON to our License API. The site assembles the payload, signs it with the private key, and returns an envelope. The client verifies the signature with the embedded public key.
Temy by RSG, by plaginam Revit and by plaginam 3ds Max — in odnom meste, pod obschim akkauntom. Openoe chtenie for vsekh, sozdanie tem — for zaregistrirovannykh, privatnye sections — for customers with active license.
Chtoby litsenzionnyy status, zakazy and temy zhili pod odnim akkauntom. On forume vidno, kto from uchastnikov — pokupatel with active license, kto trialschik, a kto gost. This silno menyaet kachestvo otvetov in tekhnicheskikh vetkakh. And SSO odno — mezhdu saytom, accountom and forumom.
Pereyti k forumu→If your answer isn't here — write to the forum or to support@. We answer on business days within 24 hours; for priority support — within SLA.
RSG switches to bypass mode — protection turns off, Revit Server keeps working as usual. This is intentional, so customers don't run into a broken production environment at the moment of expiration. Once a license is installed, RSG returns to Full mode.
Yes. The trial starts automatically without contacting our server. License activation is done via files — .rsgreq (license request, downloaded from the admin panel) and .rsglic (signed license, uploaded back). The site never reaches into the customer's infrastructure.
The machine fingerprint is calculated from the machine name and the MAC addresses of network interfaces. If the host name and MACs are preserved, the fingerprint stays the same and the license remains valid. If hardware was changed, re-activation with the same key is needed (by default one key — one machine, but this is configurable via the quantity parameter).
Yes. For Russian legal entities — invoice in rubles, act, UPD, support for INN and KPP. The companyUid field becomes part of the license payload, so the customer's admin panel shows which organization the key was issued to. For international customers — Stripe invoice to the company.
Yes. A license can be issued either for a specific list of versions [2022, 2023, 2025] or for all versions (unlimitedRsVersions = true). RSG automatically detects RS versions installed on the host and suggests the right tier for the number of versions you need.
Not yet, the first releases are in development. Subscribe to the blog or watch for an announcement on the forum — buyers who already have an RSG license will get a discount when plugins go on sale. Technically the plugins use the same License API and the same cabinet — we're building it all on one platform to avoid unnecessary duplication.
Run RSG next to Revit Server and check it on a test project. You will see immediately what Revit Server itself does not do: rights are enforced before a user can accidentally or intentionally harm the project.