Category Archives: Venture Capital

littleBits Raises An Additional $11.1M in Series B Funding

littleBits, the New York City based open hardware startup, has raised a $11.M Series B round of funding led by True Ventures (@trueventures) and Foundry Group (@foundrygroup) and includes new investors Two Sigma Ventures (who had also just led an $11.5M investment in Rethink Robotics, and is invested into Floored (@Floored), who I have blogged about before) and Vegas Tech Fund (@VegasTechFund).   Returning investors Khosla Ventures (@vkhosla), Mena Ventures, Neoteny Labs, O’Reilly AlphaTech (@OATV), Lerer Ventures (also invested into Floored) (@lererventures) and new and returning angel investors also participated.  littleBits had previously raised $3.65M in Series A funding, and $850K in seed funding, bringing its total raised to date to over $15M.

littleBits mission is to “turn everyone into an inventor by making electronics accessible as a material.” littleBits makes “Bits modules” that snap together magnetically to make it easy for children and adults to build simple circuits and inventive projects in seconds. littleBits, and its CEO Ayah Bdeir (@ayahbdeir) have won numerous awards and are viewed as leaders in the maker movement.

I previously profiled littleBits in my two part blog series in November and December 2012 looking examining the intersection of the makers movement with the “Minecraft generation” in my own house – as I try to get my own kids to focus more on the worlds of atoms instead of bits.  You can find those two posts here: (1) http://3dsolver.com/the-makers-movement-intersects-with-the-minecraft-generation/  and (2) http://3dsolver.com/the-maker-in-the-minecraft-generation-part-duex/

Congratulations to littleBits!

CrunchBase: Using Crowdsourced Data for Commercial Purposes

For those of you who don’t know about CrunchBase (@crunchbase), it is a crowdsourced database of information about startups, people and investors.  Crunchbase describes themselves as “the free database of technology companies, people, and investors that anyone can edit. Our mission is to make information about the startup world available to everyone and maintainable by anyone.”  AOL acquired Crunchbase and TechCrunch in 2010 from Michael Arrington.

Crunchbase has been very successful in sourcing data, and have established strong relationships with many of the leading venture capital firms who regularly share data about their portfolio companies (fundraising, people, etc.).  CrunchBase has even developed an Excel Data Exporter, in addition to its API access, to allow for the broader distribution of the information contained in its databases.

The current Crunchbase Terms of Service, Privacy Policy,and Licensing Policy govern the use and access of Crunchbase data.

As of the date of this blog, the Licensing Policy provides that:

We permit anyone to republish our content in accordance with this licensing policy.

We provide CrunchBase’s content under the Creative Commons Attribution License [CC-BY]. Our content includes structured data, overviews and media files associated with companies and people. Our schema, and documentation are also offered under the Creative Commons license.

We ask that API users link back to CrunchBase from any pages that use CrunchBase data. We want to make sure that everyone is able to find the source of the content to keep the service up-to-date and accurate.

This Licensing Policy may be updated from time to time as our services change and grow. If you have any questions about this policy please contact us at licensing@crunchbase.com.

CrunchBase provides a specific licensing contract for services that charge for the use of their data. Contact licensing@crunchbase.com

The CrunchBase Terms of Service provide further restrictions on how the API maybe used:

We provide access to portions of the Site and Service through an API thereby enabling people to build applications on top of the CrunchBase platform. For purposes of this Terms of Service, any use of the API constitutes use of the Site and Service. You agree only to use the API as outlined in the documentation provided by us on the Site.

 On any Web page or Application where you display CrunchBase company or people results, each page must include a hypertext link to the appropriate company or person profile Web page on CrunchBase.com. Additional CrunchBase Branding Requirements can be found on the following Web page: http://info.crunchbase.com/docs/licensing-policy/. CrunchBase may grant exceptions on a case-by-case basis. Contact us atlicensing@crunchbase.com for special branding requests, which must be approved in advance in writing.

CrunchBase will utilize commercially reasonable efforts to provide the CrunchBase API on a 24/7 basis but it shall not be responsible for any disruption, regardless of length. Furthermore, CrunchBase shall not be liable for losses or damages you may incur due to any errors or omissions in any CrunchBase Content, or due to your inability to access data due to disruption of the CrunchBase API.

