the problem
Files have to be fast at every site and consistent across all of them.
Branch users want local-LAN speed. The organization needs one authoritative version of each file. Traditional NAS does not stretch across sites, and sync products drift.
- Per-site NAS fragments the file estate and multiplies operations.
- Sync products trade authority for performance, or the reverse.
- Ransomware needs versioned files an attacker cannot overwrite.
- Cloud-only file conflicts with data-residency requirements.
the joint solution
Nasuni Edge with a Scality back end.
Nasuni Edge appliances cache active files locally per site. Scality RING holds the namespace centrally. Files written through Nasuni land in RING as objects, with versioning preserved.
- One global namespace from a single Scality cluster, fed by site-local Nasuni caches.
- Object versioning lets any file roll back without a backup-restore window.
- Capacity grows by adding Scality nodes; reach grows by adding edges.
- Runs entirely on-prem when residency matters.
joint solution benefits
What Nasuni on Scality delivers.
One file space across sites.
UniFS gives every location the same file system. Scality is the canonical store; the edges cache locally for performance.
Object-versioned file recovery.
Each save becomes a new object version. Recover any file or share to any point in time without a backup restore window.
Scale by adding edges.
Add Nasuni edges for sites, add Scality nodes for capacity. Neither side forces a re-architecture of the other.
On-prem for sovereign estates.
UniFS plus Scality runs entirely on-prem across multiple data centers under one administrative domain.
Joint architecture
How Nasuni runs on Scality.
Workloads flow through the partner integration and land on the Scality data layer.


















