Take what you need
SPFN ships as composable packages, not a monolith. @spfn/core is the only
required piece; everything else is opt-in. Each package's documentation is
served here, straight from the repo — the same READMEs maintained alongside
the code.
Framework
| Package |
What it does |
@spfn/core |
Server, routing, database, codegen — the kernel every app uses |
spfn (CLI) |
create, init, codegen, dev workflow |
@spfn/migrate |
Transactional, code-based data migrations with a run-once ledger |
@spfn/mcp |
One MCP contract over authenticated Streamable HTTP or a local stdio bridge |
Batteries
| Package |
What it does |
@spfn/auth |
Sessions, OAuth providers, RBAC, invitations |
@spfn/storage |
Object storage for S3-compatible services, GCS, and local files |
@spfn/notification |
Email and messaging with pluggable providers |
@spfn/monitor |
Error tracking, persisted logs, and an admin dashboard |
@spfn/cms |
Content models and admin endpoints |
@spfn/workflow |
Lightweight pipeline and step orchestration |
@spfn/i18n |
Translation catalogs, interpolation, fallbacks, and React context |
Serving
| Package |
What it does |
@spfn/pages |
Serve a website from a repo — this site runs on it |
@spfn/pages-next |
Next.js integration: layouts, catch-all helpers, static export sync |
Versioning
Packages currently ship as alpha or beta prereleases (0.x.y-alpha.N /
0.x.y-beta.N). APIs can move between prereleases; release notes will land on
this site when they start shipping.