Consulo: an open IDE platform forked from IntelliJ Community in 2013

A platform repository, not the whole product

Consulo is described in one line as a platform repository, and the important clarification follows: plugin implementations are held in their own repositories. That single sentence changes what you are looking at when you clone this project.

The platform itself started in 2013 by forking IntelliJ Community Edition, which means the foundation is JetBrains' IntelliJ architecture, and the stated main goal is to create an open IDE where you do not need to select an IDE for different languages. Instead, the project provides a standard for language implementation inside the IDE.

That is the whole idea in two clauses. Rather than an IDE per language, one IDE that hosts language implementations written against a shared standard. The topics attached to the repository confirm the shape: desktop-application, ide, platform and web-application, so the platform serves both a desktop client and a web one.

The top-level layout follows the platform pattern. There is modules/ for the core, arch/ for architecture work, distribution/ for the packaged builds, sandbox/ for the runnable sandbox projects, native/ for native components, and a.mvn/ directory for Maven configuration, alongside a top-level pom.xml.

So the sensible way to approach this repository is as the frame of a modular IDE, with the interesting content living in the plugins you would add afterwards.

Building needs Maven 3.9 and JDK 25

The build requirements are modern and specific.

You need Maven 3.9 or later and JDK 25 or later, and the build status table shows continuous integration runs against Java 25 and Java 26, each with its own workflow badge. That is a fast-moving target, and it tells you the project keeps pace with the current JDK release rather than supporting older ones.

Building from the command line is a single command:

mvn package

That is all the build documentation there is, which is a sign of how familiar the audience is: this is a fork of an existing IntelliJ-derived codebase, and the people building it know the Maven layout already.

The two run modes are the more interesting part, because they show the platform is meant to be extended and tested from the inside. The readme gives a table of commands for running Consulo from the repository:

The desktop AWT and Swing sandbox runs with `mvn consulo:run-desktop-awt-fork -am -pl :consulo-sandbox-desktop-awt`, and the web sandbox runs on port 8080 with `mvn consulo:run-web-fork -am -pl :consulo-sandbox-web`.

Both are sandbox projects, which is the platform's test harness. The desktop one runs the AWT and Swing client, and the web one runs on port 8080. The -am flag builds the required modules first and -pl selects the sandbox module, so a contributor can run the platform shell without installing anything.

That is the fastest way to see what Consulo actually is: a working IDE with no language support at all, waiting for plugins.

A daily release train rather than versioned releases

The release pattern is unusual and worth understanding before you plan an upgrade.

The three most recent releases are consulo#4585 from 2026-10-20, consulo#4584 from 2026-10-19 and consulo#4583 from 2026-10-19. These are numbered builds rather than semantic versions, and there are two of them on the same day.

A number of releases in the thousands on that cadence means the project publishes continuously, and the numbers are build identifiers rather than a version you would write in a dependency file and expect to stay stable. The last push was on 2026-10-20, the same day as the newest build, so the branch and the published artefact move together.

The repository is not archived, the default branch is master, and the licence is Apache 2.0 with LICENSE.txt and NOTICE.txt at the root. A NOTICE file alongside the licence is the usual sign that third-party code is bundled, which is exactly what a fork of IntelliJ Community Edition would carry.

The other top-level files fit the project. verbaria.json and verbaria-lock.json sit at the root alongside the licence files, and the readme does not explain them.

There is also an ISSUE_TEMPLATE.md and a CONTRIBUTING.md, and the readme points to a GitHub discussions forum, a Discord channel, a download page at consulo.app and a project site at consulo.io.

What the fork actually changes, and what it does not

The honest assessment has to start from what a fork of IntelliJ Community Edition inherits, and then ask what Consulo adds.

What it inherits is substantial. The IntelliJ platform is decades of work on indexing, incremental compilation, a language-agnostic plugin API, a settings system, version control integration, refactoring infrastructure, and a UI framework that most plugin developers already know. Consulo did not rebuild any of that, and the readme makes no claim to have.

What Consulo adds is the standard for language implementation, and the platform shape around it. The community and language support live in separate plugin repositories, which means the platform is designed so that a language implementation is a bounded, independently versioned thing rather than a module in the core tree.

That is a coherent bet, and it is not a new one: the JetBrains platform already supports plugins for many languages, and the difference here is that the project intends to be open in a way the commercial IDE is not, including the platform itself.

The costs of the fork are the usual ones and they are real. A codebase that forked a community edition in 2013 has to absorb the upstream churn or diverge from it, and the plugin API is not the same API that current IntelliJ plugins target, so an existing plugin is not portable. The build requirement of JDK 25 and later, with CI on Java 25 and 26, also means the toolchain is a moving target that a plugin author has to keep up with.

The realistic audience is therefore narrow: a team that needs a language the available IDEs do not support well, and that is prepared to build and maintain a language plugin for this platform.

Where the sponsorship and profiling tools fit

The readme closes with a section about YourKit, and the way it is written is worth a note.

YourKit supports open source projects with tools for monitoring and profiling Java and.NET applications, and the readme names the Java Profiler, the.NET Profiler and YouMonitor as its products, with YourKit named as the creator of them. A logo and a paragraph explain the relationship, and the page has the shape of a sponsorship acknowledgement.

For a project whose origin is a fork of a commercial IDE, that is a sensible way to cover the cost of profiling a codebase of that size. An IDE is a hard thing to profile because it is a long running desktop application with a lot of state, and having a profiler licence available to contributors is a real, practical contribution rather than a symbolic gesture.

The section is also a small illustration of how open source projects of this type are usually funded. There is no foundation, no institutional sponsor and no commercial product. There is a maintainer, a community on Discord and a forum, an issue template, a contributing guide, and a set of tool sponsorships.

If you are evaluating Consulo as a base for your own tooling, that funding and governance picture is part of the decision. The platform is open in the sense that you can read it, build it and extend it under Apache 2.0, and it is maintained under the Apache 2.0 licence.

Editorial conclusion

Consulo suits a Java developer or organisation that wants an IDE extensible with their own language support, or a team willing to maintain a language plugin against this platform rather than another one. It does not suit someone expecting a polished everyday editor, because it is a platform whose language support lives in separate repositories, and it does not suit a Java shop that has no reason to leave the IntelliJ ecosystem. Before evaluating it, build it with Maven on JDK 25 or later, run the desktop or web sandbox to see the shell without any language plugin, and check FUNCTIONALITY.md for what the platform currently covers.

Frequently asked questions

Official sources

1. consulo/consulo on GitHub
2. License: Apache-2.0
3. Project website
4. README
5. Releases