# Pricing structure ## Executive summary The Nuvolos platform natively provides compute resources and configurable tools for computational research and educational use cases, as well as for combinations of both. The pricing structure of Nuvolos consists of two parts: the Nuvolos subscription and on-demand resources. The [Nuvolos subscription](#the-nuvolos-subscription) is based on your contract with us and runs on an annual basis (different terms are possible by agreement). The on-demand resources are additional resources that can be purchased with Credits on top of those provided by the Nuvolos subscription. You can have a Nuvolos subscription without Credits, but you cannot spend Credits on Nuvolos without a subscription. Resources include compute capability and storage (see [below](#storage)). With a Nuvolos subscription, you can have one or more [resource pools](#resource-pools), which are logical groups of resources. They can be either [shared](#shared-resource-pool) or [dedicated](#dedicated-resource-pool). In this overview, we will briefly explain each of these concepts in more detail. ## The Nuvolos subscription A subscription to Nuvolos is based on a yearly contract signed between you and the company that develops Nuvolos, ALPHACRUNCHER AG (or ALPHACRUNCHER Inc.). The subscription is tailored to your specific use case and requirements; there are no fixed tiers or plans for Nuvolos subscriptions. Instead, you provide us with your particular use case and approximate number of users, and we determine the estimated annual seats and resources you will need based on that information. The base subscription consists of the following parts for a given subscription period: * Access * Compute allocation * Storage allocation The cost of the Nuvolos subscription is based on the number of seats associated with the access component and the quantity of compute and storage resources allocated on an annual basis. The size of the resource components and the access component are not linked. This approach ensures what you pay is always custom-tailored to your actual resource needs, preventing overpayment for underutilized plans or tiers typical of SaaS offerings. In general terms, a subscription allocates to the subscriber a certain number of seats (we distinguish between full-time and part-time users), a certain number of compute units or [CUs](/pricing-and-billing/nuvolos-compute-units-ncus.md), and a certain amount of high-performance storage capacity. Seats limit concurrent active user access to the platform. We monitor compliance with the agreement by reviewing average concurrent utilization rates. The compute units (CUs) can be spent on *concurrent* usage of applications (such as Airflow, VSCode, and Spyder) up to the maximum total amount allocated to you based on your subscription. The unit of measurement is compute unit hours (CUhours), and your agreement states a term total. The subscription's resource allocation is always for an *average* usage over the year. To allow for the flexibility necessary for research, your subscription permits short-term fluctuations in usage that exceed the allocated CUs. ## Credits In addition to the general Nuvolos subscription, you can purchase Credits. These are units of measure for on-demand resources. They provide access to additional CUs, as well as special allocations such as dedicated resource pools, special kinds of storage, and professional services. Credits can be bought at the rate of 8 Euros or 9 USD per Credit. You can purchase Credits at any time as long as you have a Nuvolos subscription. Any unused Credits will roll over to the next year provided you renew your Nuvolos subscription. Credits cannot be acquired or used independently of a Nuvolos subscription. Credits can be applied to any resources available through Microsoft Azure cloud services, including specific compute needs, GPUs, storage types, and more. {% hint style="info" %} If you would like to buy additional Credits, please contact [**support@nuvolos.cloud**](mailto:support@nuvolos.cloud) and request a quote. {% endhint %} ## Application resource accounting Each application on Nuvolos has a [size](/features/applications/application-resources.md#size-and-price-of-an-application), which determines both the resources it uses *and* how the costs of these resources are covered. Each size belongs to one of the following categories: * Sizes included in plan ("Included") * Credit-based sizes purchasable with credits ("Credit") Whenever you run an application at a size included in your plan, the resource usage is recorded in [CUs](/pricing-and-billing/nuvolos-compute-units-ncus.md). This resource usage is regularly compared against your subscription limits (as described [above](#the-nuvolos-subscription)). Sizes included in the plan do **not** come with resource guarantees. An application with 4 CUs can use up to 4 vCPUs and 16 GB RAM of a larger machine. Based on the load generated by other platform users, it may only be able to use fewer resources at peak load. You can set how many CUs an application will have available as resources by changing the [application size](/features/applications/application-resources.md) yourself. Self-service changes within the platform are possible between 1 and 16 CUs. By contrast, if you run an app at a credit-based size, the application's resource pool will be charged in Credits according to its price. Credit-based sizes need to be [enabled by a space administrator](/administration/space-management/hpc-spaces.md#hpc-integration) in each space. Credit charges start when the application starts and stop when the application stops—either due to [inactivity](/features/applications/long-running-applications.md#automatic-stopping-due-to-inactivity), shortage of credits, or the end user stopping the app. During runtime, credit charges are accounted for every 15 seconds. Credit-based sizes run on dedicated compute nodes, so CPU and RAM resources are guaranteed to be exclusively available for the application, regardless of other platform users. ## Resource pools There are two types of resource pools: shared and dedicated. The standard Nuvolos subscription provides CUs from a shared resource pool. ### Shared resource pool In the shared resource pool, all applications you run draw from the same resource allocation — your general allocation of CUs. A shared resource pool is essentially a certain amount of vCPU and RAM that is configured identically and dedicated to running all applications you choose to run. ### Dedicated resource pool You can also draw from a dedicated resource pool. This is a resource pool configured specifically to optimize for one particular application, and only one application will draw on it at a time. This is useful when you need particularly heavy or unusual compute usage for a specific application (such as a High Performance Computing use case). Applications on dedicated resource pools can scale between 8 vCPUs/32 GB RAM and 120 vCPUs/456 GB RAM. As with shared resource pools, you can scale as needed using the Nuvolos platform. Unlike the regular CU allocation from a shared resource pool, usage of a dedicated resource pool requires purchasing additional Credits corresponding to the intended usage. ## Storage By default, the Nuvolos subscription includes sufficient storage for your use case. The storage provision is based on our high-performance file system, backed by Snowflake as our database provider. Specific storage needs, such as SQL-compliant table storage and large file storage for unusually large volumes of unstructured data, can be purchased as additional services using Credits. ## Cost control You can exercise cost control in various ways. The suggestions below are ordered from simplest to most impactful. ### Monitor usage regularly Use the [resource monitoring dashboard](/administration/monitoring-resource-usage.md) to track CU consumption, storage footprint, and credit spend. Resource pool managers can drill down to the organisation and space level to identify where resources are being used. * **CU consumption** — review the [CU limits and capacities](/administration/monitoring-resource-usage/ncu-limits-and-capacities.md) tile for a real-time view of your compute allocation. * **Storage consumption** — review the [file system limits and capacities](/administration/monitoring-resource-usage/file-system-limits-and-capacities.md) tile to see how much of your storage allocation is in use. ### Right-size applications Applications do not need to run at their maximum size. [Change the application size](/features/applications/application-resources.md#changing-application-resources) to match the workload: * Use a smaller included size (e.g. 1–2 CUs) for editing, light analysis, or teaching. * Scale up to larger included or [credit-based sizes](/features/applications/application-resources.md#size-and-price-of-an-application) only when running demanding computations. * Size changes take effect on the next application restart — there is no cost while the application is stopped. ### Stop idle applications Applications that are not in use still consume CUs or credits. Nuvolos [automatically stops inactive applications](/features/applications/long-running-applications.md#automatic-stopping-due-to-inactivity), but you can also stop them manually to free resources sooner. ### Rest unused spaces If a course has ended or a project is paused, [rest the space](/administration/space-management/resting-spaces.md) to move its data to more affordable storage. This can significantly reduce your [file system footprint](/administration/monitoring-resource-usage/file-system-limits-and-capacities.md) and avoid storage overage charges. When you need the data again, wake the space with a single click. ### Manage storage proactively Use the [quota usage](/features/file-system-and-storage.md#quota-usage) tool inside a space to identify large files, old snapshots, or unused application libraries that can be cleaned up. Deleting unnecessary [snapshots](/features/snapshots/delete-a-snapshot.md) is often the fastest way to reclaim space. ### Align subscriptions with the academic calendar For academic institutional use cases, CU availability is tailored to the academic year. This means CUs allocated to you will be available for a certain number of hours within the academic year, excluding the summer break period. This lowers the cost of the subscription, ensuring you do not pay for resource availability during a period when the resources are likely to go unused. For details on time constraints on CU availability, refer to our documentation on [CU architecture](/pricing-and-billing/nuvolos-compute-units-ncus.md). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.nuvolos.com/pricing-and-billing/pricing-structure.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.