avais

4 ms·

1.
by avais 6y ago
Great question, and we've seen this happening actually, when some payments-based features used in scoring, data leakage. We are not doing "hard" constraints on this, but there are 2 ways for the user to identify this: first
2.
by avais 6y ago
Not yet. I think integrations is our weak part at the moment (we support just csvs, json, SQL DBs - MySQL, MSSQL, PostgreSQL) and building custom integrations based on customers needs. We're going to extend the list of standard connect
3.
by avais 6y ago
Right now there is a possibility to integrate third-party data with custom code + API calls, but I believe we need to work on this extensively to provide easier way for this. So happy to learn if you have some specific sources in mind?
4.
by avais 6y ago
Re killer feature: I believe it's being end-to-end, provide experience for "citizen x", domain experts, rather than only ML engineers: so it's no-code data cleansing, transformation + ML layer on top of this + production
5.
by avais 6y ago
yeaaah - we've experienced corner cases problem a lot. We're covering the functionality with unit tests and based on mock data, but still validating many things manually and sometimes need to do hot-fixes :) Though, the good side
6.
by avais 6y ago
We're building templates (pre-built pipelines) for particular use cases, so that it's easy to start. We have one for credit risk specifically! In addition, some functionality tailored for Risks: binning of the variables based on i
7.
Launch HN: Datrics (YC W21) – No-Code Analytics and ML for FinTech
44 points by avais 6y ago|10 comments