Skip to content

F0RLE/Axelate

Repository files navigation


Axelate Logo

Axelate

Windows-first AI Workstation


Download Axelate

Status: Active Development   License: Apache 2.0


Axelate is currently a Windows-first desktop workstation for local AI runtimes, BYOK cloud models centered on OpenRouter, and one-shell access to logs, downloads, monitoring, settings, and runtime control.

It already includes:

  • Rust + Tauri desktop backend
  • vanilla TypeScript frontend
  • streaming chat and persisted sessions
  • OpenRouter-backed text and image flows
  • local runtime and module lifecycle management
  • downloads, console, monitoring, and settings surfaces
  • backend-owned secure state

It is not yet a finished marketplace, managed platform, or polished MCP-first operating layer.

Preview

Axelate Launcher Preview

Axelate Settings Preview

Quick Start

Install on Windows first:

  • Node.js 26.1.0+
  • npm 11+
  • Rust via rustup (rust-toolchain.toml pins the tested version)
  • WebView2 Runtime
  • Windows SDK
  • Microsoft C++ Build Tools with the Desktop development with C++ workload

Then from the repository root:

npm run setup
npm run dev

The root package.json is a task runner. Frontend dependencies live in src/node_modules, not in a separate root node_modules tree.

Useful commands:

npm run doctor
npm run build
npm run tauri:build
npm run test
npm run typecheck
npm run lint
npm run verify

Branches, CI, And Releases

  • nightly is the active development branch.
  • main is the release-ready branch.
  • Strict CI runs on pushes and pull requests targeting main or nightly.
  • CodeQL, dependency review for dependency-file changes, scheduled security audits, Dependabot, and CodeRabbit are configured for repository review and security coverage.
  • Protected branches require the strict frontend and backend CI checks, but not a second human approval; this matches the current solo-maintainer workflow.
  • Dependabot targets nightly.
  • GitHub releases are created by pushing a version tag that starts with v.
  • Release tags must point to a commit that is already reachable from main.

Release tags must match the versions in package.json, src/package.json, and src-tauri/Cargo.toml:

git tag v0.2.0
git push origin v0.2.0

For the full release checklist, see Releases.

Docs

Start here:

Current reference:

Planning only:

Vision and Roadmap are planning documents. They are not setup guides and should not be read as a promise that those features already ship today.

Feedback

Report Bug   Request Feature

About

Windows-first AI Workstation

Topics

Resources

License

Contributing

Security policy

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors