Plunify Cloud uses a credits-based system, where users purchase credits before using the applications, tools and services. It is similar to a prepaid mobile phone plan where you pay in advance for a certain quantity and type of services.
Credits can be purchased on the Add Credits page (login required). Credits can be purchased in blocks. Each credit will cost USD$ 0.10 or the equivalent in JPY currencies.
1 credit per GB is charged for files that are stored on Plunify Cloud per month.
Example 1
Lets says you are using InTime and submitting your jobs to the Plunify Cloud. You are using CA1 class server with Vivado 2020.1.
Total cost: 4.95 + 2.9 + 2.4 = 10.25 credits/hour
Details
Here are the full details for different server types and design tools.
Hourly Rates of Server Types
| Server Class | vCPU | ECU | MEM (GiB) | SSD | Credits / Hr (Region: US) |
|---|---|---|---|---|---|
| CA1 (Compute) | 2 | 9 | 4 | Yes | 6.78 |
| CA2 (Compute) | 4 | 17 | 8 | Yes | 9.9 |
| CA3 (Compute) | 8 | 34 | 16 | Yes | 16.13 |
| CA4 (Compute) | 16 | 68 | 32 | Yes | 28.6 |
| CA5 (Compute) | 36 | 72 | 72 | Yes | 59.77 |
| RA1 (Memory) | 2 | 7 | 15.25 | Yes | 8.29 |
| RA2 (Memory) | 4 | 13.5 | 30.5 | Yes | 12.91 |
| RA2a (Memory) | 4 | 13.5 | 30.5 | Yes | 12.91 |
| RA3 (Memory) | 8 | 27 | 61 | Yes | 22.15 |
| RA3a (Memory) | 8 | 27 | 61 | Yes | 22.15 |
| RA4 (Memory) | 16 | 53 | 122 | Yes | 40.63 |
| ZA1 (Performance) | 2 | 15 | 16 | Yes | 14.15 |
| ZA2 (Performance) | 4 | 28 | 32 | Yes | 20.97 |
| ZA3 (Performance) | 8 | 53 | 64 | Yes | 34.61 |
Hourly Rates of Design Tools
| Vendor | Toolchain | Version | Credits / Hr (All Regions) |
|---|---|---|---|
| Altera | QuartusII | 13.1.4 | 2.9 |
| Altera | QuartusII | 16.0.2 | 2.9 |
| Altera | QuartusII | 18.1 | 2.9 |
| Plunify | InTime | 2022.2.1 | 4.2 |
| Plunify | InTime | 3.2.5 | 2.4 |
| Xilinx | ISE | 14.7 | 2.9 |
| Xilinx | PetaLinux | 2020.1 | 3.2 |
| Xilinx | Vitis | 2020.1 | 3.2 |
| Xilinx | Vitis | 2022.1 | 3.2 |
| Xilinx | Vitis | 2022.2 | 3.7 |
| Xilinx | Vitis | 2023.1 | 3.7 |
| Xilinx | Vivado | 2017.4.1 | 2.9 |
| Xilinx | Vivado | 2018.2 | 2.9 |
| Xilinx | Vivado | 2018.3 | 2.9 |
| Xilinx | Vivado | 2018.3.1 | 2.9 |
| Xilinx | Vivado | 2019.1 | 3 |
| Xilinx | Vivado | 2019.1.1 | 3 |
| Xilinx | Vivado | 2019.1.2 | 3 |
| Xilinx | Vivado | 2019.1.3 | 3 |
| Xilinx | Vivado | 2019.2 | 3 |
| Xilinx | Vivado | 2019.2.1 | 3 |
| Xilinx | Vivado | 2020.1 | 3.2 |
| Xilinx | Vivado | 2020.1.1 | 3.2 |
| Xilinx | Vivado | 2020.2 | 3.2 |
| Xilinx | Vivado | 2020.2.1 | 3.2 |
| Xilinx | Vivado | 2020.2.2 | 3.2 |
| Xilinx | Vivado | 2020.3 | 3.2 |
| Xilinx | Vivado | 2021.1 | 3.5 |
| Xilinx | Vivado | 2021.1.1 | 3.5 |
| Xilinx | Vivado | 2021.2 | 3.5 |
| Xilinx | Vivado | 2022.2 | 4.2 |
| Xilinx | Vivado | 2022.2.2 | 4.2 |
| Xilinx | Vivado | 2023.1 | 4.2 |
| Xilinx | Vivado | 2023.2 | 4.2 |