Start for Free. Pay as you grow.

Subscriptions are tied to an organization in UbiOps.

Subscriptions determine the limits on one or more of the following metrics:

• Organizations
• Users
• Projects
• Deployment versions
• Compute credits

Subscription fees are billed on the first day of your monthly billing cycle.

You can upgrade or downgrade your paid subscription at any time. For example when changing from free to basic. Or by adding or removing extra users or monthly compute credits. Such adjustments become effective immediately after we received your payment. Fees for the month in which the change is made are calculated and billed pro-rata, based on the remaining days in the current billing cycle (month).

You can cancel your paid subscription at any time.  This adjustment becomes effective on the last day of the billing cycle in which you make the change. After canceling, your subscription will be changed to a free plan. Allowing you to login to UbiOps and access your existing projects and deployments. As long as you are within the Free subscription limits, you will be able to create new deployments or spend compute credits.

In the event that downgrading your subscription leads to an exceeding of the user, projects and/or deployment version limits, you will no longer be able to make requests to your deployments. By deleting the exceeding items you can get back within your limits and be able to use your deployments again.

In the unlikely event that payment of your monthly subscription fees is unsuccessful, your account will be suspended, preventing you from making requests to your deployments. Upon successful receipt of payment, your account will be activated again.

An organization is the entity that holds a single license or subscription to UbiOps. An organization can have multiple users and projects.

A user corresponds to an individual UbiOps user account and is associated to an email address. These accounts are personal and should not be shared.

When creating a user account, an organization is created in UbiOps automatically.

If you want to work with others on your projects within UbiOps, you can invite more users to your organization. Using the roles and permissions system you can set and control the individual user permissions on a organization, project and/or deployment level.

You can add or remove new users to your organization at any time. To be able to add a new user, your subscription user limit should not be reached yet. If the user limit is reached, a subscription upgrade is required before the new user can be added to your organization.

UbiOps also allows for creating service users. These are artificial users which are related to API tokens for accessing the UbiOps API. Service Users can be assigned roles just like normal users to specify their permissions. 

Service users are not counting as regular users and thus not included in the subscription user limits. Service users should however not be used as regular users.

A project is an entity within an organization in UbiOps.

The number of projects you can have in your organization is limited and varies per plan.

Deployments are objects within UbiOps that serve a user’s Python or R code. A deployment is a container that can receive requests to transform input data into output data.

Every deployment in UbiOps consists of one or more versions. Each version of the model can have different implementation, resource allocations or Python runtime, however, they must have an identical data input and output specification in order for them to be used interchangeably.

The number of deployment versions you can have in your organization and projects is limited and varies per plan. If you have a single deployment, but have 5 versions of it, the total number of deployment versions is equal to 5.

We support all major credit cards. Other payment methods (iDeal for example) upon request.

Subscription fees are billed on the first day of your monthly subscription cycle.

All prices mentioned are excluding VAT. Local VAT will be applied for customers from the EU. Except for customers outside of the Netherlands with a valid VAT-number (“reverse charge”).

Enterprises requiring tailor-made subscriptions, for example with increased service levels, bigger compute packages or expert training, contact us for details.

Best effort support means that we will try to help you as best as we can with any issues you experience or questions you have. Even though we might need a bit more time to respond and cannot always guarantee a resolution.

You can reach us via our online support portal, email or our slack community. 

For priority support and guaranteed performance, we offer extended service levels. Contact us to discuss which option suits you best and learn about prices.

You need compute credits to be able to make requests to your deployments and have them work for you; you need a positive compute credit balance in your organization.

When you have spent all your compute credits, you will no longer be able to make requests to your deployments.

We calculate compute credits spent as the server memory (in Gigabytes) that you allocated to your deployments multiplied by the time that these deployments are actually running (in hours). In other words, how much time and how much memory our servers need to run your deployments. Taking into account all the deployments in your organization. Deployments running on GPU’s use 3 compute credits per Gigabytehour. 

The longer your deployment requests take, the longer the runtime and the more compute credits are used. The more memory your deployments need, the more compute credits are used. The more deployments you have running, the more compute credits are used.

The runtime includes the (cold) start time, total uptime and shutdown time of a deployment version instance. As well as the time needed to validate your deployment during creation (i.e. file upload). Note that when you set “minimum number of instances” for your deployment to a value other than zero, it will be constantly running.

There is no limit on the number of requests you make. Or on the size of your inputs or outputs. This to make things simple. A fair-use policy applies though.

Your compute credits are automatically reset on the first day of the next monthly billing cycle, to the amount of monthly credits in your subscription.

Compute credits remaining at the end of a monthly billing cycle are not carried over to the next month. 

Compute credits cannot be shared between organizations or redeemed for money.

Need more compute credits? You can adjust your subscription at any time. Changes made to the monthly compute credits in your subscription will be applied immediately after we received your payment. Compute credits and corresponding fees are calculated and billed pro-rata, based on the remaining days in the monthly billing cycle.

Not sure how many monthly compute credits you need? Talk to one of our experts. We have plenty of examples of deployments and their compute usage. Ranging from simple scripts which take a few milliseconds to compute to neural nets requiring hours to deliver their results. We’re certain that we’ll be able to help choose the right plan. 

The free monthly compute credits included in the Pay-as-you-grow plan apply only to the first user. Additional users do not come with additional free monthly compute credits.

See https://ubiops.com/docs/miscellaneous/platform-limits/ for more information on the more technical usage limits in UbiOps.