需先从 GitHub Release 下载二进制包并解压,README 未提供源码构建方式;standalone 模式仅适合本地试用,生产部署需参考官方文档

nacos
alibabaApache-2.0活跃维护Nacos 是阿里开源的动态服务发现、配置管理和服务管理平台,帮微服务和 AI 云原生应用统一做注册中心与配置中心。
an easy-to-use dynamic service discovery, configuration and service management platform for building AI cloud native applications.
unzip nacos-server-1.0.0.zip
cd nacos/bin
sh startup.sh -m standaloneREADME 未说明硬件要求,仅提供二进制包在 Linux/Unix/Mac 或 Windows 上以 standalone 模式启动
阿里开源的动态服务发现、配置管理与服务管理平台,用于构建云原生微服务
Nacos 是阿里开源的动态服务发现、配置管理和服务管理平台,帮微服务和 AI 云原生应用统一做注册中心与配置中心。
核心能力
- 支持服务注册与发现,提供 DNS 和 HTTP 接口
- 实时健康检查,避免请求发往不健康实例
- 集中动态管理配置,更新无需重新部署
- 支持加权路由的动态 DNS 服务
- 提供可视化控制台管理服务元数据与指标
容易踩的坑
- 3.3.03.3.0(Oct 29th, 2026)最新正式版2026-10-29 · 2026-10-29 11:07 UTC
Nacos 3.3.0
Nacos 3.3.0 is a feature iteration release for the Nacos 3.x series. It brings protocol-neutral Agent management and discovery, shared AI resource search, and unified MCP lifecycle management to the stable release.
This release focuses on:
- AI Registry capabilities across Agent, AgentSpec, Skill, Prompt, and MCP resources.
- DNS service discovery and distributed locks.
- Dynamic plugin management and authentication enabled by default.
- Spring Boot 4 and Jackson 3 compatibility, with improved client and server reliability.
The main feature updates include:
- Agent registration, version management, runtime endpoints, RAD discovery, transport negotiation, and Watch/Push through Java SDKs and Console workflows.
- Shared AI resource search with hybrid keyword and vector retrieval, artifact access, and optional relevance filtering.
- MCP draft, review, publish, online/offline, and visibility management, with migration support for historical resources.
- Optional DNS discovery with A, AAAA, and SRV records over UDP and TCP.
- Distributed reentrant and non-reentrant locks with watchdog renewal and Raft consistency.
The stable release also improves Skill metadata consistency across version transitions, extends visibility plugin capabilities, and strengthens Config SDK usability, Console compatibility, and recovery after Naming reconnects and cluster restarts.
These notes are cumulative and include the changes delivered in 3.3.0-BETA and 3.3.0-RC.
Detailed changes in this release:
Feature
- #50 Add optional DNS service discovery over UDP and TCP, with A, AAAA, and SRV records, metrics, and configurable external DNS forwarding.
- #14466 Add a neutral JSON adapter with Jackson 2 and Jackson 3 runtime support.
- #14804 Add protocol-neutral Agent lifecycle management, Console workflows, RAD discovery, runtime endpoints, transport negotiation, Watch/Push, and Java SDKs.
- #15279 Add distributed reentrant and non-reentrant locks with watchdog renewal, FIFO waiting, gRPC notifications, Raft consistency, and a Java Lock SDK.
- #15471 Support SkillSpector as an AI publish pipeline.
- #15475 Add unified dynamic plugin configuration, lifecycle management, runtime updates, deterministic discovery, and Console configuration workflows.
- #15476#15604 Add plugin-owned visibility grant and revoke APIs and Console management for Skill and AgentSpec resources.
- #15541 Add Agentic Resource Discovery with search, exploration, artifact retrieval, visibility filtering, persistent indexes, and hybrid keyword and vector retrieval.
- #15640 Add Linux RISC-V64 compatibility for RocksDB JNI loading and startup.
- #15761 Add shared MCP lifecycle management with drafts, review, publish, online/offline operations, visibility, Java SDKs, and historical reconciliation while preserving existing Config/Naming serving data.
Enhancement/Refactor
- #8354 Replace the mandatory Prometheus client dependency with a pluggable client metrics SPI and a no-op default.
- #12064 Support configuring the gRPC port offset through individual client properties.
- #12734 Add request/result-based Config SDK methods, encrypted Config CAS publishing, and conditional queries with local cache reuse.
- [#13690](https://github.com/alibaba/naco
- 2.5.52.5.5 (Oct 29th, 2026)2026-10-29 · 2026-10-29 04:01 UTC
查看更新说明
Nacos 2.5.5 Release Notes
Nacos 2.5.5 is mainly a bugfix and experience-improvement release for the 2.x series.
This release focuses on:
- Hardening server disk paths and active HTTP health checks.
- Preventing service instance loss during full cluster restarts.
- Fixing gRPC frame corruption while preserving Java 8 compatibility.
- Improving HTTP request handling and cluster member consistency.
Detailed changes in this release:
Enhancement/Refactor
- #15809 Harden server disk path validation for Config storage, local TPS rules, and ZIP extraction to prevent access outside intended directories.
- #15828 Harden active HTTP health checks by validating request targets and custom headers and restricting checks to the registered instance target.
BugFix
- #15857 Fix permanent service instance loss during full cluster restarts by excluding connection-based clients from Distro snapshots that can overwrite new registrations.
- #15865 Fix controller method lookup for HTTP HEAD requests by resolving them to the corresponding GET mappings.
- #15951 Fix inconsistent cluster member hashing by aligning
hashCode()with the address-based comparison used byequals().
Dependencies
- #15936 Upgrade gRPC to 1.78.0 to fix frame corruption causing false message-size and mid-frame end-of-stream errors, while retaining Guava 33.3.1-android for Java 8 compatibility.
Upgrade Notes
This release strengthens validation for disk paths and active HTTP health checks. Before upgrading, review the following configurations:
- Config identity fields must not be exactly
.or... Local TPS rule names must be valid file names without path separators or directory traversal components. - HTTP health-check targets must use relative URI references, such as
/healthwith optional query parameters, without a scheme, authority, or fragment. Custom headers must be valid and must not includeContent-LengthorTransfer-Encoding.
Existing HTTP health checks that fail the new validation are skipped without sending requests or changing instance health status. Update affected configurations to restore health checking.
Deployments using valid identifiers and health-check configurations require no changes for these validation updates.
Java Version Requirements
Nacos 2.5.5 retains the Java 8 baseline used by the 2.x series.
Module Java Required Nacos-Server / Nacos-Console Java 8 Nacos-Client Java 8
Full Changelog: https://github.com/alibaba/nacos/compare/2.5.4...2.5.5
- 3.3.0-RCpre-release2026-09-21 · 2026-09-21 13:11 UTC
查看更新说明
Nacos 3.3.0-RC is a release candidate for the Nacos 3.3 feature iteration. It builds on 3.3.0-BETA with expanded AI Registry capabilities, DNS service discovery, and further security and compatibility improvements.
This release focuses on:
- Protocol-neutral Agent management and RAD discovery, including transport negotiation and Watch/Push.
- Shared AI resource search and unified MCP lifecycle management.
- DNS-based service discovery and Config SDK improvements.
- Authentication enabled by default, migration safeguards, and runtime stability.
The main feature updates include:
- Agent registration, endpoint publication, discovery, Java SDKs, and Console management, with a migration path for historical A2A data.
- Search and discovery across Agent, AgentSpec, Skill, Prompt, and MCP resources, including shared indexes and artifact retrieval.
- MCP draft, review, publish, online/offline, and visibility management while retaining existing serving contracts.
- Optional DNS A-record queries over UDP and TCP.
The release also retains BETA's dynamic plugin management, distributed locks, Jackson 2/3 support, and Spring Boot 4 compatibility. It includes further fixes across Config, Naming, Console, clients, AI storage, and authorization.
These notes are cumulative for 3.3.0 and include the changes documented in 3.3.0-BETA.
Detailed changes in this release:
Feature
- #50 Add optional DNS service discovery with A-record queries over UDP and TCP.
- #14466 Add a neutral JSON adapter with Jackson 2 and Jackson 3 runtime support.
- #14804 Add protocol-neutral Agent lifecycle management, Console workflows, RAD discovery, runtime endpoints, transport negotiation, Watch/Push, and Java SDKs.
- #15279 Add distributed reentrant and non-reentrant locks with watchdog renewal, FIFO waiting, gRPC notifications, Raft consistency, and a Java Lock SDK.
- #15471 Support SkillSpector as an AI publish pipeline.
- #15475 Add unified dynamic plugin configuration, lifecycle management, runtime updates, deterministic discovery, and Console configuration workflows.
- #15476#15604 Add plugin-owned visibility grant and revoke APIs and Console management for Skill and AgentSpec resources.
- #15541 Add Agentic Resource Discovery with search, exploration, artifact retrieval, visibility filtering, persistent indexes, and hybrid keyword and vector retrieval.
- #15640 Support Nacos server deployments on Linux RISC-V with RocksDB.
- #15761 Add shared MCP lifecycle management with drafts, review, publish, online/offline operations, visibility, Java SDKs, and historical reconciliation while preserving existing Config/Naming serving data.
Enhancement/Refactor
- #8354 Replace the mandatory Prometheus client dependency with a pluggable client metrics SPI and a no-op default.
- #12064 Support configuring the gRPC port offset through individual client properties.
- #12734 Add request/result-based Config SDK methods, encrypted Config CAS publishing, and conditional queries with local cache reuse.
- #13690 Log the resolved client logging configuration and include namespace IDs in subscription logs.
- [#14804](https://github.com/alibaba/nacos
- 3.2.43.2.4 (Aug 27th, 2026)2026-08-27 · 2026-08-27 05:28 UTC
查看更新说明
Nacos 3.2.4 is mainly a bugfix, security-hardening, and experience-improvement release for the 3.2 series.
This release focuses on:
- Strengthening JRaft, HTTP/gRPC authorization, embedded database, login, active health check, and MCP import security.
- Fixing standalone Console, Prompt visibility, Config history, listener state, and MCP tool authentication issues.
- Improving Config detail, edit, and history page usability.
For cluster and API operators, this release also:
- Adds server-identity authentication to native JRaft gRPC traffic with rolling-upgrade-aware enforcement.
- Disables selected deprecated v3 AI APIs by default and provides a temporary compatibility switch.
- Adds an allowlist policy for MCP tool imports from private or local targets.
Detailed changes in this release:
Feature
- #15687 Add server-identity authentication to native JRaft gRPC traffic with rolling-upgrade-aware enforcement.
Enhancement/Refactor
- #14817 Add a shared, disabled-by-default compatibility gate for deprecated Pipeline and MCP import APIs.
- #15661 Harden distributed embedded database result resolution to supported scalar types and registered row mappers.
- #15688 Refactor controller context-path URI parsing for consistent route matching.
- #15695 Improve Config detail, edit, and history layouts with compact metadata and a full-screen content view.
- #15712 Harden active health checks by validating target addresses and disabling unsafe MySQL JDBC options.
- #15749 Add configurable outbound access control for MCP tool imports, allowing public targets and allowlisted private or local targets.
BugFix
- #15475 Fix caller identity forwarding from a standalone Console so the Server enforces caller-specific RBAC.
- #15476 Fix Prompt visibility enforcement for list, detail, version, download, and Client read paths.
- #15560 Fix MCP tool passthrough authentication being lost after publishing from the Console.
- #15634 #15563 Fix authorization metadata and resource parsing across Admin, HTTP/gRPC, Prometheus, and AgentSpec APIs.
- #15660 Fix standalone Console startup failure caused by a missing Config clone permission checker bean.
- #15682 Prevent username enumeration by normalizing login failure responses.
- #15701 Fix Config history next-record queries on Derby and apply gray-name filtering correctly.
- #15724 Preserve the namespace filter when aggregating listener-by-IP state across cluster members.
Breaking Change Notice
Nacos 3.2.4 changes the default behavior of deprecated AI APIs and private MCP tool imports, and introduces an irreversible JRaft authentication enforcement transition.
Affected users:
- Users calling the deprecated Pipeline list/detail or legacy MCP import APIs. These APIs now return HTTP
410 Goneby default. - Console operators importing MCP tools from private or local addresses. These targets now require an administrator-managed allowlist.
- Clusters attempting a mixed-version rolling downgrade after all members have enabled JRaft authentication enforcement.
Recommended upgrade path:
- Migrate to the canonical Pipeline and
/v3/console/ai/import/*APIs. If additiona
- 2.5.42.5.4 (Aug 27th, 2026)2026-08-27 · 2026-08-27 03:14 UTC
查看更新说明
Nacos 2.5.4 is mainly a bugfix, security for the 2.x series.
Detailed changes in this release:
BugFix
[#15661] Harden distributed database query result resolution. [#15712] Fix active health check target address validation.
Java Version Requirements
Module Java Required Nacos-Server / Nacos-Console Java 8 Nacos-Client Java 8
Full Changelog: https://github.com/alibaba/nacos/compare/2.5.3...2.5.4
用户点评
登录用户的真实使用记录,可按版本和硬件筛选还没有人点评。第一个说出真实体验的人最有价值。
Nacos: Dynamic Naming and Configuration Service
What does it do
Nacos (official site: nacos.io) is an easy-to-use platform designed for dynamic service discovery and configuration and service management. It helps you to build cloud native applications and microservices platform easily.
Service is a first-class citizen in Nacos. Nacos supports almost all type of services,for example,Dubbo/gRPC service, Spring Cloud RESTFul service or Kubernetes service.
Nacos provides four major functions.
-
Service Discovery and Service Health Check
Nacos makes it simple for services to register themselves and to discover other services via a DNS or HTTP interface. Nacos also provides real-time health checks of services to prevent sending requests to unhealthy hosts or service instances.
-
Dynamic Configuration Management
Dynamic Configuration Service allows you to manage configurations of all services in a centralized and dynamic manner across all environments. Nacos eliminates the need to redeploy applications and services when configurations are updated, which makes configuration changes more efficient and agile.
-
Dynamic DNS Service
Nacos supports weighted routing, making it easier for you to implement mid-tier load balancing, flexible routing policies, flow control, and simple DNS resolution services in the production environment within your data center. It helps you to implement DNS-based service discovery easily and prevent applications from coupling to vendor-specific service discovery APIs.
-
Service and MetaData Management
Nacos provides an easy-to-use service dashboard to help you manage your services metadata, configuration, kubernetes DNS, service health and metrics statistics.
The web console is available in the following languages: 中文, English, Русский(only new UI)
Quick Start
It is super easy to get started with your first project.
Deploying Nacos on cloud
You can deploy Nacos on cloud, which is the easiest and most convenient way to start Nacos.
Use the following Nacos deployment guide to see more information and deploy a stable and out-of-the-box Nacos server.
Start by the provided startup package
Step 1: Download the binary package
You can download the package from the latest stable release.
Take release nacos-server-1.0.0.zip for example:
unzip nacos-server-1.0.0.zip
cd nacos/bin
Step 2: Start Server
On the Linux/Unix/Mac platform, run the following command to start server with standalone mode:
sh startup.sh -m standalone
On the Windows platform, run the following command to start server with standalone mode. Alternatively, you can also double-click the startup.cmd to run NacosServer.
startup.cmd -m standalone
For more details, see quick-start.
Quick start for other open-source projects:
Documentation
You can view the full documentation from the Nacos website.
You can also read this online eBook from the NACOS ARCHITECTURE & PRINCIPLES.
All the latest and long-term notice can also be found here from GitHub notice issue.
Contributing
Contributors are welcomed to join Nacos project. Please check CONTRIBUTING about how to contribute to this project.
How can I contribute?
- Take a look at issues with tags marked
good first issueorcontribution welcome. - Answer questions on issues.
- Fix bugs reported on issues, and send us a pull request.
- Review the existing pull request.
- Improve the website, typically we need
- blog post
- translation on documentation
- use cases around the integration of Nacos in enterprise systems.
Other Related Project Repositories
- nacos-spring-project provides the integration functionality for Spring.
- nacos-group is the repository that hosts the eco tools for Nacos, such as SDK, synchronization tool, etc.
- spring-cloud-alibaba provides the one-stop solution for application development over Alibaba middleware which includes Nacos.
Contact
- Gitter: Nacos's IM tool for community messaging, collaboration and discovery.
- Twitter: Follow along for latest nacos news on Twitter.
- Weibo: Follow along for latest nacos news on Weibo (Twitter of China version).
- Nacos Segmentfault: Get latest notice and prompt help from Segmentfault.
- Email Group:
- [email protected]: Nacos usage general discussion.
- [email protected]: Nacos developer discussion (APIs, feature design, etc).
- [email protected]: Commits notice, very high frequency.
- Join us from DingDing(Group 1: 21708933(full), Group 2: 30438813(full), Group 3: 31222241(full), Group 4: 12810027056).
DingDing Group QR Code

DingDing MCP Group QR Code

WeChat Group QR Code

Enterprise Service
If you need Nacos enterprise service support, or purchase cloud product services, you can join the discussion by scanning the following DingTalk group. It can also be directly activated and used through the microservice engine (MSE) provided by Alibaba Cloud. https://cn.aliyun.com/product/aliware/mse?spm=nacos-website.topbar.0.0.0
Download
Who is using
These are only part of the companies using Nacos, for reference only. If you are using Nacos, please add your company here to tell us your scenario to make Nacos better.