What's the difference between open source CartoDB version vs the paid one?

this one the open source: https://github.com/CartoDB/cartodb

and this one the "paid" version: https://carto.com/

i don't understand the advantage of the paid version beside i don't need to setup the server and carto myself.

also, if i use the open source version, which i need to setup it to my own server, is there any disadvantage to it (or any security problem, or will i get "limited" version or something) ?

  • hi team can you please help us by telling how to connect carto with redshift please help us
    – bhav
    Sep 26, 2018 at 10:43
  • Dear @bhav, please ask it as a new question through GIS SE Ask a Question.
    – Taras
    Sep 26, 2018 at 11:08
  • If you have a new question, please ask it by clicking the Ask Question button. Include a link to this question if it helps provide context. - From Review
    – BERA
    Sep 26, 2018 at 13:00

1 Answer 1


DISCLAIMER: I work at CARTO as Support Team manager and Solutions Engineer

CARTO Open Source is equal in functionality to an Enterprise paid account, but apart from having to install (and more important, maintain) your own installation, there are differences in a few services.

  • Routing, geocoding, and any other Location Based Service on a paid account come from HERE. You should have to set up your own HERE (or very soon Mapbox) credentials to get the same functionality.

  • Data Observatory is a separated component (shared by the full platform) that you should have to set up on your own (it's also Open Source).

  • We (CARTO team) do our best to answer here but Enterprise accounts have the support you may expect.

There may be other minor differences but I think that covers the relevant parts. In essence, carto.com tries to be the easiest and more convenient way to get access to the technology we develop in the open.


There's another relevant difference. CARTO provides separate Enterprise pricing plans for BUILDER (the UI to generate dashboards) and ENGINE (to create your own custom applications). That difference is not present in the Open Source version where you have no limitations in the use of API keys.


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.