Overview
CloudJiffy Marketplace provides one-click deployment of applications, stacks, and add-ons. Marketplace items themselves do not usually have a separate subscription fee. Instead, charges are based on the cloud resources consumed by the deployed environment.
This article explains how billing works for Marketplace services.
Marketplace Pricing Model
When you deploy a service from the CloudJiffy Marketplace, it is launched as a CloudJiffy environment. Billing follows CloudJiffy’s standard pay-as-you-use pricing model.
There is no standalone “Marketplace fee” for most applications.
What You Are Charged For
Marketplace deployments are billed based on the following resources:
1. Compute (Cloudlets)
-
Charged hourly based on RAM and CPU usage.
-
Includes:
-
Reserved cloudlets (minimum guaranteed resources)
-
Dynamic cloudlets (auto-scaled resources during load spikes)
-
The application you deploy determines how many cloudlets are consumed.
2. Storage
-
Each environment includes 20 GB of free SSD storage.
-
Storage usage beyond this limit is charged per GB, per hour, based on actual usage.
3. Network Traffic
-
1 GB of external traffic per hour is included for free.
-
Additional external traffic is charged per GB.
-
Internal traffic between CloudJiffy nodes is free.
4. Public IP Addresses
-
If a Marketplace application allocates a public IP, it is billed hourly.
-
Public IP charges apply even if the environment is stopped.
5. Licensed or Premium Add-Ons (If Applicable)
Some Marketplace solutions may include licensed components (for example:
-
LiteSpeed Web Server
-
Premium monitoring or CDN services)
These licenses are billed according to their usage model (usually hourly or traffic-based) and are shown separately in your billing details.
Note: Most open-source Marketplace applications do not include additional license fees.
What You Are NOT Charged For
❌ No separate Marketplace subscription fee
❌ No per-application installation fee
❌ No charge just for browsing or using the Marketplace
You only pay for resources actually consumed by the deployed service.
* Example:
If you install WordPress from the Marketplace and it creates an environment with a web node and database node, you’ll pay:
For the cloudlets used by those nodes (RAM/CPU) based on usage,
For storage beyond the free allowance,
And for any traffic/public IP or add-on licensing associated with that environment.
There isn’t a separate per-application or per-Marketplace item license fee unless the Marketplace item itself includes a paid licensed component (e.g., premium software packs or commercial add-ons) — but even then, those are usually billed as usage on your CloudJiffy account, not as a standalone Marketplace billing cycle
Need Help?
If you need help estimating costs for a specific Marketplace application or want guidance on optimizing resource usage, please contact CloudJiffy Support.