Hi Tigris,
I just read your Series A article on the Tigris blog, congrats. But what does it mean for your collaboration with Fly? Currently, billing and logins flow through Fly.io, but I can imagine that this is about to change when you run on your own hardware. Could you eleborate on this a bit?
Thanks!
Hi @hakoptak
As you have read in our Series A article, with the fundraise we are investing in growing our infrastructure footprint so we can serve our users better. We continue to partner with Fly.io and there are no changes in our partnership with Fly.io whatsoever. But at the same time we have also built out our own infrastructure running on our own hardware for users that use Tigris outside of Fly.io.
Our storage endpoint t3.storage.dev is hosted on our own hardware. For example, you can see the different regions listed here: Regions | Tigris Object Storage Documentation
I would be happy to answer any further questions about this.
Best,
Ovais
Hi @ovaistariq, thanks for your clarification. Now it makes more sense why there are two storage endpoints… I clearly missed this connection. Except for the supported regions, do both endpoints have comparible characteristics regarding network and storage latency?