Most "state of the language" writing about Delphi amounts to state-of-vibes writing: a TIOBE screenshot, a line about how the language refuses to die, a nostalgic paragraph about 1995, and not much else. None of that tells you what actually changed this year, and for anyone deciding whether to keep funding a Delphi codebase, or whether to bet a new one on it, the release history matters far more than the mood. Between the last two Delphi anniversaries, Embarcadero shipped a real point release with a new compiler target, launched a paid agentic AI add-on, rebuilt its own bundled database engine's tooling around AI as well, and reset the free tier so it finally tracks the current branch instead of trailing a year behind it. Here is what actually shipped, in the order it shipped, with the parts that matter if you are the one who has to decide what to do with a Delphi codebase, not just write about one.
Florence gets an update, and a new CPU target
The current release line is Delphi 13, code-named Florence, continuing Embarcadero's practice of naming major versions after cities (Athens was the 12.x line before it). RAD Studio, Delphi, and C++Builder 13.1, an update release rather than a full version bump, shipped in March 2026, and Embarcadero's own announcement led with a genuinely new compiler capability instead of a changelog of bug fixes. The headline feature was a native Windows on Arm compiler: Delphi source now targets Arm64 Windows directly, compiled to native code, rather than running under x86 emulation, joining Win32, Win64, macOS, iOS, and Android as a true native compile target instead of a translated one.
“The top new feature is the addition of a Delphi native Windows on Arm compiler, based on the LLVM toolchain.”
Marco Cantu, RAD Studio architect, Embarcadero
That detail about the toolchain matters more than the platform-support line item on its own. Delphi's compilers have always been genuinely native, no VM, no JIT step, no separate runtime bundled alongside the executable, and until now that model has meant a from-scratch backend for every architecture Embarcadero has ever targeted: distinct code generation work for classic Win32, for 64-bit Windows, for the Arm chips inside Android and iOS devices. Building the new Arm-on-Windows compiler on LLVM instead of another bespoke backend means Embarcadero is standing on the same compiler infrastructure that Clang, Rust, and Swift already use for code generation and optimization, rather than hand-writing a fourth or fifth instruction set's worth of backend logic from first principles. It reads as a quiet admission that maintaining N from-scratch backends for N architectures had stopped scaling, and a bet that LLVM is the more sustainable foundation for whatever CPU target shows up next. It is also a practical answer to a real, current problem: Arm-based Windows laptops have gone from a curiosity to a shipping mainstream SKU, and until 13.1 a Delphi application on one of those machines ran under Microsoft's x86 emulation layer rather than as native code, with the performance and battery-life cost that implies for anything CPU-bound.
- Refreshed VCL styling for Windows 11, catching Delphi's native Windows UI framework up to the current OS look instead of the Windows 10-era chrome it had shipped with for years.
- Android API level 36.1 and iOS 26 as supported deployment targets, which is what actually keeps an app eligible for submission to the Play Store and App Store rather than a cosmetic version bump.
- DelphiLSP, the language server behind Delphi's code completion and navigation, now emits LSIF (Language Server Index Format) output, letting other editors and code-intelligence tools consume Delphi's own understanding of a codebase instead of re-deriving it from scratch.
Kai: an agent gets wired into a thirty-year-old IDE
In May 2026 Embarcadero shipped Kai, an agentic AI add-on for RAD Studio, and it is worth being specific about what that means instead of treating it as a generic "AI now available" checkbox. Kai is wired into CodeInsight for inline "Ghost Text" completion, a dockable Agent Chat panel that keeps project-file context instead of starting from a blank conversation every time, and what Embarcadero calls MCP-powered workflows: the Model Context Protocol, the same open standard used to let AI agents drive external tools, wired up here so Kai can read a compiler error, propose and apply a fix, trigger a rebuild, and inspect the new output, without the developer leaving the editor to do any of that by hand.
“I'm sure most of you will love it! Welcome to the Kai era of Delphi.”
Marco Cantu, Embarcadero
Two decisions about how Kai actually ships matter more than the feature list. First, the model layer is not locked to one vendor: Embarcadero's own product page lists several major cloud LLM providers as supported backends, alongside fully local options through Ollama and LM Studio for teams that legally cannot send proprietary source code to a third-party API, a real constraint for the regulated, in-house codebases that make up a large share of Delphi's actual installed base, closer in spirit to a bank's back office than to an open-source project on a public forge. Embarcadero is explicit that there is no mandatory proxy layer routing that traffic through its own servers. Second, Kai is not part of the free tier. It ships as a separate, paid add-on layered on top of an existing Professional-or-above license, sold and licensed independently of RAD Studio itself, with time-limited trial redemption available for named-user seats on version 12 or 13.
InterBase got the same AI treatment
Kai was not an isolated bet on AI tooling. InterBase 15.1, Embarcadero's own bundled database engine, shipped in the same window with AI-powered Smart CodeInsight built into its IBConsole management tool, generating, optimizing, formatting, and explaining SQL using a similar mix of cloud LLM providers or an offline Ollama model for teams that need their SQL tooling to stay entirely on-premises. The same release tightened InterBase's security defaults considerably: AES-256 encryption on by default outside the lightweight ToGo Lite edition, SHA-256 password digests, a TLS 1.2 floor with versions 1.0 and 1.1 dropped entirely, and an available FIPS 140-3 compliance mode, alongside platform support extending to Windows Server 2025, RHEL 10, and Ubuntu 24. Two products from the same vendor, shipped weeks apart, both betting that the next layer of IDE and database tooling is an AI agent with a locally-runnable escape hatch built in from day one, not a cloud-only chat window bolted on after the fact.
The Community Edition finally caught up to the paid track
Delphi's free Community Edition had been sitting on the older 12.1 codebase while the paid editions moved two releases ahead of it. In August 2026, Embarcadero pushed Delphi CE forward onto the current 13, Florence branch, bringing the free tier a native 64-bit IDE, a 64-bit language server, split editor views, a new Focus Mode, and the same refreshed Android 15 and iOS 18 support the paid editions picked up a version earlier. It does not bring the Windows on Arm compiler or the iOS 26 target that shipped in 13.1 for paid editions; Community Edition tracks its own, slower cadence rather than shadowing the paid branch feature for feature. Kai is excluded as well, and Embarcadero says so directly on its own product page rather than leaving it to be discovered at a license-check dialog.
That ceiling sits deliberately at the exact boundary between a hobbyist project and a small commercial shop, which is roughly the population Delphi's own published case studies keep describing: two- and three-person engineering teams shipping paid software, not open-source contributors building in public. It is a free tier built for precisely the segment that would otherwise never touch the product at all, not a scaled-down demo of what the paid editions do. A student, a solo freelancer, or a startup still validating a product idea can build a real, multi-platform application on Delphi CE without paying anything up front, and only has to reckon with a license upgrade once the business itself has already proven it can generate real revenue.
Where it actually sits on the one chart everyone checks anyway
For the number people ask for regardless of everything above: as of August 2026, Delphi/Object Pascal sits at #11 on the TIOBE index with a 1.37% rating, down roughly 0.46 points from about 1.83% a year earlier, sitting just behind Rust at #10 (1.45%, still climbing) and just ahead of Scratch at #12 (1.27%). TIOBE's own commentary is blunter about the platform's real adoption obstacle than most Delphi coverage tends to be: Delphi is now one of only two languages left in the TIOBE top 20 that still require a paid license for commercial use, the other being MATLAB, at a moment when almost everything else in the field is free to download and ship with. Community Edition exists specifically to blunt that objection for the smallest teams. It does nothing for anyone who grows past five developers or $5,000 a year in revenue, which describes most of the companies actually running Delphi in production.
The same source code, three decades apart
The clearest statement of what this entire release cycle is actually for did not come from a changelog. It came from a webinar Embarcadero hosted in February 2026 to mark Delphi's 31st anniversary, where Marco Cantu, the language's longtime chronicler and RAD Studio's architect, showed a ten-minute demo: the original 16-bit Delphi IDE, running on 16-bit Windows, producing a 16-bit application; a 32-bit IDE producing a 32-bit application; and current 64-bit Delphi generating a 64-bit application, all from what was, with minor exceptions, the same source code.
“They all had the same source code, safe for a minor change and styling enablement.”
Marco Cantu, describing the demo at Embarcadero's Delphi 31st-anniversary webinar, February 2026
At the end of that demo, Cantu showed a native Delphi app running on what he described only as a new, coming platform, without naming it. A month later, in March, that platform turned out to be Windows on Arm. Kai, the InterBase overhaul, and the Community Edition reset are all real 2026 news on their own terms, but the throughline connecting all of it back to a compiler first shipped in 1995 is the same one that demo made literal: the product thesis has always been recompile, not rewrite, and the 2026 release cycle is that same thirty-year-old thesis applied to a CPU architecture and a coding workflow that did not exist when the bet was first made.
Where this leaves you
- 13.1's real news is the Windows on Arm compiler, and it matters specifically because it is built on LLVM rather than another from-scratch backend, which says something about where Embarcadero expects to spend its compiler-engineering budget next.
- Kai is a paid, opt-in add-on with real model flexibility (multiple cloud LLM providers or fully local models), not a bundled feature, and it is not available in Community Edition at all.
- Delphi CE finally moved off the 12.1 branch onto Florence in August 2026, but it still caps out at $5,000 a year in revenue or five developers before Professional becomes mandatory.
- TIOBE has Delphi at #11 as of August 2026, and the paid-license requirement TIOBE calls out directly is still the platform's single biggest adoption obstacle, Community Edition or not.