Windows-only access constrained Fortressware's 2008 beta when documents crossed organizational boundaries. Mobile, Mac, and Linux recipients could not open protected files, making the protection dependent on a compatible recipient environment.
Enterprise DLP offered a different level of administrative control. Fortressware lacked enterprise-wide controls, so its user-directed approach did not provide the centralized policy management buyers associated with DLP.
Fortressware occupied a middle ground between Adobe Acrobat's document restrictions and traffic-scanning DLP in 2008. Acrobat already supplied the basic protection concept; Fortressware extended it across more supported file types.
The key trade-off was where protection decisions were made. Document originators selected files and permissions, while DLP examined messaging traffic; Fortressware's lightweight client did not provide DLP-style enterprise-wide controls.
Fortressware's 2008 beta addressed document sharing through sender-controlled protection rather than comprehensive enterprise DLP. Personal Fortress wrapped selected files in permissions and used a free recipient client to control printing, redistribution, and modification.
Its value was narrower than an enterprise security platform: individuals could restrict particular files, but lacked enterprise-wide administration. The Windows-only beta also excluded mobile, Mac, and Linux recipients from protected documents.