Linux packages#
Download FICC from GitHub Releases.
Use a Linux x86_64 package below. The examples use the first 0.3.0 nightly,
0.3.0.dev1.
This is a prerelease for operators who want the new inference and federation
workflows. The latest stable 0.2.6 revision remains
0.2.6r4-final,
with application and package version 0.2.6.post4. Select the intended release
and verify its signed SHA256SUMS file.
VM providers require their documented host versions, transports and explicit grants. See provider support before installing VM modules.
Each package includes Python and application dependencies. Nodes need their own Python and SSH setup. The controller needs OpenSSH, GNU coreutils and xdg-utils; desktop startup also requires a systemd user manager. Installation does not start a root service.
| Format | Use |
|---|---|
Debian .deb |
Ubuntu 24.04 and Debian 12 package installation. |
Arch .pkg.tar.zst |
Arch Linux x86_64, installed with pacman. |
| AppImage | A movable executable with FUSE, or explicit extraction below. |
Portable .tar.gz |
An extracted directory with its own ficc command. |
| Wheel and source | Development and independently managed Python environments. |
Download SHA256SUMS, SHA256SUMS.sig and the selected packages from the same
release. Save the publisher's public key from the FICC website
as ficc-release.pub. The repository copy contains
the same Ed25519 key. Confirm its fingerprint through an independently trusted
channel before first use:
SHA256:Z8IL7pkS9IT5uHTv+YUsQnN4GE1N8CQPTVUNq+QLYlU
Use ssh-keygen -lf ficc-release.pub to display the downloaded key's fingerprint.
The release asset RELEASE.pub alone does not establish publisher identity.
After confirming the key, verify the signature and package checksums:
printf 'ficc-release namespaces="ficc-release-v1" ' > allowed-signers
cat ficc-release.pub >> allowed-signers
ssh-keygen -Y verify -f allowed-signers -I ficc-release \
-n ficc-release-v1 -s SHA256SUMS.sig < SHA256SUMS
sha256sum --check --ignore-missing SHA256SUMS
Run the checksum command only after signature verification succeeds, and confirm that it reports the exact package you intend to install. A checksum alone detects corruption; the pinned signing key establishes which publisher signed those bytes. Key rotation requires independent confirmation before replacing the trusted key.
0.3.0 first nightly#
Version 0.3.0.dev1 adds managed local inference and federation through HyperNet
Core and Suite 0.9.0. Select models, verify and cache their weights, reserve GPUs,
start services, stream responses and stop services through the UI, CLI or API.
Adapters support llama.cpp, Ollama and optional vLLM through their supported
interfaces. Multiple GPUs on one contributor can host a model; replicas can run
on separate contributors. Cross-host tensor parallelism is not supported.
Paired clusters can share selected inference services, delegate explicitly granted lifecycle operations and transfer verified model files with pause and resume. Scoped client credentials and federation grants control access. Revocation cancels active remote requests. HyperNet remains a separately configured installation; binary FICC packages include its application-stream SDK.
Managed inference qualification covers Linux with NVIDIA GPUs. Other platforms retain their existing FICC support but have no new managed GPU-runtime claim. Engine images and model weights are optional, separately approved downloads. See inference and federation for prerequisites, capability limits and operator procedures.
Back up controller state before upgrading. The database migration adds model, inference and federation records; rollback requires the matching pre-upgrade backup. Restored federation and inference state requires explicit operator reconciliation before resuming work. Keep durable control state separate from bulk model and task storage where I/O contention can block durable writes.
The nightly uses Debian version 0.3.0~dev1 and Arch version 0.3.0dev1.
The Debian download filename uses 0.3.0.dev1; its internal package version
retains ~dev1 for the correct upgrade order.
It is a published prerelease; it does not replace the latest stable release.
Debian and Ubuntu#
sudo apt install ./ficc_0.3.0.dev1_amd64.deb
ficc desktop
Arch Linux#
sudo pacman -U ./ficc-bin-0.3.0dev1-1-x86_64.pkg.tar.zst
ficc desktop
The recipe archive also contains a PKGBUILD and its verified portable input.
Extract it and run makepkg as a regular user to build the package locally.
AppImage#
Run the executable from a directory owned by the desktop account.
chmod +x FICC-0.3.0.dev1-x86_64.AppImage
./FICC-0.3.0.dev1-x86_64.AppImage
On first desktop use, FICC verifies and copies the bundled runtime into
~/.local/share/ficc/runtimes/ (or XDG_DATA_HOME). The on-demand service and
desktop entry use that private copy, so service startup needs no FUSE mount.
The service keeps its privilege restrictions. Each release has a separate
content-addressed runtime; existing launcher settings remain authoritative.
Opening the AppImage requires a working FUSE installation. Without FUSE, extract once into the directory where FICC will remain:
./FICC-0.3.0.dev1-x86_64.AppImage --appimage-extract
./squashfs-root/AppRun desktop
Do not use --appimage-extract-and-run or APPIMAGE_EXTRACT_AND_RUN. The upstream
runtime shares a temporary directory between invocations; a second command can
remove files still used by the service. FICC refuses that mode. The explicit
extraction directory must remain available while its launcher is installed.
Portable archive#
tar -xzf ficc-0.3.0.dev1-linux-x86_64.tar.gz
./ficc-0.3.0.dev1-linux-x86_64/ficc desktop
The first desktop start creates a private on-demand user service and opens the browser with a one-use sign-in. It approves no SSH aliases. Follow machine enrollment to configure trusted profiles. An existing launcher configuration remains authoritative. Stop the service before changing formats or moving a portable or extracted directory. Then reinstall the launcher with the same state and approved profiles.
Upgrade and remove#
Back up the stopped controller before an upgrade. Each account using the native
package must stop its service with ficc stop and close other bundled commands.
Debian and Arch transactions refuse replacement of an active bundled interpreter.
Install the new package normally, then open FICC. AppImage users must stop the service and run the new image with install-launcher
and their existing settings to select the new verified runtime. Portable users
must stop the service before replacing their extracted directory.
An upgrade from 0.2.0 migrates local state into the identity/project model with the existing local owner. It does not enable remote access, enroll contributors, activate policies or grant new source permissions. Retain the stopped 0.2.0 backup and old runtime together for rollback; do not open migrated state with the older version. Restore into a separate directory and follow the recovery procedure before resuming external work.
Use sudo apt remove ficc or sudo pacman -R ficc-bin to remove a native package.
Removal preserves private state and user launcher files. To retire the launcher,
run systemctl --user disable --now ficc.service, remove its generated service
and desktop entry, then run systemctl --user daemon-reload. Use the configured
service name if it differs.
AppImage installations also retain versioned runtime
directories under ~/.local/share/ficc/runtimes/ (or XDG_DATA_HOME). After stopping
all launchers that use a runtime, its directory can be removed. Keep the runtime
selected by any retained launcher configuration. Remove private state only when
it is no longer needed.
Release contents#
Each release includes SHA256SUMS and its OpenSSH signature, RELEASE.pub, build.json, a CycloneDX inventory, complete FICC source and a third-party source archive. The payload's bundle.json binds its files and links to the source and build inputs. THIRD-PARTY.md describes licenses and source correspondence. The AppImage runtime's native dependency versions are only listed where upstream provides evidence; its remaining build dependencies are named without a claimed binary version.
Supplied infrastructure providers remain separate wheels under runtime-packages/
in the payload. Their installed packages, hashes and dependencies enter the SBOM
and payload inventory. SDK documentation, remote deployment presets and policy
sources are included. Provider installation does not configure its external
service or grant authority. Use a dedicated Python environment or the source
installation for administrator-managed provider extensions after build.
See dependency notices, testing and the maintainer build procedure.