# MeterSphere: An Open-Source Continuous Testing Platform with AI Assistance

> MeterSphere is an open-source continuous testing platform from FIT2CLOUD that covers test case management, API testing, and CI/CD integration in a single web interface. Version 3 adds an AI assistant for generating test cases and connects to DevOps pipelines through a plugin marketplace.

**metersphere/metersphere** — MeterSphere 是新一代的开源持续测试工具，内置 AI 助手，让软件测试工作更简单、更高效，不再成为持续交付的瓶颈。

- Repository: https://github.com/metersphere/metersphere
- Website: https://metersphere.io/
- Stars: 13,554 · Forks: 2,845
- Language: Java
- License: NOASSERTION
- Published: 2026-09-21 · Updated: 2026-09-21 · Language: en
- Canonical page: https://hysenlabs.com/projects/metersphere-metersphere

## Five Testing Capabilities That MeterSphere Bundles Together

MeterSphere targets software teams who want to move testing out of individual engineers' local machines and into a shared, browser-accessible platform. Rather than running separate tools for test planning, API debugging, mock servers, and reporting, the platform integrates all of these in one interface.

The README describes five distinct capability areas. The AI assistant uses a large language model to generate functional test cases and API test cases from a description, which reduces the manual authoring step that typically bottlenecks test planning. The test management module handles the full lifecycle from creating test cases, through executing test plans, to filing defects and producing reports. The API testing module handles API definition, debugging, mock responses, and multi-step scenario automation, covering ground similar to what Postman handles for individual developers but with team collaboration built in. The team collaboration design uses a three-level hierarchy of system, organisation, and project to scope access and work across teams. The plugin marketplace allows extending MeterSphere with integrations into DevOps pipelines.

The current major version is V3. The README states that V1 and V2 are no longer maintained, so teams upgrading from an older installation must migrate to the V3 line.

## How the JMeter Backend and Spring Boot Core Cooperate

The technology stack divides into four layers. The backend is built on Spring Boot, and the frontend uses Vue.js. Middleware consists of MySQL for relational storage, Kafka for event streaming between components, MinIO for file and attachment storage, and Redis for caching and session management. All components run as Docker containers.

The test execution engine is JMeter. MeterSphere wraps JMeter to run API and performance tests rather than building its own execution layer. This means tests that need JMeter-specific configuration can be expressed in the underlying JMeter format, but it also means that the platform inherits JMeter's execution model, including its thread-group approach to load.

The runtime is Java 21. The Dockerfile in the repository shows this clearly:

```dockerfile
FROM registry.fit2cloud.com/metersphere/alpine-openjdk21-jre
ENV JAVA_MAIN_CLASS=io.metersphere.Application
ENV AB_OFF=true
CMD ["/deployments/run-java.sh"]
```

The main application class is io.metersphere.Application, launched through a run script packaged with the image. A version tag is baked into the image at build time using the MS_VERSION build argument, which allows pinning specific releases.

## Deploying MeterSphere: 1Panel Store or Offline Installer

The README describes two recommended deployment paths. For a quick start, the 1Panel application store provides a one-click installation route; the README links to documentation at metersphere.io/docs/v3.x/installation/1Panel/. For production environments, the README explicitly recommends the offline installer package, documented at metersphere.io/docs/v3.x/installation/offline_installation/.

The setup documentation lives entirely outside the repository on metersphere.io. There are no inline installation commands in the README itself; both paths redirect to the external documentation site. Teams that need to follow the setup procedure without internet access to metersphere.io will find the repository alone insufficient.

Plugins are installed separately through the MeterSphere plugin marketplace at apps.fit2cloud.com/metersphere. The README notes this as a distinct step after the base platform is running. Plugins cover categories such as DevOps pipeline integrations, which means the base install and the extended integrations are managed through separate mechanisms.

The Docker Hub image is metersphere/metersphere-ce-allinone, referenced in the README's badge links. The ce-allinone naming indicates that the community edition bundles all components into a single image, which simplifies initial deployment at the cost of reducing the ability to scale individual components independently.

## Where MeterSphere Hits Its Limits

The community edition and the enterprise edition are not identical products. The README points to a pricing page at metersphere.io/pricing.html for a comparison, but provides no detail about which features are community-only and which require the enterprise tier. Teams evaluating MeterSphere cannot determine the community edition's capability ceiling from the repository alone.

