I would add a little bit.
The uplink is a command line tool, it’s not a service.
When you generate an URL with it, it will use a hosted Tardigrade linkshare service to host this link by default.
You can run your own linkshare service to be independent of our hosted version.
The linksharing service allows you even host your own static site: [UPDATE] We've launched Linkshare short URLs and static site hosting!
You also can use many tools with a native connectors:
- Backup With Duplicati - Tardigrade
- Sync Files With Rclone - Tardigrade
- Set up FileZilla for Decentralized File Transfer - Tardigrade
- Backup With Restic - Tardigrade
- Kubernetes Backup via Velero - Tardigrade
- MongoDB Ops Manager Backup - Tardigrade
And also use a program interface with an uplink libraries and bindings:
To connect s3-compatible tools to Tardigrade you need either hosted Gateway-MT or self-hosted Tardigrade S3 Gateway. The choice is depends on your needs.
The Gateway-MT uses server-side encryption, the self-hosted Tardigrade S3 Gateway uses client-side encryption (the last is more secure).
In case of Gateway-MT you need only create an access grant and register it on Gateway-MT, it can be done via Browser in the satellite UI or via uplink CLI on your own computer (the last is more secure) and you won’t need to host or run anything yourself.
In case of Tardigrade S3 Gateway you will got more secure interface to Tardigrade, because files are encrypted before the leaving your network, unlike Gateway-MT, but with two downsides: it uses many connections to independent nodes as a native connector, i.e. uses more bandwidth (the current expansion factor is 2.7) and you need to host it yourself inside your infrastructure.
In both cases as result you will have endpoint, Access Key and Secret Key. This information is enough to connect almost any s3-compatible tool to the Tardigrade.