Related:

Roadmap  

[As of December, 2025]

Gekko 3.2 was released as a stable version in August 2025. New users are advised to use Gekko 3.2, but if newer features are needed, using a version in the 3.3.x series can be considered (the 3.3.x versions can be thought of as a “stable” development series (cf. the versions overview page)). Syntax changes regarding 3.3.x versions are not planned for the foreseeable future, except minor tweaks. The Gekko 2.x series is discontinued, and users are advised to migrate to Gekko 3.2 or 3.3.x.

Some aims regarding the further development of the 3.3.x series:

  • There is a Gekko Roadmap 2025 paper available, discussing how a Gekko “package” could look like. The package has since been released as a Python package on PyPI (PyGekko). At the moment the package is rather simple and string-based, using syntax like for instance: pg.run(“read gekkodatabank;”). This is expected to be developed quite a lot in 2026, integrating further into the Python language, and implementing easier looping and conditionals via Python.
  • The roadmape paper also discusses what to do about the .NET Framework being slowly phased out and replaced by .NET Core. It is envisioned to migrate the Gekko C# source code from .NET Framework to .NET Core, in order to future-proof the use of Gekko, both as a stand-alone application, and in the form of PyGekko (and the Gekcel Excel add-in for that sake). As part of this, the main Gekko window ought to migrate to use vector-based graphics (WPF) like the other Gekko windows. If a cross-platform (Linux/Mac) graphical user interface (GUI) is deemed important, for instance for PyGekko, perhaps something like Avalonia ought to be used instead of WPF.
  • Regarding Python and R etc., Apache Parquet import/export has been implemented in Gekko recently, making it easy to transfer timeseries data in the form of dataframes between Gekko and Python/R/SQL etc. The work on .parquet files is expected to continue.
  • Further work on model analysis features like for instance DECOMP, flowgraph, DISP, html browser generation, plot windows, etc.
  • More advanced seasonal correction (JDemetra+ etc.), probably via the so-called “Java cruncher”.
  • Finetuning Gekcel, among other things making available some of the Gekcel VBA code that the Central Bank of Denmark uses.
  • Fixing any bugs regarding data-traces.
  • Continued work on better error messages.