Optimized file moves via API on client-owned storage

Optimized file moves via API on client-owned storage

Optimized file moves via API on client-owned storage

We’ve implemented an optimization for file moves via API when clients are using their own storage infrastructure (outside of HERAW’s AWS environment).


From now on, when a file is moved within the same external storage (e.g., client-owned server) and hasn’t yet been registered in HERAW’s internal database, the system no longer triggers a copy to HERAW’s AWS storage.


Instead, the file remains on the original client-managed environment, which results in:


  • ⚡️ Faster operations and reduced processing times

  • 🌱 Lower environmental impact by avoiding unnecessary data duplication

  • 🔐 Respect of storage sovereignty for clients managing their own infrastructure



This change makes HERAW’s behavior more efficient, eco-conscious, and aligned with client infrastructure strategies.

We’ve implemented an optimization for file moves via API when clients are using their own storage infrastructure (outside of HERAW’s AWS environment).


From now on, when a file is moved within the same external storage (e.g., client-owned server) and hasn’t yet been registered in HERAW’s internal database, the system no longer triggers a copy to HERAW’s AWS storage.


Instead, the file remains on the original client-managed environment, which results in:


  • ⚡️ Faster operations and reduced processing times

  • 🌱 Lower environmental impact by avoiding unnecessary data duplication

  • 🔐 Respect of storage sovereignty for clients managing their own infrastructure



This change makes HERAW’s behavior more efficient, eco-conscious, and aligned with client infrastructure strategies.

We’ve implemented an optimization for file moves via API when clients are using their own storage infrastructure (outside of HERAW’s AWS environment).


From now on, when a file is moved within the same external storage (e.g., client-owned server) and hasn’t yet been registered in HERAW’s internal database, the system no longer triggers a copy to HERAW’s AWS storage.


Instead, the file remains on the original client-managed environment, which results in:


  • ⚡️ Faster operations and reduced processing times

  • 🌱 Lower environmental impact by avoiding unnecessary data duplication

  • 🔐 Respect of storage sovereignty for clients managing their own infrastructure



This change makes HERAW’s behavior more efficient, eco-conscious, and aligned with client infrastructure strategies.