Download

tip

V2.3.0 is now officially released with major upgrades! This update introduces full support for Kingbase and ShenTong databases, integrates gRPC communication protocol and serializers to significantly enhance distributed transaction capabilities. Core optimizations include: boosted JSON efficiency via fastjson2 serialization/parsing, simplified transaction development with Saga annotations, and hardened security through SSL-encrypted Raft node communication. This release delivers stronger stability and security for your system infrastructure!

System Requirements

note

The following system requirements are the minimum required to deploy Seata-Server: if your device does not meet these requirements, you may not be able to deploy Seata-Server on your device.

Items	Requirements
Java Development Kit (JDK)	JDK 8 or higher
CPU	1 core and above, supports 64-bit CPUs
Memory	2G and above
Disk	No minimum requirement, requires specific adjustments based on logging, storage mode, and other configurations
Operating System	64-bit Linux, Mac OS X, Windows

Stable Version

ASF Release

Version	Source	Binary	Release Notes	Reference Docs
2.3.0	apache-seata-2.3.0-incubating-src.tar.gz ASC SHA512	apache-seata-2.3.0-incubating-bin.tar.gz ASC SHA512	2.3.0 Release Notes	2.3.0 Quick Start
2.2.0	apache-seata-2.2.0-incubating-src.zip ASC SHA512	apache-seata-2.2.0-incubating-bin.tar.gz ASC SHA512	2.2.0 Release Notes	2.2.0 Quick Start
2.1.0	apache-seata-2.1.0-incubating-src.tar.gz ASC SHA512	apache-seata-2.1.0-incubating-bin.tar.gz ASC SHA512	2.1.0 Release Notes	2.1.0 Quick Start

1. Seata version maintenance policy, please refer to the version maintenance document , please upgrade the lower version to the current maintenance version as soon as possible. For version upgrade, please refer to the upgrade guide
2. For more release history downloads, please refer to Release History

Verify the releases

It is crucial to verify the integrity of downloaded files using GPG or SHA signatures. You should download the KEYS along with the .asc and .sha512 signature files for the appropriate distribution. It is recommended to obtain these files directly from the main distribution directory, rather than from mirror sites.

Verify Signatures

1. Download the GPG signatures KEYS and the release along with its .asc signature file.

2. Import the public key:

   gpg --import KEYS

3. Verify the signature:

   gpg --verify apache-seata-***.asc apache-seata-***

   If something like the following appears, it means the signature is correct:

    gpg: Signature made Tue Apr 29 12:11:09 2025 CST
    gpg:                using RSA key 775377BF271D659E591249CD63E269707E8BF0FB
    gpg: Good signature from "xxx" [ultimate]

Verify Checksums

1. Download the release along with its .sha512 signature file.

2. Verify the checksum:

   shasum -c apache-seata-***.sha512

   If something like the following appears, it means the checksum is correct:

   apache-seata-***.tar.gz: OK