The public product surface is unusually detailed about mechanics and commercial limits. DeskFerry documents schedules, triggers, approvals, knowledge, memory, run logs, app tiers, credits and action allowances rather than describing agents only in abstract terms.13 Its security material states that data and credentials are encrypted in transit and at rest, workspaces are isolated, and team access can be separated into admin, editor and viewer roles.4
The important limitation is evidence provenance. DeskFerry publishes customer testimonials and outcome figures, including lead-volume, response-time and hours-saved claims, but those examples are hosted by DeskFerry and are not independently audited.1 Current external coverage does not provide a substantial verified-user rating corpus or independent comparative test of DeskFerry's execution reliability, connector failure handling or long-running agent accuracy.
DeskFerry is also fully hosted rather than a self-hosted framework.2 Organizations with sensitive data should therefore evaluate its OAuth scopes, data retention, subprocessors and model-provider routing against their own policies rather than inferring privacy from the presence of encryption alone.