Show IH: Feedback on my file storage software

On reading your comment again, I think you are referring to issues with physical block-level sync (DRBD etc) across systems, but I was referring to the chunk of file data that changed.

Hi,

Thank you for taking time to write your feedback, it is much appreciated! :-)

To clarify, I am not doing block level sync right now as I do not have any client side apps written for this, but what I meant was that the logic has been written in the backend application already (although I am not exposing it via any API right now) so that a future client side app only has to sync the changed blocks (and not the entire file). My backend stack is a secret recipe altogether which gives me enough confidence to try these stuffs out.

Honestly, with this software I am targeting a class of business that is stuck in-between Dropbox and Box, and this software itself will potentially end up as a mix of best of both in the long run. And then there is a chunk of businesses who want such a solution on-premises.

This is a collaboration software, so the value comes only when there are many users. With email alerts, realtime alerts, audit logs, every action on a file or document can be tracked. Then there is versioning, so older copies of a file can also be recovered if necessary.

And then I have a new take on the concept of "Team Folders" which makes it ridiculously easy to collaborate on files within group, with multiple groups at once, and still further restrict access to those team members itself. I have found few Dropbox users wanting such advanced controls in their forums.

Data migration is what I will be working on next as soon the initial version is complete. With OAuth, it is not that a difficult task to fetch file list from any of the other apps, and then migrate the same to mine. I plan to implement OAuth in my software as well very soon, thus others can build solutions with my software as backend. Well, these are the plans for near future. Hopefully! :-)

Hi Caleb,

Yes, it is a secure collaboration tool, but workflow features has not been added yet. I am planning to add workflow in the advanced version once I complete and release this base one.

And I am so ashamed to tell you, I have not got both the landing page as well as a demo url at this moment. I was so excited to just show this out and get some feedback that landing page and demo skipped my attention, but my plans are to launch this within the next two months. I am still reading through the excellent material here in IH to do a product launch.

This will be my first product launch, so taking everything in a steady pace right now.

EDIT: I put up the landing page with more info at https://www.fileago.com/

Hi Juraj,

Thank you for taking a look!

There is not much value in this for a single user (except that a user can store his files and even retrieve older versions of files, and maybe share files with others using a publicly accessible url).

However, file sharing and collaboration inside a small (or big) company can be easily fulfilled with it. It will be released both on cloud as well as in-premises solution, so there is an option to choose as per the requirements of a company (security point of view).

Simple answer to you would be that it saves your time/money/energy exactly how the other solutions like Dropbox/Box do when you use its web UI. I have no native app to sync files yet, but necessary logic is already incorporated in the backend for block level sync, so in the future it can be done as well.

Imagine collaborating within a group, and then you invite 2 more groups to one particular directory, and then a third group with read only permissions for one its sub-directories, and then maybe entirely blocking access for a group member in a sub directory within it.

I find that even Dropbox do not allow the last part I said (check section 'Can I restrict access to a folder inside a team folder?' at https://www.dropbox.com/help/business/team-folders).

In a nut-shell, I believe my solution could offer a more granular way of restricting access. Plus, like I said, I have a different take on "Team Folder" concept, but I will not be able to reveal right now (I am really really sorry, but I hope you would understand).