Why OpenSumi Is the Next‑Gen Open‑Source IDE for Web and Electron
OpenSumi, the first domestically developed, highly customizable, high‑performance IDE framework compatible with VS Code extensions, enables developers to quickly build dual‑platform (Web and Electron) IDEs with modular architecture, independent processes, and extensive view customization, addressing the repetitive setup challenges faced by Alibaba and Ant Group teams.
After nearly three years of joint effort by Alibaba Group and Ant Group, OpenSumi, the first domestically developed, highly customizable, high‑performance IDE development framework compatible with VS Code extensions, is now open‑source.
What is OpenSumi
OpenSumi is a dual‑platform (Web and Electron) IDE framework aimed at vertical domains, offering low entry barriers, high performance, and strong customizability.
The framework was initially launched by Alibaba’s Taobao engineering team together with Ant Group’s experience technology and R&D efficiency teams. Built with TypeScript and React, it provides core modules such as resource explorer, editor, debugger, Git panel, and search panel. Developers can start from a starter project, configure it briefly, and quickly create their own local or cloud‑based IDE product. OpenSumi is compatible with the VS Code plugin ecosystem, allowing most VS Code extensions to run seamlessly, and offers low‑cost, highly customizable view extensions to satisfy most IDE view‑customization scenarios.
Compared with existing open‑source solutions like code‑server and Theia, we chose to develop our own framework because internal teams repeatedly spent months on similar IDE foundation work, facing limited customizability, deep source dependencies, maintenance difficulties, and unmet internal requirements.
Architecture of OpenSumi
To run both in Web and Electron environments, OpenSumi adopts a front‑back separation with an abstract communication layer.
Web uses WebSocket for communication, while Electron uses IPC. Each connection has its own independent DI container, making the backend stateless and strictly isolated between connections.
OpenSumi consists of three core processes: Extension Process (plugin), Node Process (backend), and Browser Process (frontend).
Plugins run in separate processes to avoid affecting IDE performance, similar to VS Code’s approach, and communicate with the backend and frontend through the communication layer.
Core capabilities are split into modules linked by contribution points and DI, with weak dependencies. Core modules such as theme and layout services are directly depended on by other modules, so module import order must be respected during integration.
Advantages of OpenSumi
OpenSumi offers low entry barriers, high performance, and exceptional customizability for vertical business domains. It enables full‑view customization through modules or plugins, allowing developers to tailor both basic capabilities and business‑specific views.
In many internal product implementations, we naturally use modules for foundational capabilities and plugins for business‑level view or functionality customization, achieving higher maintainability and customizability. The following diagram shows a typical internal layering structure.
Open Source Repository
Project address: https://github.com/opensumi/core
Official website: http://opensumi.com/
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Java High-Performance Architecture
Sharing Java development articles and resources, including SSM architecture and the Spring ecosystem (Spring Boot, Spring Cloud, MyBatis, Dubbo, Docker), Zookeeper, Redis, architecture design, microservices, message queues, Git, etc.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
