A complete system from the start
Mobile, Admin, and Server share contracts. Each layer knows its responsibility and how it works with the other two.
MIT open source · Mobile + Admin + ServerBuild every side of your app as one system
Build Android, iOS, and HarmonyOS with uni-app x, run operations in React, and serve APIs with Go and PostgreSQL. Mobile, admin, and server share one contract from day one.
AppKernia core value
WHY APPKERNIA
Building an app should not begin by stitching together three starters
I kept meeting the same problem from one app project to the next: mobile frameworks, Admin templates, and server scaffolds are all abundant. But once a product needs Android, iOS, HarmonyOS, operations, permissions, files, notifications, and dependable APIs, developers are still left to bridge every seam.
That is why I started AppKernia. It is not another framework that tries to own every decision. It connects the foundation every app team rebuilds, so you can reach the problems that are unique to your product sooner.
Keep repeated work in the foundation
Security, i18n, authorization, state, and engineering become defaults, returning development time to product experience.
Maintain it with developers for the long run
Explicit contracts, stable dependencies, and evolvable structure make the project easier to understand, extend, and improve together.
ONE FOUNDATION · THREE SURFACES
One repository connects every side of the app
These are not three templates placed next to each other. Routes, identity, locale, authorization, and error codes move through one contract while each surface focuses on what it does best.
AK Mobile
A uni-app x foundation for Android, iOS, and HarmonyOS NEXT with typed networking, secure storage, static routes, and an AK UI layer.
uni-app x · UTS/UVue · VDOM · AK UI
AK Admin
An operations console built around real permissions, organizations, multi-tenancy, and safe administrative workflows.
React · Vite · TanStack · Ant Design
AK Server
A PostgreSQL-first modular Go backend with OpenAPI contracts, rotating sessions, audit, jobs, files, and notification modules.
GoFrame · pgx/sqlc · PostgreSQL · River
BUILT ON PROVEN TOOLS
One stack, with every tool doing what it does best
uni-app x connects mobile platforms, React shapes the operations experience, Go and PostgreSQL carry the business and its data, and OpenAPI keeps every surface speaking the same language.
uni-app xMobile- ReactAdmin
- TypeScriptAdmin
- ViteAdmin
- GoServer
- PostgreSQLData
- OpenAPIContract
- DockerRuntime
- Ant DesignAdmin UI
CORE FEATURES
Give the shared problems to the foundation and your time to the product
Identity, authorization, data, releases, and internationalization follow the same rules, so you can shape the business instead of repeatedly repairing the seams between surfaces.
01
Session security
Access Tokens, Refresh Token rotation, audience isolation, and secure client storage form one coherent path.
Explore authentication →02Authorization and tenancy
The frontend delivers a clear experience while Backend and SQL own authorization and tenant isolation, keeping one source of truth for access.
Explore the permission model →03End-to-end i18n
zh-CN and en-US span API, Admin, Mobile, and docs with stable error codes and fallback rules.
Understand the locale contract →04OpenAPI contracts
Routes, requests, responses, and errors flow from the server source of truth into generated clients.
Browse the API →05AK UI adaptation
Shared components and Props, Event, and Slot contracts isolate mobile pages from platform details.
View mobile components →06A maintainable engineering baseline
Migrations, tests, CI, and bilingual documentation evolve with the code, helping new contributors join one shared workflow.
Read the development guide →CAPABILITY MATRIX
One capability, three clear responsibilities
From sign-in to content publishing, follow one row to see how Mobile, Admin, and Server divide the work.
| Capability | Mobile | Admin | Server |
|---|---|---|---|
| Identity and sessions | Device identity, secure storage, refresh coordination | Secure cookies, session and MFA management | Audience isolation, rotation, revocation |
| Authorization and tenancy | Capability gates and stable error codes | Menu, action, and data-scope UX | Server authorization and SQL tenant filters |
| Content and operations | Articles, notifications, versions, profile | Content, files, jobs, settings, audit | Versioned content, object storage, workers |
| Internationalization | AkI18n, navigation, system formats | i18next, Ant Design, Day.js | LocaleResolver and embedded catalogs |
RUN FROM SOURCE
Clone it, start it, then make your first change
Follow the guide through environment checks, start the complete stack, and open Admin. You do not need to understand the whole repository before your first run.
Get the source
Clone the repository and enter the AppKernia root.
git clone https://github.com/Payhon/AppKernia.gitStart the stack
Docker runs PostgreSQL, migrations, seed, API, and Admin.
docker compose up --build -dOpen Admin
Confirm service health, sign in to Admin, then enter Mobile development.
curl http://localhost:4173/healthzPRODUCT, END TO END
From the operations console to the phone, grow one product across every surface
Manage applications, content, releases, and storage in Admin, then carry sign-in, notifications, reading, and account experiences into Mobile. Both surfaces meet through the same API and product rules.
FAQ
Questions before you begin
Is AppKernia a low-code platform?
No. It is an auditable, extensible engineering foundation and contract system. Product behavior is still implemented in Go, React, and UTS/UVue.
What stage of project is AppKernia for?
Use it to evaluate full-stack app architecture, start a new project, or help shape an open-source foundation. AppKernia is still in 0.x and will evolve quickly; before launch, complete the security, performance, backup, and platform testing your product needs.
Why call out HarmonyOS?
Because HarmonyOS should not be the platform a cross-platform stack adds last. AppKernia puts HarmonyOS NEXT on the main mobile path, so components, routes, networking, and engineering conventions evolve together.
Can I contribute without Go or UTS expertise?
Absolutely. Reproduce an issue, improve docs, review a design, add tests, check platform compatibility, or refine a translation. The community guide takes you from a first small change to a code contribution.
BUILD WITH US
If this direction solves a problem for you, help make it better
From opening an issue and clarifying a paragraph to adding a component or platform adaptation, every contribution helps the next developer start more easily. If you like AppKernia, leave a Star on GitHub so more people looking for a complete app foundation can find it.