For IT reviewers and detailers

Rebarkit technical details

The practical facts about installing and running the Rebarkit add-in for Autodesk® Revit®.

Installation facts

• The distribution is one x64 MSI with selectable features for each supported Revit version.
• Installation is per Windows user under %APPDATA%; the reviewed installer does not write to Program Files, protected system locations, or the registry.
• Administrator rights are not required by the reviewed installer. Company software policy may still require an IT-approved installation process.
• The installer does not provide a separate family or content pack. Close Revit before installation, then start or restart Revit when setup is complete.
• Rebarkit relies on the runtime hosted by Revit. It does not bootstrap a separate .NET runtime.

Model impact

Rebarkit creates and edits standard Revit elements. The reviewed product code:

• does not add custom or shared parameters;
• does not register updaters;
• does not write extensible storage;
• does not depend on specific families; and
• leaves created content editable after uninstall.

These statements reflect the reviewed command, core, and service code paths. They are product behaviour claims, not a substitute for an organisation's own software review.

Licensing behavior

Rebarkit is free to use with no time limit or trial countdown. Once it is useful in your workflow, licensing is agreed by quote for the team size.

• LicenseSpring performs hybrid validation: an online check can fall back to a local check with a 30-day offline grace period.
• Initial activation requires connectivity.
• Activation sends the license key plus first name, last name, email, company, and country to LicenseSpring.
• Local license state is stored per user under %LOCALAPPDATA%\GRevity Point\Rebar Tools.

Usage analytics

Rebarkit uses Mixpanel with EU data residency handling. Analytics is currently enabled when the analytics service is initialized and there is no user-facing opt-out.

• Command events include the license-key-derived distinct ID, command name, result, count, Revit version, and add-in version.
• An event message may include exception text.
• The license activation flow also sets a Mixpanel People profile.
• Name, email, company name, and registered country can therefore be associated with usage data.

Analytics calls are fire-and-forget, so a network failure should not block normal command execution. A paid analytics opt-out is available only by explicit customer arrangement. Contact GRevity Point to discuss.

Outbound services

Rebarkit may communicate over HTTPS with the following services:

• LicenseSpring for license activation and validation.
• Mixpanel for usage analytics with EU data residency handling.
• Google connectivity probe at google.com/generate_204 to detect whether network access is available.

The exact LicenseSpring and Mixpanel hosts and TLS behavior are managed by their SDKs rather than hardcoded in the add-in. A formal security review should verify the deployed SDK traffic for the release being assessed.

Compatibility by release

Compatibility belongs to each release because the supported Revit range can change. Check the Rebarkit release notes before deployment.