Why install and configure JustOn in a production org?
Generally, we recommend to install and configure JustOn Billing & Invoice Management in your production org. There are several reasons to do so that outweigh the potential security gain of a sandbox.
Save time an money
Setting up JustOn in its real "run-time environment" (the production org) saves a lot of time, since there is no need to create, upload and deploy change sets, to repeat configurations that cannot be transferred, etc. For many businesses, the time gained this way outweighs the (potential) advantage of configuring the new app in a safe org.
Keep your business running without interferences
Installing and setting up JustOn in your production org has no impact on your running business processes in Salesforce. JustOn ships a number of new objects, Apex classes, etc. that (initially) do not interfere with your org and other installed apps in any way. Think of a new app you install on your phone – it is completely separate and does not affect the rest of your phone's functionality. Even better: as long as your users are not assigned a JustOn license, they do not see anything of it.
Use all data
A great part of JustOn's configuration is implemented in actual data records, like custom setting records, invoice templates, master subscriptions, etc. That is, change sets, the usual mechanism for deploying changes between Salesforce orgs, do not work for this kind of information.
Use all permissions and profiles
Sandboxes usually do not reproduce the same permission, profile and role setup as a production org. That is, configuring JustOn with a possibly limited set of permissions and roles may cause errors or malfunctions in the real environment, which requires another time-consuming configuration in the production org.
Note
This advice does not extend to custom implementations or functional tests. To this end, we still recommend to create a sandbox copy of your production org after the general JustOn configuration is done.
So the recommended setup path is
Production org: Install and configure JustOn
↳ Sandbox org: Functional tests and custom development
↳ Production org: Roll out custom development and possible adjustments
Note that we do not recommend to use developer sandboxes for two reasons: they do not contain any of your original org's data, and setting up JustOn does usually not involve Apex development. Instead, use full or partial sandboxes.
Related information:
Deploy Enhancements from Sandboxes in the Salesforce Help
Sandbox Types and Templates in the Salesforce Help
Create a Sandbox in the Salesforce Help
Refresh Your Sandbox in the Salesforce Help
Change Sets in the Salesforce Help