Fenritec Alpha

@petr_ivan Hi Ivan!

Thanks a lot for your thoughtful comment 🙌 Yes — we’ve designed Fenritec with data durability and availability as core priorities. All files are encrypted and then duplicated across multiple data centers — located in the EU and operated by different cloud providers. This ensures not only redundancy but resilience against provider-specific or regional outages.
The infrastructure is set up to auto-recover from service interruptions, and we continuously monitor production health with real-time alerts. This allows us to react quickly and ensure uptime, even in case of hardware failure or degraded performance.

@petr_ivan To give you practical implementation, your file data is live replicated on two different EU providers (OVH and Scaleway) and your metadata in the database (filename, creation date, etc) is replicated on 3 (OVH, Ikoula and Scaleway).

If an interruption would occur it would take 5-10min to update the DNS names up and redirect the traffic so that we would be Up again on most platforms. That said, on Windows the switch is transparent and you should not feel any disconnection as our Sync software is "Smart" and is trying a different IP address automatically if a timeout occurs.

Hope It answers all of your questions. ;-)

@patpijanowski Thank you. Yes we are thinking about it. We hope to deliver on this timeline :

• Sept 2025 : Time machine like backup restore UI available,

• Dec 2025/Jan 2025 : Collaborative feature with either Microsoft Office Server / Only Office Server and versionning

@vedant_roy2 Ok. First, I used to be a security Pentester (OSCP and ISO 27001 Lead implementer

certified) so I know very well how security should be made and what are the current issues all the market is facing).

On cybersecurity we think the issue in three parts :

• Availability : Fenritec Alpha is replicating your file data on two datacenters of two different provider (each provider replicating basically 2 times). If one fails there should be a small interruption of 5-10 min so that the DNS is updated to point only to the live datacenter. Plus we are making cold backups to keep your data safe an be able to restore it.

• Confidentiality : On that side we should avoid having vulnerabilities in the stack and ensure that all the data are encrypted during transit and at rest. For the encryption we only use TLS 1.3 with configuration from Mozilla and we encrypt at the moment your data with a RSA OAEP + AES256 CTR so that our cloud providers can't see the data (We can still help you if you have issues with recovery : it is not a vault with only you having the keys). And regarding vulnerabilities, we follow best practices in software updates, use safe languages in the backend (Golang), review the code and self maintain software libraries maintained by only a single guy (to avoid outsider risk), review our code periodically so that we don't introduce vulnerabilities.

• Integrity : As said before we use 2 data centers and we calculate cryptographic hash to ensure your data are not corrupted and still present.

Honestly, marketers like to sell "secure" products which is a nonsense from cybersecurity perspective. What we can ensure you is that we follow best practices in security to provide you with a product that has the highest resilience against data loss and that is protecting your privacy (We are not yest 27001 but we are planing to). And my answer is just the top of the iceberg.

Hope I was not too technical. If you have more questions, don't hesitate.

@sonika_thakor Thanks for the question. We store up to 4 month all your data after removal :

• 3 month to be able to restore it with the backup feature (ui available openly in sept 2025);

• +1month in cold backup to be able to execute any disaster recovery scenario on our side;
  
  If you keep your data in thrash it evens adds 1more month.