Pricing & Trials

For Falcon, Viper, and Atlas, once we receive your trial request, we'll contact you to confirm a few things. If approved, you will receive a trial invitation by email.

For Solo and AVH, once we receive your trial request, we'll contact you only if more information is needed.

In all cases, if a trial request is denied, we'll let you know by email usually within 1 business day depending on request volume.

Viper trials are Advanced Edition which includes advanced security testing features and our MATRIX automation technology. Learn more about our Viper editions here.

Falcon trials are Essentials Edition. Premium Edition is not available as a cloud service and only provided as onsite Corellium appliances. Learn more about our Falcon editions here.

Corellium's Solo trial is for students only. Learn more about Solo here.

Atlas trials are intended for automative software development, test, and automation. Learn more about our Atlas here.

We've partnered with Arm in creating "Arm Virtual Hardware (AVH)". You can request a trial and explore a library of available processor and system board models. Please contact us about creating your own custom device models.

The duration period of a trial is typically 14 days unless we specify otherwise.

Yes. After you log in, you'll see a home screen with resources to help you on your way. This includes Corellium iOS and Android test apps to play with.

To learn more, visit corellium.com/scenarios.

No. You'll only need to provide a payment method if you decide to signup for a subscription.

You may, but you'll have to speak with us to better understand your needs and how we can help.

For Falcon, Viper, and Atlas, we offer annual subscriptions that are invoiced to your business.

For Solo, we offer monthly subscriptions for which we only accept credit cards online.

For Arm Virtual Hardware (AVH), you can provide a credit card online or purchase through business invoicing.

A device-hour signifies virtual active device usage for one hour, regardless of the number of CPU cores they contain. Devices that are turned off do not consume device-hours. At the end of each subscription period, we round up to the next whole hour after we sum all of the individual device usages together. For example, if 1 device is active for 1.6 hours, and 2 devices are active for 1.1 hours each, total usage is 4 device-hours.

A core-hour is similar, but instead of measuring devices, it measures the total CPU cores used within devices. For example, a RPi4 virtual device has a 4 core CPU while an Android-based IoT device may have a 2 core CPU.