No migration required
Keep existing files, models, and organization in place.
About Details
Founded by the people who were tired of searching.
Details was created to solve a problem faced on every MEP project: proven details already exist, but finding them breaks the design workflow.
See it in action
Detail management without leaving Revit.
The problem
Every firm has details. Few make them easy to reuse.
Engineers dig through old projects, ask coworkers, or redraw work that already exists. Details brings firm knowledge into the active Revit workflow instead of forcing teams into an external content system.
Revitis where engineers work, so it is where the detail library belongs.
Our approach
Connections that work the way your firm works.
Automatic knowledge sharing
Libraries grow through the work engineers already do.
Always current
Live links surface the latest container-model details.
Firm visibility
Admins see what teams sync and use most often.
Firm-wide tools
One connected system for engineers and BIM teams.
Firm Library
Your full detail repository
Search and filter synced details by title, discipline, project, version, and sub-discipline.
Organize
Personal folders for project work
Collect and share the details most relevant to a project without changing the shared library.
Standardize
Consistent sheets across the firm
Publish sheet templates with shared naming, numbering, detail spacing, and layout standards.
Cloud Usage and Security
Your project data belongs to your firm.
How Details uses the cloud, what is synced, and the safeguards that protect firm data.
Details Cloud Usage and Security Overview
Details is built for engineering firms that need fast access to their detail libraries without compromising security or privacy. Cloud syncs pull only what is needed to make details searchable: detail thumbnails for fast display; basic project metadata such as file path and file name for retrieval; and Revit metadata such as discipline, sub-discipline, associated equipment names, and keynote annotations for grouping. Usernames are stripped from project file paths when they are added to the Firm Library. Details does not save Revit models or full project files in the cloud.
Cloud infrastructure
Details uses Google Firebase Realtime Database, Cloud Storage, and Authentication to host firm cloud data. Data is encrypted at rest and in transit.
1. Firm-level data isolation
Each firm's project data is stored in a separate cloud partition. Isolation is enforced through Firebase Authentication custom claims. Every database request and file transfer is validated against the user's firm ID and role by server-side security rules.
- The authenticated user's firm ID must match the requested data partition.
- Only administrators can modify or delete data belonging to other users in the same firm.
- Standard users can write only to their own storage paths within their firm's partition.
Knowing another firm's identifiers or storage paths does not grant access; cross-firm requests are rejected by the server.
2. User-level data isolation
Within a firm, each user's synced projects are stored under that user's unique identifier. One user's library does not mix with another user's library.
3. License-based access control
Cloud operations are validated against the firm's active license. The license must belong to the correct firm and remain enabled. Deactivating a license immediately revokes cloud access.
4. Single-computer activation lock
Each license key can be active on one computer at a time. A hardware-based machine fingerprint is registered during activation, and attempts to use that key on another machine are denied.
5. No cross-firm data leakage
Database security rules limit users to data under their own firm ID and permitted user paths. Requests for another firm's data are blocked at the infrastructure level.
6. Read-only project connections
When Details connects to a Revit project for syncing, it opens the file in a read-only, detached mode. The original project file is not modified, and workshared models are not affected.
7. Cloud data management
Removing a project link locally does not automatically erase its cloud record, which helps prevent accidental data loss. Firm administrators can permanently delete any synced project from the Firm Library.
8. Encrypted machine identification
The activation fingerprint is generated with SHA-256 hashing. Hardware identifiers are not stored or transmitted; only the one-way hash is used.
9. HTTPS-encrypted transport
License validation, metadata synchronization, and thumbnail transfers use HTTPS encryption to protect data in transit.
10. Firebase infrastructure and data residency
Data is hosted on Google's Firebase platform in the US-Central region. Firebase provides infrastructure security, encryption at rest, backups, and service availability protections. Learn more in Firebase's privacy and security documentation.
11. No sale or advertising use
Details does not sell or rent firm data, provide it to advertisers, or expose it to other firms. Firm content is not used to train foundation AI models.
12. No full-model cloud retention
Cloud data exists to operate Details for your firm. Syncs contain thumbnails, paths, and metadata needed for search and grouping—not full Revit models, proprietary geometry, or complete project files.
13. Administrator data control
Firm administrators can permanently delete individual synced projects or wipe the entire Firm Library. Once deleted, that synced cloud data cannot be recovered by Details.
14. User-initiated sync only
Project data is not synced automatically. A user must explicitly start a sync, giving the firm control over which projects are stored in the cloud and which remain entirely local.
Work from what you already have