CrunchBase reserves the right to continually review and evaluate all uses of the API, including those that appear more competitive than complementary in nature.

CrunchBase provides a specific licensing contract for services that charge for the use of their data. Contact licensing@crunchbase.com

CrunchBase reserves the right in its sole discretion (for any reason or for no reason) and at anytime without notice to You to change, suspend or discontinue the CrunchBase API and/or suspend or terminate your rights under these General Terms of Service to access, use and/or display the CrunchBase API, Brand Features and any CrunchBase content.

I previously reviewed various licensing schemes, including the Creative Commons scheme, in a two part earlier blog series The Call for a Harmonized Community License for 3D Content where I proposed a harmonized “community” type license for content which could be produced on 3D printers (arguing that the existing license types do not “fit” for content which can mix copyright, patent, trade dress and other rights)

For those of you who are not aware, the CC-BY license type is a very broad license grant – providing for the “maximum dissimentation of licensed materials”.  You can find the existing CC license types here and specifically the summary of CC-BY license.

Crunchbase was careful to make clear that uploaded material which they link or provide along with the company information might be licensed differently (e.g. not under the CC-BY license) and specifically made clear that:

The graphical layout of the CrunchBase website and other elements of the Site, Content or Service not described above are the copyright of CrunchBase, and may not be reproduced without permission.

 

Enter Pro Populi and People+

Pro Populi, a small three person startup, has been developing applications utilizing the CrunchBase dataset, one app called People+.  Pro Populi has apparently been accessing the CrunchBase data (originally via the API, but also through other means apparently) to populate their own database of content and then accessing that content (and other content) from their applications.

Wired (@Wired) reporter David Kravets (@dmkravets) broke the story on November 5th in a story titled AOL Smacks Startup for Using CrunchBase Content It Gave Away.  If you click through the link to the original Wired article, you can review some of the correspondence gathered by David Kravets in support of the story.

Pro Populi was served with a cease and desist letter from AOL (the parent company of CrunchBase).  Quoting from the Wired article, an AOL Assistant General Counsel apparently sent the following in an email to the Pro Populi CEO after a meeting with the President of CrunchBase last Friday:

On the chance that you may have misinterpreted Matt’s willingness to discuss the matter with you last week, and our reference to this as a ‘request,’ let me make clear, in more formal language, that we demand that People+ immediately cease and desist from its current violation and infringement of AOL’s/TechCrunch’s proprietary rights and other rights to CrunchBase, by removing the CrunchBase content from your People+ product and by ceasing any other use of CrunchBase-provided content.

But if CrunchBase didn’t want to allow others to use the data, why does it license its content under the CC-SA scheme?

Hopefully CrunchBase and Pro Populi can come to an agreement which works for both of them and their interests.

While CrunchBase can likely legitimately claim to restrict access to their content via their API (licensed separately, not covered by the CC-SA scheme, and with separate terms), once content covered by the CC-SA license has been accessed and copied in a manner consistent with CC-SA, can CrunchBase assert rights to “get it back?”  That seems to be an incredibly difficult road to hoe, and inconsistent with the very broad terms of the CC-SA license grant.  Worse yet, according to the Wired article, the General Counsel of the Creative Commons Corporation doesn’t think so.  The Electronic Frontier Foundation represents Pro Populi.

Oops.

CrunchBase could have stayed within the CC license scheme and chosen a different CC license type for the underlying data – including one which specifically prohibits the use of the content for commercial purposes, which prohibits the creation of derivative works, and which requires specific attribution to them.  That license type is CC BY-NC-ND.  On a case by case basis they could have authorized/waived the restrictions contained in the license.  CrunchBase could have also changed the license grant for content accessed via the API.   This is solvable.

For an interesting view of this dispute from TechCrunch (a sister company to CrunchBase), see their take on the dispute.

 

Impact On Other “Hybrid” Commercial Use of Crowdsourced Data?

While CrunchBase and Pro Populi resolve their dispute, I am most interested in thinking about how this potentially impacts other crowdsourced data platforms and the applications built on top of them.   It is an interesting dilemma and question – how can/should crowdsourced data platforms be able to commercially benefit from their efforts – including restricting other potential competitors from a copying of data for their own purposes – commercial or otherwise?  Sourcing, filtering, vetting, editing, organizing, etc. hundreds, thousands and millions of data points is a complex undertaking.  It takes time, effort, people and ultimately money.  Unless that vetting is also done from a crowdsourced perspective (or mostly so – like the Wikipedia model), allowing potential competitors (commercial or otherwise) to copy that structured content is a potential death knell.  In that instance, openness needs to be balanced against a commercial purpose.

CrunchBase President Matt Kaufmann blogged about the CrunchBase dispute with Pro Populi and the EFF.   He essentially acknowledges the challenge of openness in the context of trying to build a commercial business – but re-affirms his belief that CrunchBase thought they restricted the use of their data (via the API or otherwise) for commercial purposes under their current licensing terms.

[T]o invest in CrunchBase’s constant improvement requires building a business around CrunchBase in a way that successfully takes into account our terms of service and our openness. We are confident that this is possible, and that’s what we are on the path to figuring out.

This is of course the challenge – adding enough value in the stack above the “open” content that can be commercialized.   As an example, take a look at MapBox – MapBox is a cloud-based platform which allows for developers to embed geo rich content into their web and mobile offerings.  They recently took $10M from Foundry Group, and I blogged about that investment – MapBox, Geo Software Platform, Maps $10M from Foundry Group.

MapBox relies on data sourced from OpenStreetMap, the “free wiki world map.”    OpenStreetMap licenses its content in two ways – the underlying data is licensed as open data under the Open Data Commons Open Database License (ODbL) while the cartography and documentation are licensed under the CC BY-SA license, the same license selected by CrunchBase).  BTW, Kevin Scofield likes the MapBox interface too.

It would be a difficult commercial business model indeed for MapBox to go through the effort of building an infrastructure to help source, collect and organize all kinds of mapping data, which was open for other uses, as well as building an application layer on top of it.   MapBox instead focuses on creating a great platform layer on top of the otherwise “open” content (others are free to do so as well).  This model works because there is enough community interest to support an undertaking like OpenStreetMap to begin with.  Can the same be said for the data underlying CrunchBase?

MapBox, Geo Software Platform, Maps $10M from Foundry Group

It is great to see continuing venture capital and public market interest in areas such as data acquisition, unmanned aerial systems, manufacturing, AEC and GIS solutions providers.

MapBox (@MapBox) announced yesterday that it had taken a Series A investment of $10M from Foundry Group (@FoundryGroup).  After three years of bootstrapping the MapBox business, in the words of Eric Gundersen (@ericg), funding lets us plan for years of building the future of geo software, from the ground up.

MapBox is a cloud-based platform which allows for developers to embed geo rich content into their web and mobile offerings.  MapBox sources its mapping data from OpenStreetMap, keeping its operating costs low and without a tie to proprietary back end mapping databases.   It will be interesting to see how MapBox navigates the GIS/Geo Software playing field over the coming years – but more developer choices, relying on crowd-sourced mapping data, could be quite transformational indeed.

Foundry Group continues its string of investments in the technical solutions space.  They were part of a team which invested $30M into Chris Anderson’s (@chr1sa) unmanned aerial systems company 3D Robotics (@3DRobotics) a few weeks ago, which I blogged about here and were also invested into Makerbot (@Makerbot), which was recently acquired by the 3D printing company Stratasys (@Stratasys) (in mid-August 2013) for $403M (+up to $201M in earn-outs).  Seth Levine (@sether) explained some of Foundry Group’s rationale for the MapBox investment here.

Foundry Group is currently also invested into Occipital (@Occipital) which has recently developed a 3D capture device which connects to an iPad, called the Structure Sensor.  Occipital currently has a KickStarter campaign going for the Structure Sensor, and as of today they are only a few thousand dollars shy of the $1M mark. In June 2013 Occipital acquired ManCTL, adding a strong team to an already deep computer vision bench, but in this case on that had the chops to do real time 3D scene reconstruction from PrimeSense powered (a/k/a the Microsoft Kinect) devices.  Foundry Group put $8M into Occipital in August of 2011.

I am very excited to ultimately see what comes from both MapBox and Occipital!

It will be interesting to see whether/if Andreessen Horowitz (@a16z) looks for a big data, geo centric sector investment as well.