Skip to main content
Your Purna account includes resource quotas that determine how much you can use each month. This page explains what each resource means, how it is measured, and what to expect.

​
Overview

Queries

Daily new conversations

AI credits

AI usage across conversations and workflows

Compute

Code execution and job runtime

Storage

Uploaded files and generated outputs

Users

Team members on your account

Capabilities

Tool access controlled by plan

​
Queries

Queries are the number of new chat conversations you can initiate per day. Continuing an existing conversation does not use another query. Queries reset daily at midnight UTC.
If you are running low on queries, continue working in an existing conversation instead of starting a new one. Follow-up messages in the same chat do not count as additional queries.

​
AI credits

AI credits represent usage of the models that read your requests, process context, and generate responses. Credit usage is based on the amount of model input and output processed during a session. Longer conversations, large file context, detailed outputs, and multi-stage workflows generally use more credits than focused questions. What can count toward AI credits:
  • Your messages and prompts
  • Purna’s responses, including formatted text, tables, and citations
  • Conversation, file, and tool context processed by a model
  • Summaries or extracted content from referenced files
Your available credits and reset schedule depend on your plan. Monitor current usage in Settings.

​
Compute

Compute measures how long private execution environments run for Code Execution and background jobs. By default, code execution provisions a private server attached to your chat session. Background jobs use isolated cloud sandboxes for longer workflows.

​
Compute Runtime and Biocompute Runtime

A single query can involve more than one type of underlying process. Purna meters each part of the run separately according to the type of runtime that performs the work.

Compute Runtime

Covers general computation and data-handling tasks, such as retrieving information from databases, preparing or transforming data, and executing general-purpose code.

Biocompute Runtime

Covers specialized biological computation, including structural predictions and genomic, proteomic, and multi-omic analyses.

​
How mixed queries are billed

When a query uses both runtime categories, each operation is billed under the category that performed that portion of the work—not under one category for the query as a whole. For example, a query might first retrieve a protein sequence from UniProt and then use Boltz-2 to perform structural analysis:
Only the Boltz-2 portion is charged as Biocompute Runtime. The UniProt retrieval is charged as Compute Runtime, even though both operations were requested in a single query.
How compute is metered:
  • Active execution time is counted while code or jobs are running
  • Paused or idle resources do not continue consuming runtime once shut down
  • Long-running jobs and large analyses use more compute than quick transformations
Keep related analysis in the same chat when possible. Follow-up code execution can reuse context and reduce repeated setup time.

​
Storage

Uploaded files, generated artifacts, job outputs, images, and exported datasets count toward your storage quota. Storage is measured as total disk usage across your account. Common storage contributors include:
Deleting a file removes it from your Files library and helps reclaim storage. Generated outputs attached to a job or chat may still be represented in the conversation history.

​
Users

Users are team members on your account. Each user gets their own login, chat history, private files, and access controlled by project and team settings. User management is available in Team settings. Invite new members, assign roles, and decide which work should be private or team-visible.

​
Tools and capabilities

Tools and capabilities are controlled by your plan and the controls beside the message composer. Use Capabilities for actions and Skills and knowledge for scientific sources and connected research context. Some entries are available to every account, while more resource-intensive tools may require a paid plan or provider approval. Examples include:
  • Web and database search
  • Code execution
  • Background jobs
  • Image and figure generation
  • Deep Research
  • Consilium
  • Paper Writing
If you need a specific integration that is not currently available, contact contact@purna.ai and we will work with you to evaluate it.

​
Enterprise

Enterprise customers can request additional capabilities beyond standard plans.
Connect professional databases, licensed reference data, internal datasets, or organization-specific knowledge sources.
Request custom pipeline configurations, larger compute environments, dedicated job templates, or specialized infrastructure.
Configure organization-level controls, support workflows, team administration, and enterprise deployment requirements.
To discuss enterprise options, reach out to contact@purna.ai.