Carto (formerly CartoDB) in Brooklyn, New York offers their location intelligence solution.
N/A
Mapbox
Score 7.1 out of 10
Mid-Size Companies (51-1,000 employees)
Mapbox is the location data platform for developers building custom geospatial features into mobile, web, and on-premise applications.
$0
per month
Retool
Score 8.4 out of 10
N/A
Retool is a UI software component library presenting a fast way to build custom internal tools, from the company of the same name in San Francisco, California.
$10
per month per user
Pricing
CARTO
Mapbox
Retool
Editions & Modules
No answers on this topic
Starting Price
$0.00
Per 1000 users
Team
$10
per month per user
Business
$50
per month per user
Enterprise
Custom Quote
Offerings
Pricing Offerings
CARTO
Mapbox
Retool
Free Trial
No
Yes
Yes
Free/Freemium Version
No
Yes
Yes
Premium Consulting/Integration Services
No
Yes
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
Designed for businesses of all sizes, Mapbox is free to start building with and offers free tiers for most products. As usage grows, volume pricing is applied automatically, no negotiation necessary.
Pricing is based either on pay-as-you-go usage or negotiated sales contracts that unlock additional discounts for annual commitments.
Paid support plans are also available.
CartoDB is great for generating geographic visualizations of data where the geographies are well-defined. It would be great for analysts to develop visualizations of data with spatial elements. That being said, the software is limited if you want to do any real data munging or analysis, as it can be cumbersome to use and there isn't a great interface for actually saving the results of different manipulations (you can save it as a new file, but it's hard to do version control, etc.). I would recommend preparing the data outside of CartoDB and only using the tool for visualization once the data is well prepared.
For services that require maps and basic geo-functionality in production, Mapbox is one of the greatest choices out there. They're free, provide much more refined/modern productions compared to Google maps, and have very good support on different platforms. For services that require higher-computation products, like matrix routing, optimization, etc..., the prices can get quite high very quickly, and you should consider moving those services to an on-premise server at that point.
Works well in: Connecting directly to databases and APIs holding candidate data. Allows teams to easily drill into records from different data sources. Quick to build dashboards. It wouldn't work well without a team to actually get it set up. There is limited design/ branding, making it look very basic. Your team requires training because data can be overwritten easily. Having some knowledge with your whole team is super important, and if you work with contractors or non-tech people, this can be a huge issue.
It is amazing at allowing control of the visualizations. It takes a little bit to get used to but the combination of full SQL queries and CSS-like styling is very powerful.
The services are built on a robust stack of open source software. I was able to build a standalone instance of CartoDB relatively easily (after some research and trial and error).
Server side map rendering is key for handling large data sets. The way the images are returned makes them very easy to catch in an HTTP cache to minimize the hits to the server. The interactivity that CartoDB has built in makes this completely transparent to the end user, they can click on parts of the static images and be presented with popups or change map styles. It's a very clever implementation.
It is a good tool to use. We can perform various customisations; I always end up exploring and finding a new feature that can be used in my work somewhere. And one good thing is that is actually quite reasonable in terms of cost, with the free tier being quite adequate
One feature that made me go in favor of Mapbox was its stellar documentation. Google Maps and Bing Maps are the other alternatives I considered, but the learning curve with both of them is steeper than it is with Mapbox. Also, Mapbox Studio gives newbies a very simple, clean and easy to use environment to make and store maps online
We selected Retool because it offers the best balance of usability and power compared to alternatives like Appsmith, ToolJet, and OutSystems. It allows us to build much faster, with broad integrations and strong enterprise features like permissions and environment management. Competing tools were either too limited, required more engineering effort. Overall, retool support has been decent too.
CartoDB definitely saves a lot of time when creating visualizations. Previously, I would use different software and have to make edits manually (or just create the visualizations manually to start with). I would say that the software definitely cuts the time required to create certain visualizations by a half or two-thirds.
Mapbox is the only service that has all the products we need to release our product to the market. Without Mapbox, we would've spent far more time integrating multiple different map/geo services like Mapbox and HERE maps together.
Mapbox was sometimes expensive in the testing period, and we would've definitely moved some of the services on-premise to save money if we had the time.
Mapbox has functionality for traffic-aware routing in many countries, as well as matrix-structured routing data, which is what enables our service to function. Having all of this integrated within an API allows us to easily scale our service to multiple different cities/countries in a matter of days.
