HelpTokenHow to optimize your token use
Go back

How to optimize your token use

Understanding how to get the most out of Astell without burning through your tokens

TokenGuides

How far tokens go on each plan

Astell has four plans, Sapling, Tree, Grove, and Forest (Enterprise):

  • Sapling: free, 2,500 tokens/month, single seat (~500 document pages). Standard (Flash) model only, 3 months of indexed history. Best for solo users who want to find the right info fast.
  • Tree: $20/seat/month billed annually ($25 monthly), 10,000 tokens/seat/month (~2,000 document pages), 18 months of indexed history. Best for teams who need shared answers and richer media.
  • Grove: $80/seat/month billed annually ($100 monthly), 50,000 tokens/seat/month, 60 months of indexed history. Best for larger orgs with complex permissions and workflows, plus Ultra mode.
  • Forest (Enterprise): custom pricing and a customizable indexing window; contact founders@labtwofour.com.

On Tree and above, tokens are pooled at the organization level. Customized admin control over token consumption is available on Grove and Forest.

Reducing document-processing usage

The biggest savings come from processing less low-value content:

  • Use manual processing, turn off auto-sync and upload key documents only when needed
  • Limit the date range, sync the last 6–12 months; process older files only when needed
  • Review integrations quarterly, remove inactive sources and tighten selective sync over time

Planning the onboarding month

When onboarding a large workspace or importing historical files, the first month often needs far more tokens because Processed Data ingestion is what consumes them. To avoid ingestion pausing mid-onboarding, set a higher token limit for the first month so ingestion can continue beyond the included pool via pay-as-you-go. After the initial ingestion finishes, usage usually drops sharply. Native Data keeps syncing free, only new or changed Processed Data consumes tokens, and you can tighten selective sync once the backlog is done.

Reviewing usage and plan fit

Review token usage every 3 months: check average consumption, identify optimization opportunities, confirm your plan still fits, and update team policies based on real usage.

Selective sync

Selective syncing lets you keep the important data flowing while avoiding unnecessary processing. You can set date ranges (such as the last 12 months) and scope sync to specific folders, channels, or repositories, and exclude attachment types you don't want processed. Selective sync is available on all plans; what matters for token spend is how much Processed Data you choose to ingest, not which plan you're on.

Getting help with tokens

If you need help with token usage, email support@labtwofour.com with the subject "Token Usage Assistance" and include your usage patterns and the questions you're trying to solve. Enterprise customers also have access to quarterly usage reviews and custom optimization consulting.

Related Articles

Continue learning with these related help articles

  • Real-World Token Usage Examples

    Check out how many tokens are needed for different real-world teams

    Read
  • What costs tokens in Astell?

    Understand what chat and ingestion activities consume tokens

    Read

Managing Token Usage

How to set token limit and see usage reports.

Native vs. Processed Data

Understand the two types of data ingested and their respective costs.

On this page

How far tokens go on each planReducing document-processing usagePlanning the onboarding monthReviewing usage and plan fitSelective syncGetting help with tokens