Open-source project
serverpod/serverpod avatar
serverpod/serverpod

Serverpod: BSD-3 in the metadata, SSPL on the package that matters

Serverpod is a next-generation app and web server, explicitly built for the Flutter and Dart ecosystem.

3,336 stars389 forksDartBSD-3-Clause

At a glance

What is it?
A Dart backend for Flutter applications that generates API code by analysing your server, with an ORM, migrations, caching, streaming and scheduling built in. The recorded licence is BSD-3 while the licence section puts the main serverpod package under SSPL, versions are pinned in four plain files at the repository root, and the built-in web server is the one feature marked experimental.
Who is it for?
Serverpod suits a Flutter team that wants a real backend, code generation and a database in one framework rather than assembled from separate services, and the parts it replaces are named plainly: cron jobs, a logging pipeline, a cache and a file upload service. Two things to settle before committing.
Can I use it commercially?
Yes. BSD-3-Clause is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 1 day ago.
What is it written in?
Mainly Dart, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • serverpod/serverpod3,336 ★ · +42
Star history
Repository2026-09-242026-11-15
serverpod/serverpod3.3k3.3k

42 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The recorded licence is BSD-3 and the main package is SSPL

The licence section splits the project in two. All Serverpod packages are licensed under BSD-3, except the main serverpod package, which uses the SSPL licence. The practical rule is then spelled out: you can use any of the client packages in your app without limitation, and you can host a Serverpod server without limitation as long as you do not offer Serverpod as a cloud service to third parties, which the file notes is typically only relevant for cloud service providers.

The repository's own recorded licence field reads BSD-3-Clause, so the permissive answer and the copyleft answer are both present in the same repository without either being marked as the exception.

A file called PUBLISHABLE_PACKAGES at the top level is where the package list lives, which is where you would find out which of your dependencies falls on which side. The same paragraph also misspells the project name once, as Severpod.

Four version files at the root, and recent tags for bundled Postgres

Versions are not read from the manifest alone. Four plain files sit at the top of the repository: SERVERPOD_VERSION, DART_VERSION, FLUTTER_VERSION and INSIGHTS_DEVTOOLS_VERSION. The framework is pinned against a Dart version, a Flutter version and a devtools version as separate inputs, which is what keeps the three moving parts aligned.

The tags tell a narrower story. The two most recent releases are both for the embedded PostgreSQL bundle, at version 16.13.0 and a revision of it. No framework release appears alongside them, so a tag list from this window says more about the bundled database than about the server itself.

CHANGELOG.md is in the tree, so the history of the framework itself is written down somewhere even when the tags are not the place to read it.

Code generation and the ORM are one path, not two features

The generation claim is that Serverpod analyses your server and produces both the model and the client-side code, so calling a remote endpoint reads like a local method call.

Underneath that sits the database layer, described as an ORM where queries use native Dart types and null-safety, with a straight path from statically checked code to the database. Migrations are a separate capability in the same list: a complete system for applying and versioning changes as the project evolves.

So the three features interlock rather than standing alone. A model definition is what the generator reads, the ORM is what executes against it, and migrations are what carry a changed model into a database that already has data. The logging capability sits alongside them, with exceptions and slow database queries surfaced in a user interface rather than in log files to grep.

Caching and streaming both assume more than one server

Two capabilities are written with a cluster in mind rather than a single process.

Caching is described as a high-performance distributed cache built in, with any serializable object cached locally on the server or through Redis when the same cache has to be shared across a cluster. The stated purpose is cutting database cost by not saving data permanently when it is not needed.

Data streaming passes serialized objects through authenticated sockets, pushes messages from the server for real-time use, and supports sending messages across a cluster of servers, with games and chat named as the fitting cases. Authentication is part of the channel rather than something applied afterwards, since the sockets are described as authenticated.

Task scheduling is framed the same way, as a replacement for cron jobs: call a method at a future time or after a delay, with the calls persisting across a server restart.

Four sign-in providers and three places to put a file

Authentication is offered either through social logins or by building your own, and the file names the currently supported set: Google, Apple, Firebase, and email.

File uploads have three destinations, which is the more consequential choice. A file can go straight to Google Cloud Storage, to S3, or into your database. Storing uploads in the database is convenient for a small app and moves the same bytes through the same connection as everything else, so the trade is between simplicity and the cost of serving large objects out of the database tier.

Health checks close the list of infrastructure concerns, covering the database and the external services in use, with custom checks and notification when something fails.

The built-in web server is the one part marked experimental

Serverpod ships a web server, and the stated uses are sharing data for applications that need both an app and traditional web pages, creating webhooks, and generating custom REST APIs to talk to third-party services.

The same paragraph that describes those uses also says the web server is still experimental and that work on it is ongoing. That qualifier sits in the middle of the capability list rather than in a caveats section, which is where a reader is most apt to skim past it.

It matters because the webhooks and third-party REST cases are exactly the ones where an application depends on an externally reachable endpoint, and that is the feature carrying the warning.

Terraform scripts for two clouds, and a monorepo with four version files

Deployment is described as easy, with Terraform scripts for Google Cloud Platform and AWS, and other platforms named as still in progress with a link to the contribution guide.

The tree is a monorepo with a lot of top-level directories: packages, modules, integrations, templates, examples, docs, tools, util, misc, docker and tests. Documentation for contributors is spread across several files rather than one, with CONTRIBUTING.md, TESTING.md, PUBLISH.md, CLA.md and CODE_OF_CONDUCT.md all present.

Among the examples are directories named auth, legacy and middleware, so a legacy path is kept alongside current ones. A separate README_subpackage.md sits next to the main README, which is what a package inside the monorepo would point its own readers at.

Editorial conclusion

Serverpod suits a Flutter team that wants a real backend, code generation and a database in one framework rather than assembled from separate services, and the parts it replaces are named plainly: cron jobs, a logging pipeline, a cache and a file upload service. Two things to settle before committing. The licence is stated two different ways, BSD-3 for the packages and SSPL for the main one, and the file that decides which is which is a list called PUBLISHABLE_PACKAGES, so read it before you redistribute anything. And check which feature you actually need against the experimental label, since the built-in web server is the one part the project itself flags as still in progress, while the Terraform scripts cover Google Cloud and AWS only.

Frequently asked questions

What is serverpod?

It is an app and web server built for the Flutter community, where you write server-side code in Dart and it automatically generates your APIs and hooks up your database. It is open source and you can host the server anywhere.

is serverpod free

The packages are BSD-3 except the main serverpod package, which uses SSPL. You can use any client package in your app without limitation, and host a Serverpod server without limitation as long as you do not offer it as a cloud service to third parties.

is serverpod production ready

The repository makes no production-readiness claim. It describes itself as a complete, competent backend for Flutter, and it flags exactly one part as still experimental: the built-in web server.

serverpod vs firebase

The file runs no comparison and names no alternative. Firebase appears only as one of the supported sign-in providers, listed alongside Google, Apple and email, and no other backend is mentioned anywhere in it.

What is the best backend framework for Dart?

That ranking is not something the repository addresses. Its own position is that it is a backend for the Flutter and Dart ecosystem which generates APIs, and it points readers to the main project page for the sales pitch rather than arguing against other frameworks.

Official sources

  1. Issues
  2. License: BSD-3-Clause
  3. README
  4. Releases
  5. serverpod/serverpod on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/serverpod-serverpod.svg)](https://hysenlabs.com/projects/serverpod-serverpod)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/serverpod-serverpod.svg)](https://hysenlabs.com/projects/serverpod-serverpod)

Was this useful?