Thanks! And good point. I'll add a comparison page on the website. But to answer your question, the main difference is price.

AWS Transfer Family was way too expensive for my use case. You have to pay $219 (0.3 * 730) just to get an SFTP endpoint, and then you get billed $0.04 per GB in or out, and that's on top of their usual $0.1 of data transfer fees. For this price, you get more control over the way your users can authenticate; this also means more configuration.

Baskt offers mostly the same features. You get an SFTP endpoint in front of your S3 bucket, the ability to easily manage users, and you can leverage the rest of AWS for your file processing thanks to S3 events. It just will not offer as many customization possibilities as AWS.

I will soon add some more features, like webhook notifications, the possibility to generate sharing links to upload or download files, and a file explorer. These features should help make Baskt a more complete tool for B2B file sharing than the bare-bones AWS solution.

The main thing I had to take into consideration when determining the pricing was concurrent usage. If I offer access to 10 users, I have to provision enough servers to handle the concurrent load of these users. Because of the file processing that's going on, CPU usage can be quite high, which drives the cost up. Also, other companies in the same field usually have plans starting at around $50.

Now, from what you are saying, I see that you would need more users but not more concurrent usage. This makes me think that the pricing would be better if it was for concurrent connections rather than users themselves. For example, 10 concurrent connections with 2k max users. This is possible.

I wrote a bit below about AWS Transfer Family, and it comes with a fixed price of $0.30 an hour per SFTP endpoint, making it come to $219 a month without data transfer fees. It's actually one of the reasons why I created Baskt.

For the web UI, it's on my roadmap and should be the next major feature I will release. I was thinking about integrating it along with the SFTP server by using the same S3-compatible buckets. But you seem to be more looking to keep your own server. I guess you would rather bridge your SFTP server through the Baskt UI?