2 ms·
I like this idea a lot, and I am a potential customer — I'm developing an app that would heavily rely on complicated data analysis, and I planned to find a data
by golergka 13y ago
I like this idea a lot, and I am a potential customer — I'm developing an app that would heavily rely on complicated data analysis, and I planned to find a data scientist after completing first prototypes.
However, there's nothing at this page right now that would convince me about this service. There's no actual examples of what your technology can achieve, there's no programming API, just a promise. I understand that you're still in development, and I'm not asking for full documentation and a page of famous logos under "they use us", but at least a code snippet or something like that would make it easier to visualize.
Right now, I'm lost; my data is a lot more complicated and inter-connected then a mere spreadsheet, will you support it? How will it work? What pricing will be, and how will it be calculated? Yes, I understand that you haven't decided yet on all this things, but that's the problem: there's nothing to show except for the idea yet.
Anyway, I really hope that this service will work great, and I wish you all the luck with it.
- swatthatfly 13y agoDatacratic has been doing what you ask for a while now (disclaimer, I work for them). We do ML, audience optimization, segmentation, multivariate and nonlinear models for small clients or for some of the largest shops in the industry. But the algorithms are indeed a small problem compared to building the on-demand infrastructure, managing the dataset, and all the rest of the challenges related to managing other people's data. Trust to handle data that doesn't belong to you is earned with great difficulty, unless it comes from shady sources.
- ncvc 13y agoAll good points. The flow is simple - upload a CSV and we'll spit out serialized models, CSV of results comparing algorithms, and an HTTP endpoint where you can get predictions. To your point about being more than a flat CSV: yes that is absolutely correct. We're starting with flat but moving towards sucking in relations (automatic joins) and constructing feature vectors from that.