GaiaNet Node
Run a self-hosted decentralized AI node with configured models and a knowledge base.
- Source repo
- GaiaNet-AI/gaianet-node
- Stars
- ★ 5k
- Last updated
- 1y ago
- License
- GPL-3.0
- Primary language
- Shell
- FA score
- 44/100 · Major gaps
At a glance
- How it runs
- Works with
- Universal · cross-platform
- Cost
- Free, no paid service needed
- Setup effort
- Medium · a few setup steps
- You'll need
- Typical use
- A developer who wants to run a GaiaNet node on a Mac, Linux host, or Windows WSL environment.
- Not a fit if
- Users who want a GUI or desktop app instead of shell commands
- Teams that cannot wait several minutes for large model and vector-database downloads
- Deployments needing documented hardware requirements or production access controls
- Source review
- 44/100 · Major gaps
What does this agent do, and when should you use it?
GaiaNet Node is a command-line software stack for installing, initializing, and running a self-hosted GaiaNet node. Its installer sets up WasmEdge with the wasi-nn_ggml plugin, Qdrant, rag-api-server.wasm, and a dashboard. gaianet init uses config.json to download chat and embedding models plus vector-database files, then prepares a Qdrant collection. gaianet start launches Qdrant and the LlamaEdge API Server, prints a node URL, and exposes a browser-accessible node information and chat experience. A --local-only mode limits access to localhost.
An operator installs the stack, then runs gaianet init, which reads $HOME/gaianet/config.json or a supplied remote configuration URL. Initialization downloads the configured model and vector-database files, starts Qdrant, removes an existing default collection, and downloads and imports a Qdrant collection snapshot. gaianet start starts Qdrant and runs rag-api-server.wasm with WasmEdge as a LlamaEdge API Server; the documented example supplies chat and embedding models, a prompt template, a Qdrant collection, and a web UI. The command prints a GaiaNet node URL that can be opened in a browser for node information and chat. gaianet config updates fields including model URLs, context sizes, port, prompts, domain, snapshot, and retrieval settings; the node must be reinitialized afterward.
- A developer who wants to run a GaiaNet node on a Mac, Linux host, or Windows WSL environment.
- A prototype team deploying a question-answering service with chosen model files and a Qdrant knowledge-base snapshot.
- A user launching the documented
llama-3-8b-instruct_londonpreset with a London guidebook knowledge base. - An operator testing a node privately on one machine with
gaianet start --local-only. - A maintainer changing chat or embedding model URLs through
gaianet configand rebuilding the initialized node state.
How do you install or deploy this agent?
From a shell on Mac, Linux, or Windows WSL, run:
curl -sSfL 'https://github.com/GaiaNet-AI/gaianet-node/releases/latest/download/install.sh' | bashFollow the terminal prompt to set the environment path; the command begins with source. The default base directory is $HOME/gaianet. To choose another directory, run:
curl -sSfL 'https://raw.githubusercontent.com/GaiaNet-AI/gaianet-node/main/install.sh' | bash -s -- --base $HOME/gaianet.altThen run gaianet init to download the model and vector-database files. The supplied material does not list required credentials.
How do you use this agent?
Initialize the default node:
gaianet initOr initialize from a preset or your own config.json URL:
gaianet init --config https://raw.githubusercontent.com/GaiaNet-AI/node-configs/main/llama-3-8b-instruct_london/config.jsonStart it:
gaianet startFor localhost-only access:
gaianet start --local-onlyThe command prints a node URL that can be opened in a browser for chat. Stop the node with:
gaianet stopAfter changing configuration with gaianet config, run gaianet init again.
What are this agent's strengths and limitations?
- Provides a coherent
gaianetCLI flow from installation through model and vector-snapshot initialization to service startup. - The documented install process sets up WasmEdge, Qdrant,
rag-api-server.wasm, and a dashboard rather than only supplying model assets. - Supports configuration through remote
config.jsonfiles as well as model URLs, prompts, and Qdrant retrieval parameters. --local-onlysupports local operation without making the node available through GaiaNet public URLs.
- Initialization downloads large model and vector-database files, which the documentation says can take several minutes.
- Operation depends on a shell, network access, WasmEdge, Qdrant, and the LlamaEdge API Server, increasing deployment complexity.
- Any update made with
gaianet configrequires anothergaianet init. - The supplied material does not document hardware requirements, resource usage, authentication, or production access controls.
How does this agent compare with similar options?
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| GaiaNet Node This agent | 44 · Major gaps | CLIFree | ★ 5k | 1y ago | Shell | — |
| ODS Private AI Server | 71 · Some gaps | CLIFree | ★ 7.8k | 2d ago | Python | OpenAI API · Claude API |
| Sim AI Workspace | 71 · Some gaps | CLIFreemium | ★ 30k | 1d ago | TypeScript | OpenAI API · Claude API |
| Hexabot | 53 · Major gaps | CLIFree + model costs | ★ 1.2k | 3d ago | TypeScript | — |
How does FollowAgents rate this agent?
Why each dimension lost points
Evidence shows the install script downloads and executes external binaries (WasmEdge, Qdrant, frpc) without checksum or signature verification, so dependency security is only partially handled. User confirmation: install and init commands execute downloads and start services without explicit risk warnings or consent prompts. Data flow transparency is limited; README describes components and ports but not detailed data flows or privacy implications. Sensitive data handling is not explicitly addressed, but the node may process user queries and model data. External effects include starting local services and potentially exposing public URLs, but no explicit warnings. Rollback: uninstall.sh is provided but no detailed rollback steps. Source attribution: publisher is unverified, but repository has clear authors and community links.
Self-consistency: commands in README and CI workflow are mostly consistent, but there are minor inconsistencies like install script paths and versions. Dependency availability: relies on external services (Hugging Face, GitHub Releases) without mirrors or fallbacks. Failure messages: CI workflow has log output, but user docs lack detailed error handling instructions.
Audience and scenarios: README targets users who want to run their own node, with various configuration options. Capability boundaries: docs describe what the node can do but not limitations or security boundaries. Trigger precision: commands and config options are clearly described, but trigger conditions are not detailed. Environment fit: supports Mac, Linux, Windows WSL, but no other platforms or hardware requirements.
Information architecture: README is well-structured with quick start, install, config sections. Install notes are detailed with multiple methods. Naming stability: command and config names are consistent, but no version history. Examples and FAQ: provides example commands and outputs, but no FAQ. Known limitations: not explicitly listed. License: GPL-3.0 license file provided. Versioning/changelog: release workflow exists but no changelog. Maintenance responsibility: security contact and community links provided, but maintainers not clearly identified.
Output usability: node provides API and Web UI with standard output formats. Marginal value: provides unique value for decentralized AI node deployment. Cost-benefit: users bear hardware and bandwidth costs, but no cost estimates provided.
Claim traceability: claims in README lack specific evidence or links. Cross-source corroboration: CI workflow provides some tests, but no independent verification. Fact-inference separation: docs do not clearly distinguish facts from inferences.
- Install script executes externally downloaded binaries without checksum or signature verification, posing supply chain risk.
- Node may expose public URLs by default; users should be aware of privacy and security implications.
- Publisher identity is unverified; reliance on community trust.
Recent releases
Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.
-
Release notes excerpt
Major changes: - Upgrade to gaia-nexus 0.8.2 - Upgrade to cardea-agentic-search 0.10.0 - Upgrade to llama-api-server 0.27.0 - Update config.json - Update default chat model to Qwen3-4B-Q5_K_M.gguf and values of relevant configuration items - Remove context_window configuration item - Remove rag_policy configuration item - Remove rag_prompt configuration item Components - CLI Tool v0.6.0 - gaia-nexus v0.8.2 - llama-api-server v0.27.0 - WasmEdge v0.14.1 with ggml plugin b6399 - cardea-agentic-search v0.10.0 - qdrant v1.14.1 - dashboard v3.1 …View on GitHub ↗ -
0.5.4 GaiaNet-Node v0.5.4
Release notes excerpt
Major changes: - Upgrade to llama-api-server 0.25.1 - Upgrade to ggml plugin b6097 - Upgrade to gaia-nexus 0.1.4 Components - CLI Tool v0.5.3 - gaia-nexus v0.1.4 - llama-api-server v0.25.1 - WasmEdge v0.14.1 with ggml plugin b6097 - qdrant v1.14.1 - dashboard v3.1 - vector v0.38.0 - frpc v0.1.3View on GitHub ↗ -
0.5.3 GaiaNet-Node v0.5.3
Release notes excerpt
Major changes: - Upgrade to gaia-nexus 0.1.2 - Upgrade to llama-api-server 0.24.1 - Upgrade to ggml plugin b5896 - Upgrade to Qdrant 1.14.1 Components - CLI Tool v0.5.3 - gaia-nexus v0.1.2 - llama-api-server v0.24.1 - WasmEdge v0.14.1 with ggml plugin b5896 - qdrant v1.14.1 - dashboard v3.1 - vector v0.38.0 - frpc v0.1.3View on GitHub ↗
FAQ
Does it require an account or API key?
What does initialization download?
gaianet init downloads the chat model, embedding model, and Qdrant vector-database files or snapshot specified by config.json.Can I keep the node local?
gaianet start --local-only makes it accessible only through localhost and not through GaiaNet public URLs.Do configuration changes take effect immediately?
gaianet config to update fields, you must run gaianet init again.