Credits
Credits are the unit Diafunc uses to measure, control, and limit the use of computing resources. A credit is a normalized unit of computing power that can be consumed across almost every part of the platform: storage, compute, entities and links in the project graph, data transfer, the conversational assistant, and more.
Where credits are spent
Every resource-consuming operation on the platform draws credits independently. The table below lists the approximate quantity structure behind one credit; the rates are not fixed and may evolve.
Usage is not always calculated exactly: some rates are based on estimates or samples. The goal is a fair distribution of resources and pricing rather than per-byte precision.
Full breakdown on the Credits page Pricing
| Resource | Approximate rate per credit |
|---|---|
| Compute | 1 vCPU for 1 minute. This is how function evaluations, symbolic regression runs, and automatic analyses all meter. It is the processor time actually consumed, not the time an operation takes: a function waiting while a model is computed is charged for that computation, not for the wait. |
| Storage | Up to 1 MB of storage for up to 1 month |
| Transfer | Up to 1 GB of transferred data |
| Actions | Up to 1,000 performed actions |
| Entities | Up to 1,000 entities stored for up to 1 month |
| Links | Up to 1,000 links stored for up to 1 month |
| Events | Up to 1,000 created events |
| Assistant input tokens | Up to about 60,000 tokens sent to the conversational assistant (prompts, context, and history) |
| Assistant output tokens | Up to about 15,000 tokens generated by the conversational assistant (its replies) |
| Support | Up to 1 support request message |
Usage is not always calculated exactly: some rates are based on estimates or samples. The goal is a fair distribution of resources and pricing rather than per-byte precision.
Subscription and extension packs
Every account has a subscription plan that issues a defined number of credits at the start of each billing cycle. On the Ultimate Plan, Ultimate Extension Packs add further credits: each pack issues its own per-cycle allocation on top of the plan.
The cycle runs monthly from your subscription's anniversary, not from the first of the calendar month: sign up on the 14th and your allowance refreshes on the 14th of every month. The Usage page names the exact date.
Credits must be used in the cycle in which they were issued. Unused credits expire automatically when the next allowance arrives and cannot be carried over or transferred.
The cycle runs monthly from your subscription's anniversary, not from the first of the calendar month: sign up on the 14th and your allowance refreshes on the 14th of every month. The Usage page names the exact date.
Credits must be used in the cycle in which they were issued. Unused credits expire automatically when the next allowance arrives and cannot be carried over or transferred.
Running out of credits
If your credits are exhausted, your active projects are temporarily locked: running analyses, function evaluations, and the assistant stop, and new ones can't be started. Existing data remains untouched and visible. Diafunc sends a one-time email when this happens, and the Lab surfaces a banner explaining what is paused and how to resume.
Projects are unlocked automatically the moment your credit balance is positive again, either on the next monthly refresh or as soon as an extension pack takes effect.
Projects are unlocked automatically the moment your credit balance is positive again, either on the next monthly refresh or as soon as an extension pack takes effect.