
# Parse Server

Node.js application backend for data APIs, users, permissions and server-side application logic.

Canonical page: https://launchinyourcloud.com/directory/parse-server/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## Parse Server

Node.js application backend for data APIs, users, permissions and server-side application logic.

- Listing: https://launchinyourcloud.com/directory/parse-server/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean, heroku
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream Parse Server.
- Licensing model: open-source
- Installation: Install the upstream Node.js package and configure a supported MongoDB or PostgreSQL backend; run standalone or in an Express application.
- Architecture: Customer-operated Node.js backend with database and selected file/push integrations
- Operations: Customer manages Node services, database, class/object permissions, master keys, storage adapters, backups and upgrades.
- Product website: https://parseplatform.org/
- Source review: 2026-11-15; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Cloud Code is code executed in the server environment, not evidence of a vendor-operated cloud dependency. External storage, push-notification providers and third-party adapters have their own boundaries and licenses. GHSA-43rg-r2xr-q686 affects Parse Server versions before 9.12.0-alpha.3: creating a user with an existing user's auth data can return protected fields and hidden auth-adapter data, including MFA secrets and recovery codes. The advisory concerns the logging-in user's own object and requires that user's auth data or an applicable session token; it is not an arbitrary-user disclosure. Requests using the master or maintenance key are unaffected. There is no known workaround; Parse Server 8 is not patched, and the first published patched version is the 9.12.0-alpha.3 prerelease.

Apache License 2.0 for upstream Parse Server. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated Node.js backend with database and selected file/push integrations. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- backend-platforms: Application backend with data APIs, user authentication, access rules and server-side Cloud Code; database and file adapters are separately configured.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.parseplatform.org/parse-server/guide/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.parseplatform.org/parse-server/guide/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.parseplatform.org/parse-server/guide/ (checked 2026-11-12). 

- digitalocean: Boundary not confirmed; Customer-operated; control plane: not-assessed. Source: https://docs.parseplatform.org/parse-server/guide/ (checked 2026-11-12). 

- heroku: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.parseplatform.org/parse-server/guide/ (checked 2026-11-12). 


### Cloud deployment evidence

- Parse Server cloud hosting options (aws, azure, gcp, digitalocean): https://docs.parseplatform.org/parse-server/guide/
  The upstream guide explicitly lists AWS, Google Cloud, Azure and DigitalOcean as hosts for the Parse Server application and provides installation guidance. This compatibility statement is separate from the DigitalOcean Spaces file adapter; select current Node.js/database versions and secure the deployed server.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Parse Server deployment on Heroku (heroku): https://docs.parseplatform.org/parse-server/guide/
  The upstream guide documents the Parse Server application on Heroku with MongoDB Atlas, including project configuration and validation. The application and database are in separate customer-controlled services; verify database network access, current runtime versions, secrets and production security.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Parse Community maintains an established public project, contributor review process and community forum. The current release stream includes November 2026 stable and LTS maintenance.

Reviewed 2026-11-10.

- Current stable and LTS releases: https://github.com/parse-community/parse-server/releases

- Community contribution process: https://github.com/parse-community/parse-server/blob/alpha/CONTRIBUTING.md

- Long-running community governance discussion: https://community.parseplatform.org/t/official-discord-server/1506

### Sources

- Official installation and runtime: https://docs.parseplatform.org/parse-server/guide/

- Upstream project and capabilities: https://github.com/parse-community/parse-server

- Current upstream license: https://raw.githubusercontent.com/parse-community/parse-server/alpha/LICENSE

- Security advisory GHSA-43rg-r2xr-q686: https://github.com/parse-community/parse-server/security/advisories/GHSA-43rg-r2xr-q686

### Licensing sources

- https://raw.githubusercontent.com/parse-community/parse-server/alpha/LICENSE

### Infrastructure sources

- https://docs.parseplatform.org/parse-server/guide/


### Buyer diligence


Research coverage: 6/12 fields (50%); 5 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Parse Server supports external application-user authentication adapters; published 8.6.123 includes a Keycloak adapter that verifies provider tokens and returned user attributes. Configure the adapter/provider and map application users and permissions. This is an app-user backend capability, not proof of administrator SSO in Parse Dashboard, and does not establish SCIM. Scope: Published application-user federation adapter, distinct from separately deployed management dashboards. Source: https://github.com/parse-community/parse-server/blob/8.6.123/src/Adapters/Auth/keycloak.js (reviewed 2026-11-20). Supporting source: Official third-party authentication guide — https://github.com/parse-community/docs/blob/gh-pages/_includes/parse-server/third-party-auth.md.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. GHSA-43rg-r2xr-q686 can expose protected fields or hidden auth-adapter data in the logging-in user object, including MFA secrets and recovery codes. The advisory affects versions before 9.12.0-alpha.3 and identifies that prerelease as patched; Parse Server 8 is unpatched and no workaround is known. It requires the user auth data or applicable session-token conditions; master/maintenance-key requests are unaffected. Scope: Auth-data login response advisory reviewed November 15; not an arbitrary-user disclosure or a recommendation to adopt a prerelease without compatibility review. Source: https://github.com/parse-community/parse-server/security/advisories/GHSA-43rg-r2xr-q686 (reviewed 2026-11-15).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official server repository documents a Node.js application/package with a separately configured database. The server, dashboard and optional adapters have separate configuration and lifecycle; they are not one cloud appliance. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://github.com/parse-community/parse-server (reviewed 2026-11-14). Deployment artifact: https://github.com/parse-community/parse-server. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Sources checked — unresolved. The published server identifies Node.js plus a supported database and configurable storage/live-query services, but not a workload-specific whole-system CPU/RAM/storage minimum. Size request/query rates, files, live subscriptions, database indexes and replication separately. A managed Parse hosting plan or tutorial allocation is not a self-hosted HA capacity guarantee. Scope: Published upstream runtime/dependency scope; complete production sizing remains unconfirmed. Source: https://github.com/parse-community/parse-server/blob/8.6.123/README.md (reviewed 2026-11-20).

- License pricing: Documented. The reviewed upstream application uses Apache License 2.0. Review the licence and bundled-component notices for your use and distribution. Hosting, databases, delivery services, commercial support and any separately licensed additions have their own costs and terms; no hosted-plan price is treated as a self-hosted quote. Scope: Parse Server 8.6.123 upstream application; not a managed Parse hosting plan; software terms only, excluding infrastructure and operations. Source: https://github.com/parse-community/parse-server/blob/8.6.123/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was 8.6.123, published 2026-11-09. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. The November 14 advisory GHSA-43rg-r2xr-q686 says Parse Server 8 is unpatched; this historical stable-release snapshot is not a secure-version recommendation. Scope: Upstream parse-community/parse-server release record; commercial editions and deployment packages may differ. Source: https://github.com/parse-community/parse-server/releases/tag/8.6.123 (reviewed 2026-11-15). Supporting source: Parse Server auth-data disclosure advisory — https://github.com/parse-community/parse-server/security/advisories/GHSA-43rg-r2xr-q686.






