5/3/2023 0 Comments Facebook flexifyThat's something we're looking to change, but at this point that's one of the biggest challenges. We provide technology to our bigger partners and those bigger partners will market Flexify.IO as part of the whole combined offering. This the reason we currently position ourselves more like a technology enabler. We can't afford to spend big dollars on purchasing expensive marketing or hiring salespeople. Speaking specifically about Flexify.IO, we are still self-funded. … They become the biggest portion of your bill and that's especially true in multi-cloud environments. Kandaurov: The first thing that prevents multi-cloud from wide adoption, and it's industry-wide, is traffic fees, especially egress traffic fees. What are some challenges Flexify.IO has faced in these early years? We realized just adding support for cloud providers would not bring us a lot of business, it would just sit somewhere on a list.įor us, the main decision to support a cloud provider or not support a cloud provider is their willingness to actually market multi-cloud or at least our migration to that specific provider. Sometimes we reach out to providers, sometimes providers reach out to us. The last one we added in this way was OVHcloud. We perform a compatibility test and add support for this provider as a high priority. Sometimes we have a customer come to us to migrate data onto Backblaze from another provider we do not support yet. Kandaurov: We add features mostly based upon our customer requests. What determines future partnerships and compatibility? So, most of our revenue comes from one-time migrations, but it creates a market to upsell recurring features of data replication and multi-cloud storage. It's basically like an Uber that's a one-time service since it takes you from A to B, but it's actually recurring because you'll have a need to move again. We do provide this service, but what we've found with some of those customers is they actually become recurring.įirst of all, because of the first migration project they have more migration projects. We want to have recurring customers, but we also understand that at this stage of multi-cloud adoption, most enterprises just want to have a solution to move from one cloud to another. We do not change data we do not encode data. Kandaurov: If someone is using Flexify.IO, they're not locked into Flexify.IO. How do you expect customers to use Flexify.IO compared to other software-as-a-service offerings? We focused on helping companies overcome those lock-ins and be able to freely migrate data and applications between various cloud offerings. Sergey KandaurovCo-founder and CTO, Flexify.IO If someone is using Flexify.IO, they're not locked into Flexify.IO. What was the niche you saw Flexify.IO filling when you opened your doors? In this Q&A, Kandaurov outlines what made him and his co-founders consider multi-cloud storage a viable market, what sort of challenges their business faces for growth and how they see the services offered by Flexify.IO evolving. The company formed a partnership with Backblaze in early 2020 and the Flexify.IO software is now the data migration offering for Backblaze customers. Kandaurov said the company runs compatibility checks to add more clouds based upon client needs.įlexify.IO was first prototyped in 2016 by Kandaurov and his two co-founders, Sergey Smirnov and Alexey Schepetkov, with 2018 marking the software's first public release. Since then, however, Flexify.IO has expanded to support 20 different public and private cloud services such as Wasabi, Alibaba Cloud, Backblaze and Dell EMC ECS. Originally, Flexify.IO only supported the migration of object data from Amazon's S3 to Azure's Blob storage. Sergey Kandaurov, Flexify.IO co-founder and CTO, says the streamlining of APIs through Flexify.IO will allow users to take better advantage of multi-cloud environments to select the best price for storage as well as the access speeds needed for their applications, simultaneously avoiding the potential cost lock-in with the major public clouds. Users can discontinue Flexify.IO after a migration and access their data from the respective clouds they've migrated to as well. Pricing for these migrations, however, is based upon the particular cloud providers being used as well as other factors such as a cloud provider's egress traffic fees and the chosen data center location. No coding changes are needed for a user's application to swap between the APIs of multiple clouds and there is no need to migrate data off any cloud infrastructure as Flexify.IO migrates directly to the target clouds, according to the company. Instead, it allows applications or data to be stored on multiple clouds and accessed as if it were a single storage source. Flexify.IO does not store or modify customer data.
0 Comments
Leave a Reply. |