Coreon 2 Readiness: New API, New Search – Save Speed – Miscellaneous Improvements
This early January 2026 release is mainly a preparation release for launching Coreon 2 in various iterations throughout 2026: A completely reworked Search engine delivered via a new API.
Further: Various miscellaneous improvements.

Preview via a New API: Fast Search
Fast and Flexible
We see more and more activities to integrate Coreon as a single source of a truth, as a backbone into GenAI / LLM and other enterprise solutions. A live connection to Coreon makes the querying software solution benefit from the always up-to-date live data and particularly Coreon’s smart search and term annotation for many languages. This asks for ultra fast response times!
Querying a repository with more than 600,000 concepts in the graph, spanning almost 2 million terms … and achieving a response time for term recognition or search below 300 milliseconds like in the screenshot … this was the benchmark we wanted to hit.
For this two major developments were happening under the hood in autumn 2025, namely:
- Reworked Search: We moved from older Apache Solr versions to Solr 9, re-developed the indexing mechanism, and tuned it for fast responses
- Redesigned API: We reworked the interfaces. We particularly introduced selectors to not by default “deliver” all possible details per request, but allow narrowing the information, for instance, by language or by property.
Further: So-called “pagination” is now supported for basically any response that contains longer “lists” of data.
These two together, already well integrated into the beta version of Coreon 2, achieve very targeted, very fast responses.
Both components are deployed these weeks to selected repositories upon demand. Contact us! In spring 2026 – with the public launch of Coreon 2 – the new Search will become available also via the general new UI when interacting with Coreon through the browser.
Engineering teams can start developing against these new interfaces. Besides this technological step forward, a few “minor” improvements also made it into this release:
User Interaction Improvements
- Prevent accidental deletion of concepts: When you are about to delete a concept that has many narrower, i.e. children concepts then after the deletion all the children were moved to “top”, i.e. became root nodes. To prevent such an accidental deletion of broader, i.e. parent, concepts, all narrower ones require to be moved first, and then deletion is possible.
- Fast saving and updating of term and concepts: When simply adding / editing a term or a property then an integrity check of the concept content is happening. In some situations this went a few unnecessary steps too far, slowing down the response until the save operation was finished. This has been optimised. Saving, particularly for concepts with many relations, is now faster.
Various import and repository management as well as authentication related improvements also made it into this release (some of below had already been deployed as hotfixes to selected repositories):
Microsoft Excel (.xlsx) Import Enhancements
- Columns with languages based on four-letter language codes not working. This is now supported.
- Policy “Patch” fails to write new concepts: Adding new concepts at the end of a spreadsheet is now supported.
- Add a 2nd or 3rd property to an existing concept or term not supported: Adding another row to mimic the embedded structure for further concept or term properties is now supported.
Repository Management and Authentication
- User Management: Bright mode – difficult to read the page number to click on. This has been resolved.
- Logout: Login form shown within a static repository homepage instead of the full screen Login page. This has been resolved.
- Login: Screen flickers right after first ever-time registration. This has been resolved.
- Export / Import: Export fails when filter contains more than one term property rule. This has been resolved.
- Import: “Patch” method fails for concepts without terms. This has been resolved.
- Dashboard / Snapshots: Fail to apply snapshot in some circumstances. This has been resolved.
- Adapted Coreon XML Schema (XSD): The schema got two minor updates:
- “required” was removed from the edge’s
source, sourceCuidas well astarget, targetCuid @typeattributes, - the
flag_setelement can now also contain the<history>element.
- “required” was removed from the edge’s
Enjoy these product improvements. We look forward to now mature the new Coreon 2 user interface during the next couple of weeks!

