Actually while similar to Jev and uses the popularized architecture by Jev, Kairos uses an underlying model called Grayson trained by Finic but for Fraud. You can check it out - https://finic.ai/
There will always be projects that share the same name. You can do quick search on Github: https://github.com/search?q=kairos&type=repositories. However it does not change the significance of what each project is building and the problem they sought to solve.
Nothing is built yet. Before I spend time building it, I want the idea roasted.
LaunchPort: launch your side project and get real customers without incorporating first. You'd keep the code, IP, and customers. Infra, payments, sales/marketing and legal handled for you; you "graduate" into your own company whenever you're ready.
Do you get what this does?
Would you actually sign up?
What would stop you?
I needed to back up terabytes of Postgres RDS data to R2 without intermediate local dumps or AWS egress fees, I could not find any ideal solution, so I built this.
DuckLake is great for the lakehouse layer and it's what we use in production. But there's a gap and thats what I'm trying to address with OpenDuck. DuckLake do solve concurrent access at the lakehouse/catalog level and table management.
But the moment you need to fall back to DuckDB's own compute for things DuckLake doesn't support yet, you're back to a single .duckdb file with exclusive locking. One process writes, nobody else reads.
OpenDuck sits at a different layer. It intercepts DuckDB's file I/O and replaces it with a differential storage engine which is append-only layers with snapshot isolation.
reply