Parse Server

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

  • AWS
  • Azure
  • Google Cloud
  • DigitalOcean
  • Heroku
Customer-operated Servers / containers Open Source / Open Core

4 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Install the upstream Node.js package and configure a supported MongoDB or PostgreSQL backend; run standalone or in an Express application.

  2. Operated by

    Your team

    Customer manages Node services, database, class/object permissions, master keys, storage adapters, backups and upgrades.

Deployment boundaries by provider
  • AWS: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Parse Server cloud hosting options ↗ · Source checked 2026-11-12

  • Azure: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Parse Server cloud hosting options ↗ · Source checked 2026-11-12

  • Google Cloud: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Parse Server cloud hosting options ↗ · Source checked 2026-11-12

  • DigitalOcean: Boundary not confirmed · Customer-operated

    Provider deployment is documented, but the reviewed evidence does not establish a more specific account or service boundary.

    Parse Server cloud hosting options ↗ · Source checked 2026-11-12

  • Heroku: Customer platform workspace · Customer-operated

    Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.

    Parse Server deployment on Heroku ↗ · Source checked 2026-11-12

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodInstall the upstream Node.js package and configure a supported MongoDB or PostgreSQL backend; run standalone or in an Express application.
InfrastructureServers / containers
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.
Licensing modelOpen Source / Open Core
Apache License 2.0 for upstream Parse Server. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.
LicenseApache License 2.0 for upstream Parse Server.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

6 of 12 fields researched (50%) · 5 documented · 1 unresolved. Evidence coverage is not a feature score.

Single sign-on
AvailableEvidence and scope for Single sign-on

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.

Published application-user federation adapter, distinct from separately deployed management dashboards · Source ↗ · Official third-party authentication guide ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Security controls
DocumentedEvidence and scope for Security controls

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.

Auth-data login response advisory reviewed November 15; not an arbitrary-user disclosure or a recommendation to adopt a prerelease without compatibility review · Source ↗ · Reviewed 2026-11-15

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

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.

Upstream self-hosted deployment; not a provider support or production-readiness certification · Deployment artifact ↗ (repository default branch (moving; select matching application release)) · Reviewed 2026-11-14

Documented · Editor reviewed.

Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing

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.

Published upstream runtime/dependency scope; complete production sizing remains unconfirmed · Source ↗ · Reviewed 2026-11-20

Sources checked — unresolved · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

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.

Parse Server 8.6.123 upstream application; not a managed Parse hosting plan; software terms only, excluding infrastructure and operations · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

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.

Upstream parse-community/parse-server release record; commercial editions and deployment packages may differ · Source ↗ · Parse Server auth-data disclosure advisory ↗ · Reviewed 2026-11-15

Documented · Editor reviewed.

Show all fields (6 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.

Scope & considerations

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.

Community & 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.

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.

Compare within Backend platforms

  • Appwrite Self-HostedSelf-hosted backend services for authentication, databases, storage, functions and messaging.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    Customer-operated · Open Source / Open Core
  • Gravitee API Management Self-HostedOpen-source and commercial self-hosted API management platform with documented EKS, AKS and GKE deployment paths.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • HashiCorp Consul EnterpriseCommercial service networking, discovery and service-mesh platform deployed into customer cloud infrastructure.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • Hasura GraphQL Engine v2GraphQL API engine that exposes connected databases through permission-aware application APIs.
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • KeystoneJS (Keystone 6)Self-hosted content backend with a configurable GraphQL API and administration interface.
    • Northflank
    Customer-operated · Open Source / Open Core
  • Kong Gateway Self-ManagedOpen-source and commercial self-managed API gateway with supported AWS, Azure and Google Cloud deployment platforms.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • Medplum Self-HostedOpen-source FHIR healthcare backend, clinical application and automation platform deployed in customer cloud infrastructure.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • Red Hat OpenShift Container PlatformCommercial self-managed Kubernetes application platform installed and operated in customer cloud accounts.
    • AWS
    • Azure
    • Google Cloud
    • Alibaba Cloud
    • IBM Cloud
    Customer-operated · Commercial Only

Showing 8 of 11 other listings in Backend platforms. These products address related workflows; read their category-fit notes before comparing scope. See all of Backend platforms →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Parse Server cloud hosting options ↗ · AWS, Azure, Google Cloud, DigitalOcean

      Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

      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.

    • Parse Server deployment on Heroku ↗ · Heroku

      Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

      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.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory