At the risk of offending the more chaste monks, why bother using perlexe (or any modified interpreter) to do this. Pay your dues and leave the open modules open ( CGI.pm - right? right!, DBD, DBI, whatever else). Take the subroutines that are your core algorithms and re-write them in C. You can then utilize XS or Inline to create platform dependent modules that can be delivered as thin wrappers around dynamic library(ies). There are some issues with this

• You would have to invest in a development environment per platform you support.
• The devel enviroment needs to match, exactly, the environment that built perl.
• Object code can be reversed engineered too.

I think that's going to be your best approach. If you think you don't have the skills to do this "core" shared object approach, please feel free to contact myself or any of the other monks here - I'm sure any of us would be happy to help for a slice of the profits.

-derby