Build business features in an existing project. Spend less time setting it up again.
AppKernia includes account, permission, and content modules, with source for mobile apps, the admin console, and Go services. This website reuses the app's account and content APIs. AI can work against the OpenAPI contract and module conventions, then run the project's checks to reduce repeated boilerplate and integration work during Vibe Coding.
Login, permissions, and publishing are implemented. Add the pages and endpoints your project needs.
OpenAPI defines requests, responses, and error codes, giving frontend and backend work the same reference.
The project checks types, contracts, translations, and tests. AI-generated code must pass them too.
AI agents can use akone to list, create, update, and publish content. Configure the steps for a repeatable maintenance task; every operation stays within the API Client's granted permissions.
Workflow illustration
Requires an API Client and a connected service supporting the relevant content endpoints. Content operations currently use PostgreSQL.
Explore akoneSign in to manage your profile and saved articles. For development, download native module source and follow the setup and integration tutorials.
Sign in with your app email and password. Edit your display name, language, and time zone, or review saved articles and login sessions.
Membership →Secure storage, third-party authorization, push, and interactive CAPTCHA modules are free to download. Each page lists dependencies, setup steps, and device testing requirements.
Plugins →Browse project setup, enterprise apps, plugin development, and IoT articles for configuration steps, code examples, and test requirements.
Browse topics →Review workflows, system integrations, and first-release scope for training, device management, field service, and content membership apps.
A product pack shared in a group chat can still leave sales quoting old specifications and installers following a superseded guide. A manufacturing training app can assign learning by product and role, keeping the material version, practical work, and supervisor review together. After a revision, a regional lead can identify the people who need an additional check.
After a circulation-pump alert, the on-call operator needs to check the asset, sampling time, and current site response. A device-management app can put that evidence together and distinguish an accepted command from a confirmed result or an unresolved outcome. This reduces the need to reconstruct events across charts, messages, and phone calls.
A technician finds that a repair needs a spare part. Days later, the customer is still calling, but customer service can only see that a visit took place. A field-service app needs separate records for the reported problem, planned appointments, and work performed so dispatch can see delays, technicians receive follow-up tasks, and customers get a specific next arrangement.
After registration, a learner needs a suitable starting point, an achievable exercise, and someone to ask for help. A training membership app can organize material around those actions, record progress and feedback, and grant access under explicit rules. Update frequency and service commitments need to match the staff time the training team can provide.
Run the project locally, then add endpoints and pages using the OpenAPI contract and module conventions. Tutorials cover shared accounts and native plugin development.
Read development tutorials →
apps/
ak-mobile/ uni-app x
ak-admin/ React
ak-web/ Next.js
server/ Go
blueprint/ OpenAPIuni-app x · React · Go · PostgreSQL
Read release plans, architecture notes, and tutorials. Solution articles also cover implementation requirements and acceptance checks.
An app with an administration interface usually needs authentication, sessions, permissions, files, and content before its business features are useful. AppKernia brings those foundations together as editable source. Your team implements the business rules and owns testing, deployment, and maintenance for its product.
Read articleAfter a user saves an article, the website must recover a session, the API must check the article's App scope, and the database must prevent duplicate bookmarks. Following this request shows the responsibilities of Next.js, Go, and PostgreSQL, including where authorization and repeated writes are handled.
Read articleAfter obtaining source, a team still needs to decide where customer logic belongs, who operates the deployment, and who accepts upgrades. The public AppKernia foundation, private official project, and customer delivery have separate code boundaries. Record versions, access, and maintenance owners at the start.
Read articleMobile apps use uni-app x, administration uses React and Vite, the website uses Next.js, and the backend uses Go and PostgreSQL. These links open each project's official resources.
Technology marks identify our stack, not a partnership or endorsement.