The AI assistant generates test cases using a large language model, but the README does not specify which models it connects to or whether the model calls go to an external service. Teams operating in air-gapped environments or with strict data residency requirements cannot determine from the repository whether AI-assisted generation is available in such configurations.

Kafka is a middleware dependency for the platform. Kafka adds operational complexity: it requires its own cluster management, has specific retention and partition configuration needs, and introduces an additional failure point. Teams who have not operated Kafka before will face a learning curve that goes beyond MeterSphere itself.

V1 and V2 are no longer maintained. Teams running those versions have no supported upgrade path documented in this repository; the README states the discontinuation without providing migration guidance inline.

## MeterSphere Versus Apifox: Different Scope

Apifox is a development and testing tool that combines API design, documentation, debugging, and mock services for individual developers and small teams. MeterSphere positions itself as a team testing management platform: it adds test plans, defect tracking, reporting, and a three-level organisational structure that Apifox does not provide. Apifox is typically adopted at the developer or small-team level; MeterSphere targets quality assurance teams that need to manage testing across an organisation.

The distinction matters for adoption. An engineering team of five to ten people using Apifox for API debugging will not find an obvious reason to migrate to MeterSphere until they need the test plan management and multi-team coordination features. Conversely, a QA organisation running structured test campaigns will find MeterSphere's reporting and lifecycle management valuable where Apifox offers no equivalent.

RunnerGo is another open-source testing platform that the related searches associated with this project. Like MeterSphere, RunnerGo combines API testing and performance testing in one interface, but the README for MeterSphere does not compare the two directly, so any technical differences cannot be confirmed from this material.

## Licence Restrictions and Maintenance Status

MeterSphere uses the FIT2CLOUD Open Source License, which the README describes as GPLv3 with additional restrictions. The two stated restrictions are: the MeterSphere logo and copyright information cannot be replaced or modified in derived works, and any derivative work must carry GPL v3 open-source obligations. This places MeterSphere outside the scope of a permissive licence. Teams building a commercial product on top of MeterSphere's source code inherit the GPL v3 copyleft requirements.

The most recent stable release is v3.6.9-lts, published on 2026-08-11. The last push to the repository was on 2026-09-21, seven days before the time of writing, indicating active development continues. The project follows a long-term support release pattern under the v3.x branch, with separate LTS tags distinct from the development branch.

FIT2CLOUD is the company behind MeterSphere and offers paid support and the enterprise edition. The README lists several other open-source projects from the same organisation, including JumpServer for bastion host management and DataEase for business intelligence, suggesting MeterSphere is part of a broader enterprise IT tooling portfolio rather than a standalone community project.

## Conclusion

Teams running Java-heavy CI/CD pipelines who want a single tool for test management, API testing, and defect tracking will find MeterSphere covers that ground without requiring multiple separate products. Before committing, verify the FIT2CLOUD licence terms, since the licence prohibits replacing the MeterSphere logo or copyright information, and requires any derivative work to carry GPL v3 obligations. Teams needing features beyond the community edition must evaluate the enterprise version through metersphere.io/pricing.html.

## FAQ

### What is MeterSphere and what does it do?

MeterSphere is an open-source continuous testing platform that combines test case management, API testing with mock support, defect tracking, and test reporting in a single web interface. Version 3 adds an AI assistant for generating test cases from descriptions.

### Does MeterSphere require a paid licence for commercial use?

MeterSphere uses the FIT2CLOUD Open Source License, which is based on GPL v3 with two added restrictions: the logo and copyright information cannot be replaced, and derivative works must carry GPL v3 obligations. An enterprise edition with additional features is available separately.

### What is the difference between MeterSphere v3 community and enterprise editions?

The README states that MeterSphere V3 has both a community edition and an enterprise edition, and points to metersphere.io/pricing.html for a feature comparison. The specific features that differ between the two editions are not described in the repository itself.

## Sources

- [Issues](https://github.com/metersphere/metersphere/issues)
- [metersphere/metersphere on GitHub](https://github.com/metersphere/metersphere)
- [Project website](https://metersphere.io/)
- [README](https://github.com/metersphere/metersphere/blob/v3.x/README.md)
- [Releases](https://github.com/metersphere/metersphere/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/metersphere-metersphere