Akan.js Manifesto
Why we build Akan.js
Developers should spend their lives on work that matters
Akan.js exists because modern software teams lose too much time to project boundaries, duplicated source code, framework glue, and style mismatches. We want one clear way to describe a business and let the system carry that intent across web, app-oriented clients, servers, databases, and deployment.
The problem
Too much work is not product work
A business usually needs a frontend, backend, database model, mobile surface, admin screen, deployment pipeline, test setup, and monitoring path. The intent is often the same, but each layer asks developers to repeat it in a different language.
As teams grow, style differences become another hidden tax. People spend time asking where code should live, how a feature should be named, how data should move, and why another module looks different from the one they just touched.
That time has a human cost. Developers should not waste evenings and vacations on avoidable wiring and configuration. We should do the necessary work well, then go live our lives.
Convention is a communication tool
Ruby on Rails gave the industry a powerful phrase: convention over configuration. Akan.js takes that idea seriously for both human programmers and AI coding agents.
When a workspace is shaped by shared rules, communication gets cheaper. A service, signal, document, store, and page each have a known role. You can open an unfamiliar feature and still know where to start.
For AI agents, convention is even more direct leverage. Predictable files and contracts reduce search space, lower error rates, and save tokens because the agent can infer the next shape from the existing one.
Write the business once
A page, signal, service, store, document, and deployment artifact should not each need a separate explanation of the same intent.
Reduce wiring
Framework work should make product work smaller, not ask teams to spend their best hours connecting tools together.
Make style a shared language
When every module follows a familiar shape, code written by another person or agent reads like code from your own hand.
From meta-framework to runtime
A meta-framework begins
Akan.js started by composing Nx, NestJS, Next.js, Webpack, and other proven tools into one product-oriented workspace.
Conventions tested in real apps
For four years, dozens of business applications were built and operated on top of those conventions until common service patterns became clear.
The lower framework moves into Akan
Akan.js began replacing the lower framework layers so the runtime, data layer, API surface, and developer experience could be designed as one system.
What Akan.js is trying to protect
Akan.js is not only a faster stack or a different folder rule. It is an attempt to protect developer attention. Source code should be reusable, business intent should stay unified, and product teams should not burn their lives on accidental complexity.