Native Client is a sandboxing technology used by Google both to sandbox it's own browser (Chrome) and Chrome store applications. NaCl provides a secure sandbox to native code: thus through a Chrome store app, NaCl is a great way to access low level performance of a user's machine without leaving the web browser. Outside of Google, NaCl is used by ZeroVM to provide a sandboxed environment to a single process, reducing application startup times to 5ms! PNaCl is a portable extension of NaCl. At its core, it is a generic low level byte/bit code, capable of efficiently representing almost any high(er) level language, though only C/C++ is supported officially. It provides all of the benefits (save for one: asm usage) of an architecture specific NaCl module, but is able to run on any architecture that has a translator built for it. Currently LLVM handles this role, and can translate PNaCl bitcode to sandboxed x86-32/x86-64, ARM, and MIPS code, which can then be run inside a sandboxing ELF loader. In Chrome, PNaCl has one additional benefit: PNaCl applications can be embedded within any web page and run without requiring additional steps by the user. To integrate PNaCl/NaCl applications with the API's and feature's present within the Chrome browser, one uses a library, called Pepper, which wraps the raw IPCs used to communicate outside of the sandbox, called an IRT. For example, Chrome provides an IRT for such things like accessing the HTML5 filesystem to store persistent files. At a modest rate of $20/hr, I can provide yourself and/or your team with valuable experience porting your applications to run either in PNaCl or NaCl. As a regular `native-client` contributor and as the creator and maintainer of the Rust PNaCl fork, I have intimate knowledge of the idiosyncrasies of Google's PNaCl/NaCl. Additionally, though my work in the Rust ecosystem, I have much experience working with the Pepper API. I am also available for programmin