Downloads

You need a server first

FeltnerAI clients connect to a server you run — they don’t work on their own. If you don’t have a server yet, start with the Quick Start. Jump to Connecting to a server below once you’ve installed a client.

Clients

Web App

OfficialOpen Source

The web app is served directly by your FeltnerAI server at its root URL — there’s nothing to install. Open the server address in any modern browser and sign in.

Source

Desktop Portal

OfficialOpen Source

The native desktop client for Windows, macOS, and Linux (built with Tauri v2). Connect to one or more servers from a single app, with session credentials stored in your operating system’s credential manager. v1 has no in-app updater — reinstall to upgrade.

Download

Source

Mobile — iOS & Android

Planned

Native mobile clients are not part of v1. In the meantime, the web app works in mobile browsers against any reachable server.

Server

FeltnerAI Server

OfficialOpen Source

The standalone Rust server. It hosts the API and the embedded web app, stores your data in SQLite, and talks to your OpenAI-compatible provider. On Windows it also runs a system-tray menu.

Releases

Source

Setup guide

Build from source

Prefer to build it yourself? The server embeds the web app, so build the frontend first.

bun install --cwd frontend --frozen-lockfile
bun run --cwd frontend build
cargo build --release -p feltnerai-server

Build the desktop Portal installer for your current platform:

bun run --cwd frontend tauri build

Tauri emits platform installers under target/release/bundle. See Set Up a Server for the full walkthrough.

Connecting to a server

Every client connects to a server you run. You’ll need its URL (for example http://127.0.0.1:8080 locally, or https://ai.example.com behind a proxy) and a user account created by an administrator — there is no open registration.

• Web app — open the server URL in a browser and sign in. You’ll be asked to change your password on first sign-in. The browser client authenticates with a session cookie and CSRF token.
• Desktop Portal — install it, add a server profile using your server’s URL, then sign in. The Portal authenticates with an opaque bearer token stored in your OS credential manager.

Each account keeps its own light, dark, or system theme, applied wherever you sign in. If no models appear in the picker, an administrator needs to configure a provider and enable models.