For AI agents: the complete documentation index is available at https://payhon.github.io/AppKernia/en-US/llms.txt, the full documentation bundle is available at https://payhon.github.io/AppKernia/en-US/llms-full.txt, and this page is available as Markdown at https://payhon.github.io/AppKernia/en-US/guide/index.md.
AppKernia

Get started

You do not need to understand every blueprint before trying AppKernia. Run the complete system first, then go deeper into Mobile, Admin, or Server as your work requires.

If you are still deciding whether it fits your project, start with What is AppKernia? for the origin, name, technology choices, real product surfaces, and future direction.

GoalStart hereRequirements
See the complete system quicklyDocker quick startDocker Desktop and Git
Change Go or React sourceSource developmentGo 1.26, Node 24, pnpm 11, Docker
Build Android, iOS, or HarmonyOSMobile developmentHBuilderX and platform toolchains
Understand the repository firstRepository structure5–10 minutes
Decide whether the project fitsWhat is AppKernia?8–12 minutes
Project maturityAppKernia has not published a stable release yet. APIs, migrations, and component contracts may change. Before production use, complete security, performance, and platform acceptance in your own environment.

What a successful first run means

Do not treat “the command printed no error” as the finish line. A complete local start should meet all of these checks:

  1. PostgreSQL, API, and Admin are healthy in docker compose ps; Migration and Seed exit with 0.
  2. http://localhost:4173/healthz succeeds, the Admin sign-in page loads, and the browser has no blocking console errors.
  3. Sign in with a local account you created through bootstrap-admin; the repository never ships a fixed default password.
  4. Dashboard summary and trend requests finish instead of remaining in Skeleton or error states.
  5. Count a Mobile platform as passed only after its real build, install, or runtime check completes on that target.

If any check fails, go to troubleshooting, keep the first failing command and exit code, and avoid diagnosing from downstream errors.

Where to go after the first run

GoalNext step
Add a business APIRead server conventions and the OpenAPI source
Add an Admin pageConfirm permission, menu, generated client, and bilingual keys
Add a Mobile page or componentContinue with Mobile development and AK UI
Change auth, authorization, tenancyRead authentication and ownership boundaries
Prepare a contributionFollow the contribution guide and evidence checks

Suggested reading order

  1. Run from the source repository
  2. What is AppKernia?
  3. Architecture
  4. Authentication and sessions
  5. Server API
  6. Mobile components
  7. Contributing