Practical overview
When it fits
Consider Nuwax when you want to self-host an agent development platform and need several agent capabilities—such as knowledge bases, model proxying, memory and plugins—within the same service. Its optional sandbox deployment is relevant when that component should run on separate servers.
Who it is for
- Teams building private AI-agent applications who can operate Docker-based services.
- Developers who want a platform that combines agent creation and distribution with knowledge-base and runtime capabilities.
- Operators who need to deploy an optional agent sandbox separately from the main service.
Documented uses
- Build and distribute AI agents within a managed platform.
- Manage knowledge bases for agent applications.
- Route agent model requests through a model-proxy capability.
- Add memory and plugins to agent applications.
- Deploy the main service locally and, when needed, configure separately deployed sandbox services.
Requirements & limits
The repository is public and identifies the project as open source under the Apache-2.0 license. Local deployment uses the Nuwax CLI and requires Docker and Docker Compose V2. Windows 10/11 is listed with support coming soon.
- The documented local setup has a minimum requirement of 4 CPU cores and 8 GB RAM.
- Docker and Docker Compose V2 are core deployment dependencies.
- Ubuntu 22.04 LTS is the recommended Linux option; other Linux versions are not fully tested.
- The README lists macOS 10.15 or later and Linux x86_64 or ARM64; it describes Windows 10/11 support as coming soon.
- The Agent Computer sandbox is optional, can run on separate servers and is described as more resource-intensive.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Deploy the Nuwax Docker agent client
Start a Nuwax agent client container using a saved key and check its VNC desktop connection.
Before you start
- Docker installed and available on the host.
- A saved key obtained from the Nuwax website: open “My Computer,” create and save a computer, then copy its key.
- A host that can run the client container; the documented command uses a named volume to persist /home/user.
Steps
On the Nuwax website, open “My Computer,” create and save a computer, and copy the key for the NUWAX_SAVED_KEY setting.
Run the documented Docker command, replacing the NUWAX_SAVED_KEY placeholder with the copied key: `docker run -d --name nuwax-client --restart always -p 6080:6080 -v nuwax_home:/home/user -e TZ=Asia/Shanghai -e NUWAX_SAVED_KEY=YOUR_KEY nuwax-docker-images-registry.cn-hangzhou.cr.aliyuncs.com/nuwax/nuwax-agent-client:la
After the container starts, visit
http://127.0.0.1:6080/vnc.html?autoconnect=true&resize=scaleto check the VNC desktop connection.Once the client starts normally in the container, select it for use in the agent platform.
Expected outcome
The Docker client is running, and the VNC page can be used to check connectivity before selecting the client in the agent platform.
Guide limitations
- Port 6080 is described as optional and for connectivity testing only; the documentation says to block it for formal use and notes it can be omitted from the run command.
- The saved key is required. Keep it secret and replace the placeholder with the actual key.
- The Docker version of the client is covered here; the documentation directs users to the Nuwaclaw page for other versions.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 9 October 2026
- Original website title
- nuwax-ai/nuwax · Official homepage title · retained in its source language