head to head · open source

NocoDB vs SlateDB

NocoDB has 65,408 GitHub stars, 5,131 forks, 710 open issues and last shipped yesterday. SlateDB has 3,607 stars, 330 forks, 184 open issues and last shipped yesterday. NocoDB leads on adoption by 1,713% (65,408 vs 3,607 stars). NocoDB is written in TypeScript under a custom or non-standard licence; SlateDB is written in Rust under Apache-2.0. NocoDB has attracted 8% as many forks as stars, SlateDB 9%. SlateDB 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.

NocoDB ★ 65K SlateDB ★ 3.6K category Infrastructure & Operations

← all 20902 open source comparisons

Side by side

NocoDB SlateDB
GitHub stars ★ 65K ★ 3.6K
License Custom / other Apache-2.0
Written in TypeScript Rust
Last push 2026-11-02 2026-11-02
Forks ⑂ 5.1K ⑂ 330
Self-hosting Yes Yes
Data ownership Your server Your server

pick NocoDB if

  • You weight community size — 65K stars and counting
  • You want the Custom / other license terms
  • Your stack matches TypeScript
  • You value the larger contributor base for long-term maintenance

full NocoDB profile →

pick SlateDB if

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

full SlateDB profile →

About NocoDB

NocoDB is the fastest and easiest way to build databases online. Website • Discord • Community • Twitter • Reddit • Documentation See other languages » Join Our Community Installation Docker with SQLite Docker with PG Auto upstall Auto upstall is a single command that sets up NocoDB on a server for production usage. Behind the scenes it auto generates docker compose for you. bash bash install.nocodb.com/noco.sh script can be found here in our github Other Methods Binaries are only for quick testing locally. When running locally access nocodb by visiting: For more installation methods, please refer to our docs…

read the full NocoDB overview →

About SlateDB

Introduction SlateDB is an embedded storage engine built as a log structured merge tree. Unlike traditional LSM tree storage engines, SlateDB writes data to object storage (S3, GCS, ABS, MinIO, Tigris, and so on). Leveraging object storage allows SlateDB to provide bottomless storage capacity, high durability, and easy replication. The trade off is that object storage has a higher latency and higher API cost than local disk. To mitigate high write API costs (PUTs), SlateDB batches writes. Rather than writing every put() call to object storage, MemTables are flushed periodically to object storage as a string…

read the full SlateDB overview →

More in Infrastructure & Operations

Related comparisons

More Databases projects

Compare either of these against the rest of the Databases field.

Frequently asked questions

Is NocoDB or SlateDB more popular?

NocoDB has 65,408 GitHub stars and SlateDB has 3,607. NocoDB has the larger community by that measure.

Are NocoDB and SlateDB free?

Both are open source. NocoDB has no licence declared in this registry, and SlateDB is licensed under Apache-2.0. Both are free to self-host.

What is the difference between NocoDB and SlateDB?

NocoDB is written in TypeScript and SlateDB in Rust. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, NocoDB or SlateDB?

Choose NocoDB if you want the larger community (65,408 stars) or its Custom / other licence terms. Choose SlateDB if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.