Skip to content
Akurion Akurion
Docs

Plans

Plans

Akurion uses credits to meter document processing, retrieval, answer generation, API usage, MCP tool calls, and workflow execution. Plans are designed to support pilots, growing teams, and enterprise deployments.

Free Trial

Best for evaluating Akurion with a small project and sample data.

Included:

  • Starter credits.
  • Project creation.
  • File upload.
  • Core chat and cited answers.
  • Access to available data source setup flows.
  • API key creation for testing.

Team

Best for a department or team using Akurion on active internal knowledge.

Typical needs:

  • More processing credits.
  • Multiple projects.
  • Team members and roles.
  • Connected enterprise data sources.
  • Metadata configuration.
  • API and MCP usage.
  • Usage analytics.

Business

Best for organizations deploying Akurion across multiple teams and knowledge domains.

Typical needs:

  • Larger credit allocation.
  • More projects and users.
  • Source health visibility.
  • Prompt playbooks and workflows.
  • Graph RAG for selected projects.
  • Subscription-level API keys.
  • Organization administration.

Enterprise

Best for regulated, high-volume, or custom deployments.

Enterprise packages can include:

  • Custom pricing and usage commitments.
  • Higher limits.
  • SSO configuration.
  • Security and procurement support.
  • Custom onboarding.
  • Connector planning.
  • Workflow and API integration support.
  • Optional custom deployment discussions.

Contact sales@structhub.io for enterprise packaging.

Credits

Credits are consumed by platform work such as:

  • File discovery and processing.
  • Text extraction.
  • Metadata generation.
  • Embedding and indexing.
  • Chat and answer generation.
  • MCP tool calls.
  • Workflow runs.
  • Graph build activity.

Credit usage depends on source size, file formats, retrieval depth, model usage, workflow complexity, and tool selection.

Choosing a Plan

Start with a small pilot when:

  • You are evaluating one team or one knowledge domain.
  • You want to test answer quality and citations.
  • You want to prove source connectivity.

Move to a larger plan when:

  • Multiple teams need access.
  • You need recurring syncs and workflows.
  • You need API or MCP integration in production.
  • You need governance, SSO, and admin reporting.