Public betaNative Axonyx

Documentation

Axonyx is a Rust-first web framework for readable `.asx` pages, Cargo-native tooling, Foundry UI, and low-JavaScript sites.

Public beta loop is live

Axonyx now has published Cargo packages, a native scaffold flow, typed `.asx` and `.ax` checks, content collections, API contract reports, state bindings, and static build output. This documentation route is rendered by Axonyx itself.

Browse the Axonyx stack

If you are new to Rust web development, start with Pages and Application flow. The deeper layers are there when you need contracts, state, UI primitives, or testing.

Read firstPagesHow `app/**/page.asx` maps to routes ExecutionRuntimeAxum, Tokio, streaming, and server policy ContractsMeltTyped routes, schema reports, and OpenAPI export Data flowData and StateQueries, actions, patches, and database boundaries UIFoundryComponents, blocks, themes, and design primitives ToolingDebuggingDiagnostics, Doctor, graphs, and error boundaries AdapterReactUse Axonyx UI inside existing React/Next apps

Choose your path

Start with Axonyx

Install the Cargo tools, scaffold a site, and run the native dev loop.

Open getting started

Learn the application flow

See the files, commands, and package roles in the order you use them.

Open application guide

Deploy to Render

Use Axonyx as a Render Web Service with Cargo build and hosted PORT.

Open Render guide

Define routes

Learn how `app/**/page.asx`, loaders, actions, and API routes fit together.

Open routing guide

Understand the runtime

Follow a page through The Melt into the Axum and Tokio production process.

Open runtime guide

Debug and build

Use diagnostics, Doctor, Aegis, and reproducible build gates.

Open debugging guide

Build with Axonyx UI

Browse native Foundry components, responsive blocks, and themes.

Open UI catalog

Use React Adapter

Use Foundry UI from React/Next.js while the native framework matures.

Open React docs

Framework loop

cargo install create-axonyx
cargo install cargo-axonyx
create-axonyx my-site --yes --template site
cd my-site
cargo ax check
cargo ax actions
cargo ax doctor --deny-warnings
cargo ax build --clean
cargo ax run dev

Content from The Melt

These cards are indexed from `content/docs/*.md` during the Axonyx build loop, then loaded with `data docs = DocsList()`.

Getting Started

Install Axonyx, scaffold a native site, and run the first Cargo-powered development loop.

Getting Started

Install create-axonyx and cargo-axonyx, scaffold a site template, then run cargo ax check, cargo ax doctor, cargo ax upgrade, cargo ax build, and cargo ax run dev.

getting-started

Content Collections

Index markdown and MDX during The Melt so docs, blogs, and CMS content can be queried without a database first.

Content Collections

Axonyx reads configured content folders during build time, extracts frontmatter, and exposes entries through Content.Collection.

Markdown files become typed content records.
Frontmatter feeds stable fields such as title and excerpt.
The Melt writes a static manifest for docs, blogs, and CMS previews.

content-collections

Foundry UI

Use the packaged Axonyx UI primitives and theme tokens from native `.asx` pages.

Foundry UI

Foundry is the industrial design language behind Axonyx UI, with reusable primitives, package-served CSS, and theme-ready surfaces.

foundry-ui

Published packages

Framework crates

Loading package versions from Axonyx state...

This line is seeded from `dist/_ax/state/snapshot.json` as the first backend-provided state packet.

UI package

`axonyx-ui` 0.0.71 is consumed as a Cargo package.

Package CSS is served through `/_ax/pkg/axonyx-ui/index.css` by the Axonyx dev/build tooling.

Foundry component behavior is served from `/_ax/pkg/axonyx-ui/js/index.js`, so apps do not need to copy generic drawer, tabs, dropdown, popover, or theme-switcher JS.

Action manifest

`cargo ax actions` reports route-local action contracts.

Use it to inspect action names, typed inputs, optional fields, and default values before wiring forms.

`cargo ax actions --schema` exposes the same route contracts for tooling, docs, and future low-code/CMS screens.

Framework status

Beta-complete loop

Scaffold, check, inspect routes/content/state/actions, build, and run are connected through Cargo.

Still maturing

Auth helpers, uploads, additional database adapters, the WASM client bridge, and Blockbit CMS remain next-layer modules.