When using CQ5 quickstart, it’s easy to know what runmode you’re using, as it’s defined by the jar file name itself – eg; cq-author-4502.jar. But if you use the start/stop scripts and want to confirm they are configured correctly, or are using a CQ5 instance that has been previously started by someone else, you might want to be 100% sure of the runmode(s) that CQ5 is operating in. The easiest way to do this is through the OSGi console.
CQ5.5
- Open the OSGi console and click the Configuration Status button (or navigate directly to http://SERVER:PORT/system/console/config)
- Traverse through the tabs with the >> link on the right, and select the Sling Settings tab
- Confirm the runmodes
AEM (CQ5.6)
- Open the OSGi console and navigate to Main > OSGi > Sling > Web Console > Configuration Status (or navigate directly to http://SERVER:PORT/system/console/config)
- Traverse through the tabs with the >> link on the right, and select the Sling Settings tab
- Confirm the runmodes
I've been a developer for over a decade, working with a varied range of products. I'm also an Adobe Certified Expert AEM 6.0 Developer, CQ 5.6 Component Developer, ColdFusion, and Advanced ColdFusion, and a Certified Scrum Master.
Code Monkey 
Pingback: AEM Best Practice: OSGi Configurations | Code Monkey
AEM (CQ5.6.1)
1) Open the OSGi console and navigate to Status > System properties (or navigate directly to http://SERVER:PORT/system/console/status-System%20Properties)
2) Confirm the runmodes
for 5.6.1 – it’s http://SERVER:PORT/system/console/status-slingsettings
Jason, the same also applies for AEM 6
Also we are able to know runmode in code, it can be useful if we create some components with different behavior for both modes. It’s described here, on StackOverflow: http://stackoverflow.com/questions/12245751/determine-runmode-in-adobe-cq