Show HN: LockFS

[0xGhostInAJar]

LockFS is a small open-source Java tool that encrypts files individually instead of bundling everything into a single container.

Many vault systems rely on large encrypted blobs or container files. They can become complex to handle as they grow and complicate backups across mixed storage sizes.

LockFS takes a file-level approach: - Each file is encrypted independently - No monolithic container growth - Files can be added, moved, or removed without rewriting a large archive

Contributions and feedback are welcome.

[giuliomagnifico]

Nice but… Java? In 2026? Why it’s written in Java?

[0xGhostInAJar]

Java was chosen because it offers a strong balance for this project in terms of portability, ecosystem maturity, and development velocity.

Rust would absolutely be a strong candidate for a security-focused tool like this. However, Java provides mature cryptographic APIs and straightforward cross-platform distribution via a single JAR.

C and C++ offer performance and control, but they introduce additional complexity around manual memory management and long-term maintenance. For this project, working in a managed runtime helps reduce certain classes of memory-related bugs.

Python is very productive and has excellent libraries, but for a file-heavy encryption workflow the performance characteristics and stronger static typing of Java are preferable.

[atmanactive]

How does it compare to Cryptomator?

[0xGhostInAJar]

LockFS is different from Cryptomator. Instead of mounting an encrypted virtual drive, it encrypts files individually on disk. This keeps the design simpler and avoids issues related to mounted filesystems. It also does not depend on a centralized config file, so encrypted files can be moved, added, or removed independently without breaking anything