The AI era changed who builds software, and how. Superfunction is our answer: the architecture every full-stack product needs, shipped as packages — so the non-creative work is already done.
For building on the web — especially when you need backend features — Next.js is one of the best choices there is. Frontend and server live in one project, one dev command. That integration is a real advantage, and it is where SPFN lives. It pays off for mobile apps too: one project carries the marketing page and the app's backend together.
Transactions, connection pools, background jobs, auth. The moment an app becomes a product, simple API routes stop being enough — and the hard part was never the endpoint. It is the architecture around it.
Millions of people now build complete products with AI — many shipping their first backend.
Ask an AI for the same feature twice and you get two different shapes. Codebases drift, run by run.
The people who can hold a system together with good architecture are very few. Most projects never get one.
Every project needs login, uploads, jobs, email — and every project rebuilds them from scratch, differently. The same problem, again.
Superfunction is an opinionated answer: one fixed vertical slice per
feature — entity, repository, route, typed client — and the modules every product needs,
shipped as @spfn/* packages. The structure is deterministic. Humans and AI
agents both know exactly where things go, and login never gets built from scratch again.
Human time — and tokens —
belong to creative problems.
That is the bet behind Superfunction. In the AI era, human attention should move up the stack: not writing another session store, but deciding what to build, for whom, and why. SPFN takes the solved problems off your desk so your time and your tokens go where they matter.