everteam.rrs vs Gimmal Records

everteam.rrs helps organizations centralize retention policies and manage document lifecycles across the organization. It links rules to legislative, regulatory, or normative references, and lets rules combine retention periods, trigger events, and final disposition with confidentiality, environmental, or security requirements. Users can delegate policy updates, validate change requests before publication, and retain a history of changes. Policies can also be published for employees. The retention repository can be imported or exported in XLS format, or described through a web interface; search and configurable properties are intended to support compatibility with existing repositories. REST APIs connect third-party systems, and Everteam IG Suite can apply lifecycle rules to sources such as Office 365, shared drives, messaging systems, and SAP. Deployment options are SaaS, private cloud, or on-premises, with API, self-hosted, and web platforms listed. Pricing is on request, and prospective customers are directed to contact Everteam. The company says it was founded in 1990 and joined the Kyocera Document Solutions group in 2020.

Gimmal Records manages records across enterprise repositories without requiring content to be moved elsewhere. A centralized dashboard provides visibility into information held across those repositories, while file plans, retention schedules, record classes, rules, and triggers help classify information and manage it through its lifecycle to disposition. Record controls include declaration actions, legal holds, record properties, and time-stamped audit entries; audit reports can be filtered and exported. A legal hold can pause a record's lifecycle and prevent disposition or modification while the hold remains active. Disposition can use ongoing inbox approvals or optional batch processing based on predefined rules. Documented connectors include Box, SharePoint Server, Documentum, FileNet, SharePoint Online, and Universal File Share, although some SharePoint connectors are marked deprecated. Deployment options include Gimmal-hosted cloud, customer servers, and customer cloud servers such as Azure. On-premises requirements include Windows Server 2016 or later, SQL Server 2016 or later, HTTPS, and TLS 1.2. Pricing is on request.