Nexent is a zero-code platform for auto-generating production-grade AI agents, built on Harness Engineering principles. It provides unified tools, skills, memory, and orchestration with built-in constraints, feedback loops, and control planes — no orchestration, no complex drag-and-drop required, using pure language to develop any agent you want.

One prompt. Endless reach.

Watch the demo video

🚀 Get Started Now

⭐ Before you get started, please star us on GitHub — your support drives us forward!

Deploy on Your Own

If you need to run Nexent locally or in your private infrastructure, we offer two deployment options:

System Requirements

Resource	Docker	Kubernetes
CPU	4 cores (min) / 8 cores (rec.)	4 cores (min) / 8 cores (rec.)
Memory	8 GiB (min) / 16 GiB (rec.)	16 GiB (min) / 64 GiB (rec.)
Disk	40 GiB (min) / 100 GiB (rec.)	100 GiB (min) / 200 GiB (rec.)
Architecture	x86_64 / ARM64	x86_64 / ARM64
Software	Docker 24+, Docker Compose v2+	Kubernetes 1.24+, Helm 3+

Note: Recommended configurations ensure optimal performance in production environments.

Docker Deployment (Recommended for Individuals/Small Teams)

Quick and straightforward for most users. Prerequisites: Docker 24+ and Docker Compose v2+:

git clone https://github.com/ModelEngine-Group/nexent.git
cd nexent
bash deploy.sh docker

The root deploy.sh only forwards to the target deploy script; the native Docker implementation is bash deploy/docker/deploy.sh. The Docker and Kubernetes deploy scripts share the same deployment configuration model. Interactive runs show Bash TUI menus for component selection, port policy, and image source. infrastructure is required; application, data-process, and supabase are selected by default and can be disabled when you want a smaller deployment. Use b/Backspace to return to the previous TUI step and q to quit. Use --defaults to skip the TUI and deploy with saved deploy.options or built-in defaults. Non-interactive runs can also pass the same choices with --version, --components, --port-policy development|production, and --image-source general|mainland|local-latest. Successful deployments save non-sensitive choices to each deploy directory's deploy.options for reuse on the next run.

Docker and Kubernetes both use deploy/env/.env as the runtime configuration file. Existing deploy/env/.env is kept as-is. If it does not exist, the deploy scripts first reuse docker/.env, then fall back to deploy/env/.env.example. Monitoring-specific settings are generated from deploy/env/monitoring.env.example into deploy/env/monitoring.env.

Docker uninstall is handled by bash uninstall.sh docker. It can preserve or delete data volumes: run it interactively, pass --delete-volumes true|false, or use bash uninstall.sh docker delete-all to remove containers and persistent data.