Akan.js v2 is here

Version 2 is the release where Akan.js stops being a wrapper around many lower frameworks and becomes a Bun-first full-stack runtime. The goal is a more consistent developer experience: fewer moving parts, fewer duplicated assumptions, and one runtime path from local development to production builds.

One runtime: Bun

Akan.js v2 removes the split between Node-based tools and Bun-based execution. The framework, CLI, server runtime, test path, and package workflow now share the same foundation.

Framework layers move inside Akan

Instead of coordinating NestJS, Next.js, Vite, and other layers from the outside, v2 owns the lower framework path so user-facing behavior can be simpler and more consistent.

SQLite-first data

MongoDB powered v1, but v2 starts from SQLite. With WAL mode and modern deployment options, SQLite is often the most practical first database for early and mid-stage services.

Why Bun-only

A clear runtime is part of the product

Akan.js v1 operated on top of NestJS, Next.js, and Vite. That gave the project reach, but it also meant Akan had to negotiate with multiple framework lifecycles, build systems, and runtime assumptions.

In v2, we chose not to support the Node.js environment as a first-class runtime. That is a deliberate product decision. A framework that promises one way to build web, app-oriented clients, APIs, services, and data should also give teams one comfortable execution model.

Bun lets Akan own more of that experience directly: package installation, scripts, server execution, SQLite access, tests, and production artifacts can all align around the same toolchain.

What changed from v1

v1

NestJS and Next.js shaped much of the server and web experience.
Vite and Node.js ecosystem assumptions were part of the operating model.
MongoDB was the default document database choice.

v2

Bun is the required runtime and package foundation.
Akan replaces more lower framework behavior directly.
SQLite becomes the first-class local and service database path.

Why SQLite first

Akan.js v1 used MongoDB. It was flexible and familiar for document-oriented application work. But for v2, we wanted the default database to match the way many services actually begin: small team, fast iteration, local-first development, simple operations, and enough performance headroom to grow.

SQLite with WAL mode is no longer just a toy database for prototypes. For many early and mid-stage products, it can handle practical read/write workloads while keeping deployment and local development dramatically simpler.

This choice also fits Akan's philosophy. Start with the simplest reliable path, keep business code close to the product, and avoid operational complexity until the product has truly earned it.

The direction of v2

Akan.js v2 is about concentration. One runtime, one convention-driven workspace, one business definition flowing through pages, APIs, services, data, and deployable artifacts. The stack is smaller so the product surface can get bigger.