head to head · open source

NocoBase vs Rivet

NocoBase has 24,256 GitHub stars, 2,876 forks, 307 open issues and last shipped yesterday. Rivet has 6,144 stars, 249 forks, 269 open issues and last shipped yesterday. NocoBase leads on adoption by 295% (24,256 vs 6,144 stars). NocoBase is written in TypeScript under a custom or non-standard licence; Rivet is written in Rust under Apache-2.0. NocoBase has attracted 12% as many forks as stars, Rivet 4%. Rivet 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.

NocoBase ★ 24K Rivet ★ 6.1K category Developer Tools

← all 8884 open source comparisons

Side by side

NocoBase Rivet
GitHub stars ★ 24K ★ 6.1K
License Custom / other Apache-2.0
Written in TypeScript Rust
Last push 2026-09-17 2026-09-17
Forks ⑂ 2.9K ⑂ 249
Self-hosting Yes Yes
Data ownership Your server Your server

pick NocoBase if

  • You weight community size — 24K 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 NocoBase profile →

pick Rivet if

  • You want the Rivet 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 Rivet fits your workflow better

full Rivet profile →

About NocoBase

NocoBase is an open source AI plus no code platform, written in TypeScript, for teams and non developers who need to build and run internal business systems such as admin dashboards, CRM, and ERP tooling.

read the full NocoBase overview →

About Rivet

Rivet is an open source runtime for building stateful backends around in memory actors. It is written in Rust and released under the Apache 2.0 license, and it lives in the developer tools ecosystem for build and deployment, with topics that place it alongside Cloudflare Durable Objects, FoundationDB, serverless platforms, and realtime multiplayer infrastructure. An actor in Rivet is a long running, lightweight process that holds its state in memory while persisting that state automatically, so a developer creates one actor per agent, per session, or per user rather than managing a separate service for each.…

read the full Rivet overview →

More in Developer Tools

OpenCode ★ 208K Langflow ★ 155K Supabase ★ 110K pi ★ 107K fastapi ★ 102K Neovim ★ 102K

Related comparisons

vite vs webpack vite vs appwrite vite vs parcel webpack vs appwrite vite vs harness vite vs dokku vite vs turborepo vite vs nx opencode vs pi opencode vs openhands opencode vs paperclip opencode vs orca opencode vs cline opencode vs aider opencode vs continue opencode vs tabby opencode vs neovim opencode vs zed langflow vs neovim langflow vs zed opencode vs kilocode opencode vs codeedit neovim vs zed langflow vs kilocode

More Build & Deployment projects

Compare either of these against the rest of the Build & Deployment field.

NocoBase vs vite NocoBase vs webpack NocoBase vs Appwrite NocoBase vs parcel NocoBase vs Harness NocoBase vs Dokku NocoBase vs turborepo NocoBase vs nx NocoBase vs gradle NocoBase vs rspack NocoBase vs devbox NocoBase vs xmake

Frequently asked questions

Is NocoBase or Rivet more popular?

NocoBase has 24,256 GitHub stars and Rivet has 6,144. NocoBase has the larger community by that measure.

Are NocoBase and Rivet free?

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

What is the difference between NocoBase and Rivet?

NocoBase is written in TypeScript and Rivet 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, NocoBase or Rivet?

Choose NocoBase if you want the larger community (24,256 stars) or its Custom / other licence terms. Choose Rivet if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.