# Protecting code and licensing for independently deployed Rails applications...?

**URL:** <https://www.ruby-forum.com/t/protecting-code-and-licensing-for-independently-deployed-rails-applications/172063>\
**Category:** Rails\
**Created:** [July 14, 2009, 3:33am UTC](https://www.ruby-forum.com/t/protecting-code-and-licensing-for-independently-deployed-rails-applications/172063 "2009-07-14T03:33:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dezrtdude](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/f4b2a3/32.png) [@dezrtdude](https://www.ruby-forum.com/u/dezrtdude)\
**Post date:** [July 14, 2009, 3:33am UTC](https://www.ruby-forum.com/t/protecting-code-and-licensing-for-independently-deployed-rails-applications/172063/1 "2009-07-14T03:33:55Z")

</div>

Hi All,

I’m writing a Rails application which will have reasonably regular  
updates – nothing abnormal here. I face a problem, however, due to  
the distribution model. Basically the application will be sold for  
stand-alone “intranet” installation due to its “add-on” nature (it’s  
basically a web interface for an existing, database-driven industry  
standard application).

My concern(s) then revolve(s) around protecting code and update models  
(registration codes, etc.) for multiple independently deployed Rails  
applications. Does anyone have a good starting point for reading up  
on this? Any input regarding such a process?

Best.

---

<div class="post-metadata">

**Author:** ![dezrtdude](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/f4b2a3/32.png) [@dezrtdude](https://www.ruby-forum.com/u/dezrtdude)\
**Post date:** [July 14, 2009, 3:42am UTC](https://www.ruby-forum.com/t/protecting-code-and-licensing-for-independently-deployed-rails-applications/172063/2 "2009-07-14T03:42:12Z")

</div>

Michael Williams wrote:  
[…]

> My concern(s) then revolve(s) around protecting code and update models  
> (registration codes, etc.) for multiple independently deployed Rails  
> applications.

There was a thread on this topic not long ago. Probably the best way to  
protect source code is to use JRuby (or Slingshot?) and compile a Java  
executable, but even that’s not foolproof – apparently Java decompilers  
have got pretty good.

As far as registration codes go, perhaps you can have the app contact  
your company’s central database for validation…

> Does anyone have a good starting point for reading up  
> on this? Any input regarding such a process?

Yeah, check the previous threads on the subject…

> Best.

## Best,

Marnen Laibow-Koser  
[http://www.marnen.org](http://www.marnen.org)  
removed\_email\_address@domain.invalid