PeachPie's newest public tag is ten months older than its last commit, and nightly builds are subscriber only
PeachPie - the PHP compiler and runtime for .NET and .NET Core
At a glance
- What is it?
- A PHP compiler that targets the .NET runtime through the Roslyn compiler platform, distributed as a Visual Studio extension, a dotnet command line and NuGet packages. The current builds are offered to paying subscribers, two of the three continuous integration rows carry no status badge, and the file contains no command at all.
- Who is it for?
- PeachPie is the right tool for a team that already lives in .NET and has PHP code it cannot rewrite, and the wrong one for a team that needs a compatibility list, a support commitment or a reproducible current build today. Three checks decide it.
- Can I use it commercially?
- Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 10 days ago.
- What is it written in?
- Mainly C#, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- peachpiecompiler/peachpie2,490 ★ · +8
| Repository | 2026-09-30 | 2026-11-15 |
|---|---|---|
| peachpiecompiler/peachpie | 2.5k | 2.5k |
8 Stars in the last 46 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The newest public tag is ten months older than the last commit
Three releases are on record: v1.1.10 on 2024-08-23, v1.1.11 on 2025-02-20 and v1.1.13 on 2025-11-17. The numbering skips a patch, so v1.1.12 either never shipped or was made quietly and is not listed here.
The last commit to the repository is dated 2026-09-26. That leaves roughly ten and a half months of development above the newest tag, which is a long time for a compiler whose compatibility surface changes one language feature at a time.
This is not a criticism of the pace so much as a practical fact about what a consumer gets. Anyone installing from a public package feed gets code from November 2025. Anyone tracking the project for whether a given PHP feature now compiles has to read commit messages rather than release notes, and anyone who needs the current behaviour has a problem the next section addresses.
The project does describe itself as maintained in spare time by people who welcome pull requests, which is consistent with a tag cadence measured in quarters rather than weeks.
Nightly and release builds go to paying subscribers
The distribution section names the package format as the most convenient way to use the project, and then says that nightly builds and release builds are provided to subscribers on Patreon, with a link to become a patron and a promise of being listed as a sponsor.
That sentence is the whole answer to where current code lives. A public tag from November 2025 is the newest thing available without paying, and the difference between that and the current tree is the difference between working and not working for anyone waiting on a specific PHP feature or bug fix.
The repository carries the tooling such a feed needs: a PowerShell script named for the MyGet service, a NuGet configuration file, and a directory whose name is the abbreviation for NuGet packages. Publishing to a non-public feed requires exactly that sort of setup, and none of it is documented in the readme, which says only that the packages exist and where to pay for them.
So there are three channels with three different freshness levels, and the readme names none of the version numbers on any of them. The tag tells you 1.1.13, the subscriber feed tells you nothing until you subscribe, and the commit history tells you what changed without telling you what it is called.
Two of the three CI rows have no status badge and a fourth config is not in the table
The continuous integration table has three rows and three columns of platform names: AppVeyor on Visual Studio 2019, Azure DevOps on Windows, and GitHub Actions on Ubuntu 18. The status column is filled in for the first row and empty for the other two.
An empty status cell means the reader cannot tell from this file whether those two builds pass, whether they exist at all, or whether the badge simply was never pasted in. For a compiler with three platforms in play, that is the single most useful thing the file could tell you and it is the thing it withholds.
The platform names have their own age in them. Visual Studio 2019 and an Ubuntu numbered 18 are both several generations back from anything a current .NET developer would name, and neither row says which .NET version is targeted, so the table documents where the builds run without documenting what they build against.
There is also a Travis configuration file at the root of the tree, which is a fourth continuous integration system not represented in the table at all.
The command line section contains no command
The usage section opens by saying there are two ways of using the project through the dotnet command, one in a shell and one in Visual Studio through an official extension, and then covers them in turn.
The Visual Studio half is specific. The extension has a marketplace identifier, it creates new projects from templates, it builds and debugs, it profiles PHP code using the built in diagnostic tools, and it deploys to Azure. The same paragraph adds that VS Code and Rider can also be used to build and debug, without naming an extension for either.
The command line half has none of that. It points at a short introduction video for seeing the compiler run, and at a getting started page in the documentation, and stops. There is no invocation to copy anywhere in the file, no flags, no project file format and no output path.
That is defensible for a compiler whose real interface is a documented command set that changes, and it is also why this file cannot answer the question a new user has first, which is what to type. The readme also contains no code block of any kind, so nothing here can be copied without leaving the repository.
PHP and C# are meant to share one runtime in both directions
The stated goal is two way interoperability: hybrid applications with some parts written in C# and others in PHP, which the project says are entirely compatible and can communicate inside the .NET framework.
The mechanism underneath that claim is a reimplementation, not a translation. Compiled programs do not run on an interpreter ported from the PHP sources; they run on what the file calls the reimplemented PeachPie runtime, which it describes as fully compatible with the PHP runtime. So PHP semantics, including the ones that are surprising, are reproduced as managed code that .NET itself executes.
The second stated goal is performance, and its argument is structural rather than measured. Extensive type analysis plus the influence of the Roslyn compiler platform are expected to improve the performance of PHP applications and components. No figure appears in the file, and no benchmark is linked, so the claim is a design argument rather than a measurement.
A third goal names cross platform development, which is what compiling legacy PHP into portable class libraries buys: a build output that is a .NET library rather than a script tree.
Source-less distribution is presented as a security benefit
The security goal has two halves and one of them has a cost the file does not mention. The first half is that programs run inside the standardized and manageable .NET or .NET Core environment, so the code is fully verifiable without any unsafe constructs. The second is that PHP applications can be distributed source-lessly for added security benefits.
Both follow from compiling ahead of time into a managed runtime that has a verifier and a JIT rather than an interpreter that executes whatever text it is handed. Shipping without source removes one thing an attacker could read, and verifiable code removes a class of memory safety problem by construction.
What a deployment team loses is the source. A sourceless deployment cannot be stepped through, cannot be patched by hand, and cannot be symbolicated back to the code that produced it unless symbols are kept and shipped separately. Nothing in the file says whether the compiler emits portable PDBs, whether they can be published alongside the assembly, or whether that step is on the reader.
For a compiler whose stated audience includes hybrid applications with existing PHP code bases, that trade is usually worth making once and then forgetting. It is still a trade, and the file presents only the half that favours it.
Compatibility is a web page that changes, not a table in the repository
There is no compatibility table in this file, no feature matrix and no list of supported PHP versions. Both pointers go outward: a roadmap page for the state of the project, and a compatibility overview page for the state of PHP language support.
The readme does warn about this in its own words, calling the status dynamic and the project a work in progress, and saying the list of finished and planned features changes frequently and is updated regularly. That candour is worth having, and it also means the answer to any compatibility question has to be looked up at the moment of asking rather than read once.
The two pages answer different questions and neither is versioned. The roadmap tells you what is being worked on, the compatibility overview tells you what works, and the git history of the repository tells you when either changed. Only one of those three is something you can pin.
For a project whose main selling point is dropping a PHP code base onto .NET, the practical consequence is that the evaluation has to be a spike against your own code rather than a reading exercise.
The solution is steered by two MSBuild files and a build folder
The tree is the shape of a large compiler project. There is a solution file at the root, two MSBuild files that apply to every project beneath it, a directory each for source, tests, tools, build scripts and documentation, an editor configuration, a git attributes file, a git ignore, a NuGet configuration, a MyGet script and a directory of package definitions.
Two central build files is the arrangement to notice. Properties and targets defined once at the directory level apply to every project in the solution, which is how a multi project compiler keeps one version number, one set of references and one set of analyzer settings without repeating them in each project file. It also means the version a consumer ends up with is decided in two files at the root rather than in any single project's manifest.
The package definitions matter for the same reason. A directory of them plus the feed configuration is how a compiler publishes many packages that have to move together, which is consistent with the split between a types library, the compiler itself and whatever runtime pieces a program needs at execution time. None of those package names are in the readme, so the package graph has to be discovered from the feed.
The license file is named LICENSE.txt, and the terms are Apache-2.0, with the project also listed as a member project of the .NET Foundation.
Editorial conclusion
PeachPie is the right tool for a team that already lives in .NET and has PHP code it cannot rewrite, and the wrong one for a team that needs a compatibility list, a support commitment or a reproducible current build today. Three checks decide it. Ask for the compatibility overview for the PHP features you actually use, because the readme states plainly that the status is dynamic and the project is a work in progress. Ask what the current build is, because the newest public tag is v1.1.13 from November 2025 while the repository's last commit is dated 2026-09-26. And price the subscription, because nightly and release builds are described as going to subscribers on Patreon, which is the only stated route to code newer than the tag.
Frequently asked questions
What is PeachPie and what is it built on?
An open source PHP compiler for .NET, built on the Microsoft Roslyn compiler platform. PHP is compiled ahead of time and executed under the .NET runtime on what the project calls its reimplemented PeachPie runtime. It is Apache-2.0 licensed and is listed as a member project of the .NET Foundation.
How do I get the current build of PeachPie?
The readme says nightly builds and release builds are provided to subscribers on Patreon. Without a subscription, the newest published tag is v1.1.13 from 2025-11-17, while the repository's last commit is dated 2026-09-26, and it names no version numbers for the subscriber feed.
Can PeachPie mix C# and PHP in one application?
Yes, that is the first stated project goal: hybrid applications with parts written in C# and others in PHP, described as entirely compatible and able to communicate inside the .NET framework. Compiled PHP runs on the reimplemented PeachPie runtime rather than on a ported interpreter.
Does PeachPie let you deploy PHP without shipping the source?
Yes. Source-less distribution is one of the stated security benefits, on the grounds that programs run in the .NET environment, where the code is verifiable without unsafe constructs. The readme does not say whether debug symbols can be produced and shipped alongside the compiled assembly.
How complete is PeachPie's PHP compatibility?
The readme gives no list and points to a compatibility overview page and a roadmap on the documentation site, warning that the status is dynamic and the project is a work in progress whose feature list changes frequently. It also says the project is maintained in spare time.
Which IDEs does PeachPie support?
There is an official Visual Studio extension, published under the marketplace identifier iolevel.peachpie-vs, which creates projects from templates, builds and debugs, profiles PHP with the built in diagnostic tools and deploys to Azure. VS Code and Rider are named as usable for building and debugging, with no extension named for either.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/peachpiecompiler-peachpie)Star history chart for your README
[](https://hysenlabs.com/projects/peachpiecompiler-peachpie)Was this useful?