Skip to main content
Credits are spent in two ways: when working on the Canvas and when jobs run. On Less, you can choose how much power you want to use for sessions and for jobs. The more power you use, the more credits you spend.

​
Instances and Credit usage

You spend credits faster on larger instances. On a Micro instance, you will use 0.1 credits per hour. On a X-Large instance, you will use 8 credits per hour.
A couple of examples:
  1. You use a Micro instances for 10 hours on the Canvas. You will use 10 * 0.1 credits = 1 credit
  2. You use a X-Large instance for 26 minutes on the canvas. You will use 26/60 * 8 credits = 3.46 credits
  3. You have a source that updates every hour. It runs for 4 minutes on a Medium instance. You will use 4/60 * 2 credits = 0.13 credits for each job and 0.1333 * 24 = 3.2 credits for the day (i.e. 24 jobs)
  4. You have an orchestration that runs once per day. The orchestration runs for 7 minutes and activates 2 jobs:
    1. Job 1 runs for 3 minutes on a Medium instance. You will use 3/60 * 2 credits = 0.1 credits
    2. Job 2 runs for 4 minutes on a Small instance. You will use 4/60 * 1 credits = 0.06 credits
    3. Your orchestration job runs for 7 minutes on a Micro instance. You will use 7/60 * 0.1 credits = 0.01 credits
    4. You will use 0.1 + 0.06 + 0.01 = 0.17 credits per run

​
Canvas

When you open new model, we create a session for you. You can see which session you’re using next to the title. You can track how much power you’re utilising of that instance with the metrics (see below).
Read more about instances and credit usage on the canvas here.

​
Jobs

When you schedule a source, model or orchestration to run, it becomes a job. Every time it runs, it uses credits. You can choose which instance to use for your job when editing a source or a model. Orchestrations always use a micro instance to run (obviously the individual jobs use their own specified instances - think of the orchestration as a “background”/meta job).