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.

I had to look this up. You are talking about Carta Maps? That's different from what this audience will think of when we read Carta but ironically your comment is the same.