VectorMethods

Pricing

Pricing for plans and processing credits

Start free, upgrade to Starter or Pro through Stripe checkout, or scope an Enterprise plan with custom processing credits, workflow customization, and dedicated deployment options.

Free

A workspace for trying core search, prompt runs, and early schema design.

$0

No checkout required

10 video processing credits included
Entry-level API and processing throughput
  • Core search and processing workflows
  • Prompt runs for validation projects
  • Community support

Starter

For teams moving from evaluation into repeatable processing and API work.

Popular

$49/mo

Stripe monthly subscription

500 video processing credits included
Higher API and processing throughput
  • Connector, webhook, automation, and API key access
  • Email support
  • On-demand credit purchases

Pro

For production teams that need larger self-serve credit allocation and priority help.

$149/mo

Stripe monthly subscription

2,000 video processing credits included
Highest self-serve API and processing throughput
  • Priority support
  • Bulk review workflows for larger libraries
  • Larger recurring credit allocation

Enterprise

For governed deployments with custom rollout, infrastructure, and workflow requirements.

Contact us

Custom commercial terms

Custom video processing credit allocation
Enterprise API, search, and processing limits
  • Bulk processing and archive-scale onboarding
  • Upstream and downstream workflow customization
  • Dedicated instances, SLAs, and support alignment

Commercial model

Plans combine recurring access, included processing credits, and optional credit purchases.

Self-serve plans
Free, Starter, and Pro support validation, API usage, prompt runs, and paid Stripe checkout.
Credit packages
Buy additional video processing credits when a batch or rollout needs more capacity.
Enterprise deployment
Customize credits, bulk processing, integrations, infrastructure, support, and rollout plans.

What determines scope

Scope follows operational coverage, not a flat feature checklist.

  • Media volume and retention windows affect ingestion, search, reprocessing, and credit planning.
  • Workflow complexity matters when teams need bulk processing, automation, downstream handoffs, or cross-functional review paths.
  • Governance depth changes the rollout shape when security review, dedicated instances, legal review, or wider stakeholder access is required.

How teams move into production

Most teams start with one workflow, then expand once retrieval quality, schema design, and downstream usability are proven.

Enterprise planning usually centers on archive scale, cross-team handoffs, and rollout ownership.

Frequently asked questions

Explore related pages

Related workflows, technical foundations, and next steps.