head to head · open source

parse-server vs cubefs

parse-server has 21,410 GitHub stars, 4,806 forks, 561 open issues and last shipped 7 days ago. cubefs has 5,660 stars, 714 forks, 265 open issues and last shipped 2 days ago. parse-server leads on adoption by 278% (21,410 vs 5,660 stars). parse-server is written in JavaScript under Apache-2.0; cubefs is written in Go under Apache-2.0. parse-server has attracted 22% as many forks as stars, cubefs 13%. cubefs was the more recently maintained of the two, and both are self-hostable with no licence fee.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

parse-server ★ 21K cubefs ★ 5.7K category Data & Analytics

← all 15422 open source comparisons

Side by side

parse-server cubefs
GitHub stars ★ 21K ★ 5.7K
License Apache-2.0 Apache-2.0
Written in JavaScript Go
Last push 2026-09-13 2026-09-18
Forks ⑂ 4.8K ⑂ 714
Self-hosting Yes Yes
Data ownership Your server Your server

pick parse-server if

  • You weight community size — 21K stars and counting
  • You want the Apache-2.0 license terms
  • Your stack matches JavaScript
  • You value the larger contributor base for long-term maintenance

full parse-server profile →

pick cubefs if

  • You want the cubefs feature set and don't need the biggest community
  • You prefer the Apache-2.0 license terms
  • Your stack matches Go
  • You evaluated both and cubefs fits your workflow better

full cubefs profile →

About parse-server

Parse Server is an open source backend, built for Node.js and the Express web application framework, that can be deployed to any infrastructure able to run Node.js and that serves applications written against the Parse Platform.

read the full parse-server overview →

About cubefs

CubeFS is an Apache 2.0, CNCF graduated cloud native distributed file and object storage system written in Go, built for teams that need POSIX, HDFS, S3, and REST access to a single storage layer across datacenters, private and hybrid clouds, and Kubernetes.

read the full cubefs overview →

More in Data & Analytics

Mermaid ★ 90K Crawl4AI ★ 84K Scrapling ★ 82K Apache Superset ★ 75K echarts ★ 67K scrapy ★ 64K

Related comparisons

mermaid vs clickhouse crawl4ai vs clickhouse scrapling vs clickhouse apache-superset vs clickhouse mermaid vs apache-pinot clickhouse vs duckdb crawl4ai vs apache-pinot scrapling vs apache-pinot firecrawl vs scrapy firecrawl vs crawlee browser-use vs crawl4ai crawl4ai vs scrapling crawl4ai vs scrapy scrapling vs scrapy crawl4ai vs easyspider scrapling vs easyspider godot vs pixijs mermaid vs apache-superset supabase vs metabase mermaid vs echarts grafana vs apache-superset apache-superset vs echarts mermaid vs metabase mermaid vs pixijs

More Data Warehousing & Processing projects

Compare either of these against the rest of the Data Warehousing & Processing field.

parse-server vs ClickHouse parse-server vs seaweedfs parse-server vs rustfs parse-server vs Apache Pinot parse-server vs dlt parse-server vs mountpoint-s3 parse-server vs hue parse-server vs bigquery-utils parse-server vs bigfunctions parse-server vs arc

Frequently asked questions

Is parse-server or cubefs more popular?

parse-server has 21,410 GitHub stars and cubefs has 5,660. parse-server has the larger community by that measure.

Are parse-server and cubefs free?

Both are open source. parse-server is licensed under Apache-2.0 and cubefs under Apache-2.0. Neither carries a licence fee.

What is the difference between parse-server and cubefs?

parse-server is written in JavaScript and cubefs in Go. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, parse-server or cubefs?

Choose parse-server if you want the larger community (21,410 stars) or its Apache-2.0 licence terms. Choose cubefs if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.