CARTO is more focused on backend pipelines and large-scale data (where everything needs to be tiled before it can be visualized), while Kepler is a great last-mile visualization tool. It probably makes more sense for enterprises that scale beyond what Kepler can do.
That said, credit where it’s due - their engineering team is a super active contributor to the deck.gl framework powering kepler.gl.
That said, credit where it’s due - their engineering team is a super active contributor to the deck.gl framework powering kepler.gl.