Data

 █████╗ ██████╗ ███████╗██╗  ██╗       ██╗███████╗
██╔══██╗██╔══██╗██╔════╝╚██╗██╔╝       ██║██╔════╝
███████║██████╔╝█████╗   ╚███╔╝        ██║███████╗
██╔══██║██╔═══╝ ██╔══╝   ██╔██╗   ██   ██║╚════██║
██║  ██║██║     ███████╗██╔╝ ██╗  ╚█████╔╝███████║
╚═╝  ╚═╝╚═╝     ╚══════╝╚═╝  ╚═╝   ╚════╝ ╚══════╝

The full-stack meta-framework for Alpine.js. File-based routing, server-side rendering, API routes, and one CLI — powered by Vite and Node.

Apex is to Alpine what Next.js is to React. You already know the syntax: if you can write x-data, you can build a full-stack, server-rendered app — shipping a fraction of the JavaScript of a React framework.

npm i -g @apex-stack/core   # install the Apex CLI (once)
apex new my-app             # scaffold, install deps, init git
cd my-app
apex dev                    # → http://localhost:3000

No global install? npm create apexjs@latest my-app, then npm run dev — same result using the project-local CLI (apex then runs via npm run dev / npx apex, like next or vite).

Why Apex

Every major reactive library has a meta-framework — React has Next, Vue has Nuxt, Svelte has SvelteKit. Alpine.js, despite its huge mindshare, has none. Apex fills that gap:

• HTML-first, JS-light. Server-render your pages to real HTML; Alpine hydrates only what needs interactivity.
• Zero new component model. An .alpine single-file component is just HTML, a server loader(), and scoped CSS.
• Node-native. No PHP required — bring Alpine's DX to the entire JavaScript ecosystem.
• TypeScript by default. Strict types end to end.
• AI-native, safely. Every typed route is also an MCP tool — and one auth policy (defineAuth + auth/can + resource access/scope) governs pages, REST, and the MCP surface, so an AI can never exceed the logged-in user. See AUTH_DESIGN.md.
• Runs on the phone. apex build --mobile packages your app into an installable native shell that runs the same SSR, API routes, on-device SQLite, and auth on the device — fully offline, no server, no port. Same code as the web.
• Installable + offline on the web too (🟡). A pwa: { name } config block makes apex build emit a web manifest + a precache service worker — apex extend pwa sets it up, icons included.

Packages

Run on the device (mobile)

apex build --mobile packages an Apex app into a self-contained bundle that runs its full SSR + API pipeline on a bare on-device JS engine — Android's androidx.javascriptengine, iOS's JavaScriptCore. Offline, no server, no port: server-rendered pages, /api routes, an on-device SQLite (sql.js compiled to pure JS, seeded at boot and persisted across cold starts), and sealed-cookie auth — the same <script server> loaders, routes, and auth you wrote for the web, unchanged.

It's a WebView app (like Capacitor or Ionic), but unlike them it runs your actual server — SSR + API + DB + auth — on the device, from one TypeScript codebase. Not React-Native native widgets. External APIs (Supabase, Turso over HTTP) still work from client code.

apex build --mobile                          # self-contained on-device bundle
apex mobile android --appId com.you.app \
  --name "My App" --assemble                 # scaffold native shell, sync assets → APK
apex mobile ios --appId com.you.app \
  --name "My App" --generate                 # scaffold WKWebView shell, sync assets (build on a Mac)

apex mobile android scaffolds the native shell and syncs your assets; --assemble runs gradle to produce an installable APK (needs the Android SDK). apex mobile ios scaffolds a WKWebView + JavaScriptCore shell into mobile/ios and syncs the same bundle; --generate runs XcodeGen for you, but building and signing needs a Mac + Xcode. The iOS engine is CI-verified on the iOS Simulator; Android is turnkey (one command → APK) while iOS scaffolds anywhere and compiles on a Mac. See the mobile docs.

Status

On npm — start with npm create apexjs@latest. See ROADMAP.md for what's built and what's planned.

Support

Apex JS is free and MIT-licensed. If it's useful to you, you can support its development:

ko-fi

License

MIT © Andre Corugda