Sure its freeware but if you want to use it and don't have your own dedicated host you need to either find a host that has it installed or a host that will install it for you. It requires fundamental changes to both Apache and PHP. Sure it looks good and would probably even be a nice application to use but getting a host to provide the service is another story. If you read the quote from the Midgaard Manual below you will understand why this could be a problem for some hosts.
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote/font><HR>
B.5.1. Is the Midgard distribution an entire replacement for my current PHP build?
Yes, Midgard is a replacement to your copy of PHP3. The Midgard version should be able to run any PHP stuff you can throw at it, but if your system is running in a critical environment, I would recommend installing two Apache servers - one with PHP3 and one with Midgard-PHP3, and run them at separate ports. This shouldn't (I guess) eat up too much resources as you can easily specify how many httpd processes you want Apache to run. And also with this kind of setup, there wouldn't be any problems with reconfiguring one server, as the other would be unaffected by this.
In most cases, it is safe to replace the normal PHP module with the Midgard-patched one. For example, Midgard's PHP module is the default PHP package for Linux-Mandrake 6.1
This situation is far from optimal as it makes users unable to use the PHP packages supplied by their operating system vendor with Midgard and also makes it difficult for our developers to keep up with PHP releases. We're looking forward to merging our changes with the main PHP branch but there are some architectural matters making this difficult at the moment.