Web, app, server, fragmented frameworks, integrations, and duplicated declarations wear teams down. Akan lets one line of business code describe web, iOS, Android, server, and database surfaces together.
Configure less, repeat less, and keep business intent readable from database to UI.
Akan.js
Business code becomes the whole product
export class ProductInput extends via((field) => ({
name: field(String),
})) {}Web / App
SEO web and native-feeling client transitions.
Server / Realtime
Bun-powered HTTP and WebSocket surfaces.
Database / Validation
SQLite first, scalable, and schema validated.
Docs / Plugins
Live docs and official feature blocks.
Akan keeps decisions consistent so teams can spend more energy on business code and less on framework assembly.
Configure everything in akan.config.ts. Even when you configure nothing, the defaults keep your product moving.
Use verified code everywhere. Share domain logic without reinventing the wheel for every surface.
Akan turns business declarations into docs, APIs, queries, state, and loading behavior so repetitive work disappears.
Business schema is not only runtime code. It becomes documentation your team can inspect together.
API contracts stay close to implementation, and the generated surface can be tested as you build.
One query condition can power list, detail, and statistics reads without repeating the same plumbing.
Declare a slice once and get list loading, pagination, statistics, state, and loading behavior together.
A single business field can drive schema, validation, API contracts, fetch types, state, and UI contracts without scattering intent across the stack.
Akan supports web, iOS, Android, server, database, validation, internationalization, and official plugins as one coherent stack.
SEO-ready server-side rendering
iOS / Android client rendering
Bun HTTP / WebSocket server
SQLite first, Postgres / Redis ready
Schema validation and secure middleware
Type-safe from DB to UI
Built-in internationalization
Official plugin blocks
When a page is opened as a CSR client, pageConfig can add transition presets for list-detail flows, overlays, and context changes. It is one detail in the web/app surface, not a separate UI rewrite.
File paths, names, structures, and declarations stay consistent. Code reads like you wrote it, no matter who did.
Fewer lines mean fewer tokens, clearer intent, and updates that are easier to read, review, and ship.
export class ProductInput extends via((field) => ({
name: field(String),
})) {}Open focused flows from the bottom without leaving the CSR client.
Change context calmly when the next screen is not a deeper page.
Guide attention into the next page with a light zoom transition.
Push detail screens over lists with layered client navigation.
One page can become SEO-ready web and app-ready client screens with native-feeling transitions.
Schema changes flow into database, validation, API contracts, and generated clients without hand wiring.
Database schema changes automatically influence server, API, state management, and UI types.
State, loading, pagination, and statistics follow the domain so UI code stays predictable.
Official patterns and plugins give agents predictable blocks for upload, login, admin, chat, boards, and alerts.