Google Maps Pricing Sends Real Estate Site to Open Source

Adam DuVander
Jan. 11 2012, 03:10PM EST

In October Google announced pricing for its popular Google Maps API. Though most sites won't hit the free limits, those with a lot of traffic may be scrambling for a solution. That was the case for a New York real estate service, which discovered their bill would be $200,000 - $300,000 per year.

StreetEasy's Sebastian Delmont wrote about the company's experience in a Google Plus post:

25,000 free map views per day, and $4 per CPM (1,000 views) beyond that. On Christmas day, when everybody was opening their presents, we did ten times that. On a good day, we do 600K-700K pageviews.

We did the math and came up with numbers that reminded me of Oracle licensing in 1999. Six, seven, eight hundred thousand dollars. We met with Google salespeople, expecting to negotiate better terms, and they were nice, and they offered us discounts, but only to about half of what we've calculated.

In our opinion, their price was off by an order of magnitude.

The solution for StreetEasy was to go to open source tools, something that is becoming more common. Rolling your own mapping setup is getting much easier and gives a lot of flexibility in displaying maps. It's still far from being as easy as mapping APIs, but when there's a tradeoff like this, the development time will often pencil out.

Geo apps are still a hairy area where I expect most will want to build off someone else's expertise. And there are still many options, including the 25 JavaScript mapping APIs listed in our directory.

Adam DuVander -- Adam heads developer relations at Orchestrate, a database-as-a-service company. He's spent many years analyzing APIs and developer tools. Previously he worked at SendGrid, edited ProgrammableWeb and wrote for Wired and Webmonkey. Adam is also the author of mapping API cookbook Map Scripting 101.

Comments

Comments(10)

mike

hmmm...being a developer for a software service company, I wonder if they really did the math for going open source. I often hear about some of our potential customers "knowing a guy" who can write the app for them or deciding they can hire and do it in house, but it would be most likely a year before they were comparable in feature set to us, and by then we will have continued to innovate. So when you look at it that way, we are usually cheaper than hiring a dedicated dev staff.

I'm not saying it was a good or bad idea, but people often forget how much a good full time developer costs in terms of salary and benefits. You might get a good head start with open source tools, but someone has to maintain the code and update the code with new features.

[...] had 73 new APIs combined to a API directory including a payments service, online training platform, New York genuine estate hunt and information, amicable analytics platform, charity debate tracking use and grill and food data. In offer we [...]

[...] had 73 new APIs added to our API directory including a payments service, online learning platform, New York real estate search and information, social analytics platform, marketing campaign tracking service and restaurant and food data. In [...]

interesting post for a case study. 25K calls/day for a city specific real estate site is large. Perhaps the landing page showing map automatically is a contributor to the volume. Nevertheless good story.

See some hypotheticals here: ellanti.wordpress.com. The assumptions here probably don't reflect specific cases like streeteasy.

[...] While OpenStreetMap isn’t perfect, and there is still a lot of work to be done, it has come a long way toward creating an atlas of the entire world. Foursquare acknowledged that one of the reasons they chose to join the OpenStreetMap community is they’ve seen an increasing number of companies migrating from Google Maps. [...]