Neko has a compiler and a virtual machine with garbage collection. The compiler converts a source .neko file into a bytecode .n file that can be executed with the virtual machine. Since Neko is dynamically typed with no fixed classes, a developer only has to find the proper runtime mapping (as opposed to type mapping) so that code executes correctly. As the Neko FAQ puts it: "...it is easier to write a new or existing language on the NekoVM than it is for the CLR / JVM, since you don’t have to deal with a highlevel type system. Also, this means that languages can interoperate more easily since they only need to share the same data structures and not always the same types."
Neko requires compilation before execution, unlike its scripting language contemporaries. Since Neko doesn't need to be interpreted at runtime, it executes faster.
Neko includes a mod_neko module for the Apache server. As such, it can process user input using GET and POST requests: