CLI

The akurai binary is the whole toolchain. It has no subdependencies and runs anywhere a Linux binary runs.

akurai new <path>

Scaffold a new project from embedded templates. Creates frontend/, backend/, and data/, plus akurai.toml. Fails if the target exists and is non-empty.

akurai new myapp

akurai serve (alias dev)

Serve the current project. Registers every frontend/*.html as a template and renders pages against backend/page.json.

akurai serve --dir frontend --host 127.0.0.1 --port 8090

• --dir — frontend directory (default frontend)
• --host — bind address (default 127.0.0.1)
• --port — bind port (default 8090)

akurai version

Print the version.

Deploying

The binary is self-contained, so deployment is "copy the file and run it." Build a static binary for portability:

cargo build --release --target x86_64-unknown-linux-musl

Put it behind nginx for TLS and run it under systemd. That is exactly how akurai-framework.olibuijr.com — the site you are reading — is deployed.