Axelate

Windows-first AI Workstation

 

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.

Current Product Boundary

Use Axelate today as a desktop workstation and local integration runtime:

• install, start, stop, inspect, and remove local AI runtimes
• use BYOK cloud providers from one desktop shell
• import local integrations you trust from folders, archives, or supported URLs
• inspect logs, downloads, settings, and runtime health from the launcher

Do not treat the current app as a reviewed package store. Manually imported integrations are code the user chose to run locally; signing, reviewed publisher identity, install-time permission review, and managed execution are later layers.

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:

• User Guide
• Getting Started
• Development Workflow
• Architecture
• Integration Development
• Releases
• Current State
• Contributing

Current reference:

• Trust Model
• Integration Development: RU · ZH

Planning only:

• Vision
• Roadmap

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.

Documentation rule:

• Documentation Localizations lists available language folders and translation policy.
• English files under docs/localization/en/ are canonical.
• CURRENT_STATE, GETTING_STARTED, DEVELOPMENT_WORKFLOW, ARCHITECTURE, TRUST_MODEL, and RELEASES should describe current behavior only.
• VISION and ROADMAP may describe future direction.
• RU/ZH files are localized integration-development references and may lag the canonical English docs.

Feedback