Community Data

Community Data is an open database of people and companies, initially centered on the startup ecosystem. It is best suited to developers and other data users who want structured records they can query or extend. Its open API and contribution model are useful strengths, but contributors should weigh the automatic merging of listed owners’ pull requests carefully.

Overview

The project describes a collection of more than 1 million people and companies, with company profiles and funding data. Records are maintained in an open-source repository, and the public GraphQL API provides a way to query them. That makes Community Data a data layer for applications and analysis rather than a packaged research product with a finished workflow.

Its focus on shared, extensible data can suit builders who want to contribute improvements as well as consume records. The trade-off is that using the API or repository is more natural for technically capable users than for readers seeking a conventional searchable directory.

Key features

Structured records and validation

JSON documents follow schemas covering people, companies, locations, sectors, funding stages and curated collections. Each repository commit is checked against the relevant JSON Schema, and a commit with invalid documents is rejected. This enforces consistent structure, but schema validation alone does not establish whether information is accurate or complete.

API and contribution paths

The public GraphQL API lets developers query the records and build custom applications. Anyone can contribute by creating or editing a JSON file in the repository, and the project invites developers to list apps built on the API in its apps repository. This flexibility favors teams prepared to build their own tools; it is less suitable for users who need a ready-made research interface.

Editor, enhancers and ownership

The proof-of-concept Next.js editor uses the GitHub API, so contributors authenticate with GitHub accounts. Enhancer scripts can draw on public APIs or websites, structure information to match the canonical schemas and import it into the repository. These options support community contributions and programmatic enrichment, but require comfort with GitHub or scripting.

Person records may use Twitter, LinkedIn or a personal website as proof sources. A contributor can establish ownership through a core disambiguation attribute, after which the verification service records their GitHub username. Pull requests from listed owners are automatically merged without review. That streamlines changes by owners, but means this workflow does not provide review before those changes are merged.

Governance and license

Schema changes are proposed through pull requests and reviewed by core contributors during monthly governance calls. The project states that it uses the MIT License, copyright 2025. This gives developers a clear stated license and a defined route for schema proposals, while schema governance remains tied to the core contributor process.

Pricing

Community Data is free: the Community Data plan costs nothing and includes the open-source database and public GraphQL API. There are no paid tiers or stated seat or quota limits to weigh against the free plan. Its cost advantage comes with a different kind of commitment: users seeking a finished research product will need to build around the data themselves.

Platforms

Community Data is available on the web and through its API. API access suits applications and data workflows; the web presence supports interaction with the project, including its GitHub-based editor. The editor is explicitly a proof of concept, so it should not be mistaken for a full-featured data-management product.

Who it's for

Choose Community Data if you are building an application, querying startup ecosystem records, or willing to contribute structured data through GitHub. Its schemas and GraphQL access make it relevant to developers who want a shared data source they can extend. Look elsewhere if your priority is a turnkey company research platform or a contributor workflow with review of every owner-submitted change.

Pros and cons

• Open database and API: Free access to structured records and a public GraphQL API gives builders a starting point for custom applications.
• Schema-checked contributions: Commits with invalid documents are rejected, helping maintain consistent record structure.
• Multiple contribution routes: Contributors can edit JSON directly, use the proof-of-concept editor, or build enhancer scripts around public sources.
• Owner changes bypass review: Pull requests from listed owners are automatically merged, which may be a concern for teams that expect review before changes land.
• Not a turnkey research workflow: The product is a database and API, so users who want a finished interface or analysis workflow may need another tool.

Alternatives

For a broader set of startup data options, browse the Startup Databases category.

• Tracxn is worth considering if you want a freemium research product with a free trial; its Lite plan has usage limits, while Premium offers unrestricted access, taxonomy, custom reports and analysis.
• FlareSight may fit users who want a web and API directory with search filters and company profiles; its free plan caps profile views at five per day and includes one view-only watchlist.
• Discover Startups is an option for founders seeking a free, dedicated startup profile visible to investors and media.
• Selva may suit readers who want startup identity, descriptions and rolled-up totals for free, with additional round and portfolio information through a free account.
• StartupDB is a free alternative with a database, MCP server and REST API, no account or API key, and a limit of 120 requests per minute per IP with no daily cap.
• Dealflow.Africa is another free option, with startup access offered free forever and no credit card required.
• FirstGlance is a free alternative available on Android, iOS and the web.
• The Venture Codex is a free alternative for readers considering another no-cost option.

Verdict

Community Data is a strong fit for developers and data users who want a free, extensible startup ecosystem dataset with GraphQL access and a route to contribute. Its main reason to choose it is the combination of open records, structured schemas and API access; its main reason to look elsewhere is the need for a polished research workflow or review of owner-submitted changes.