3 ms·

Thanks for responding. That makes it more salient. I see this as useful for cases where there is a niche need for some SaaS, but not enough demand to necessitat

Thanks for responding. That makes it more salient. I see this as useful for cases where there is a niche need for some SaaS, but not enough demand to necessitate a full-blown startup around it requiring multiple developer salaries? I'd just softly suggest to make sure that the problem you're solving doesn't get lost in the marketing. Often I'll visit the sites of startups and not be able to quickly discern what it is they're doing, even after clicking their "about" page. Don't feel like it's repetitive to keep explaining this when most people aren't your customers yet.

doppenhe 10y ago
I appreciate you taking the time to give us feedback. At the core of Algorithmia we look to operationalize for scale. You can develop your own algorithms and use us as your infrastructure never having to worry about spinning up a machine again. You can mix and match work from others regardless of language. You can open source it all and make it available (caveat we still charge for running on our infrastructure) or you can make it closed source and share with no one. The algorithm developer is always in control, we just look to facilitate actually using these algorithms, libraries, ml models and functions vs reading about it in an academic paper or trying to resolve every dependency under the sun. The truth is that getting things up and running can take hours to days and Algorithmia turns it into seconds. This is how we beleive we are liberating knowledge... By making applicable and usable to developers in their day to day.