parse-community/parse-server

Parse Server for Node.js / Express

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 59 minutes ago
Added to GitGenius on September 2nd, 2026
Created on January 28th, 2016
Open Issues & Pull Requests: 557 (+0)
GitHub issues: Enabled
Number of forks: 4,814
Total Stargazers: 21,414 (+0)
Total Subscribers: 558 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 19.5 hours
Mean response time: 114.0 days
90th percentile: 390.9 days
Tracked items: 238

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 69% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "type:question" is answered fastest, typically in about 8 hours, while "bounty:$10" waits about 3 weeks. 45% of tracked open issues have had no activity in three months. Only 3% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 144
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 872 days
Stale 30+ days: 131
Stale 90+ days: 111

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • type:feature (108)
  • type:bug (80)
  • state:released-alpha (70)
  • state:released (61)
  • type:ci (26)
  • type:question (19)
  • state:released-beta (15)
  • bounty:$10 (12)

Detailed Description

Parse Server is a backend-as-a-service platform that runs on Node.js and Express, providing a complete server implementation for building scalable applications with database abstraction and API layers.

Parse Server addresses the need for a self-hosted, open-source backend infrastructure by offering a drop-in replacement for the original Parse service. It abstracts database operations through a unified API, allowing developers to switch between MongoDB and PostgreSQL without changing application code. The platform exposes both REST and GraphQL interfaces, enabling flexible client integration patterns. It includes built-in support for file storage, user authentication, real-time notifications, and object persistence, reducing the need to build these features from scratch.

Developers should choose Parse Server when they need a self-hosted backend with minimal infrastructure complexity or when they require the flexibility to migrate between database systems. It suits teams building mobile or web applications that benefit from rapid prototyping with a pre-built backend structure. Organizations already invested in the Parse ecosystem or those migrating away from the original Parse service will find it particularly relevant. The platform's support for both REST and GraphQL APIs means teams can adopt either or both depending on their client architecture preferences.

The project maintains active development with regular updates addressing bug fixes and feature enhancements. The codebase shows consistent attention to test coverage and code quality standards. Community contributions are actively reviewed and integrated, indicating an open development process. The project sustains documentation and examples that help new users understand deployment and configuration options. Maintenance efforts extend to keeping dependencies current and addressing security concerns as they arise.