Pricing / Routes / team-workspace

Team Workspace Pricing Route

A route type describes the purchase or access path. Pricing model, direct plan rows, purchase track, and pricing owner remain separate fields.

7 route facts · 5 tools
01

Route definition

Route taxonomy is about access path, not price level, ranking, buyer fit, or editorial guidance.
Definition

Multi-user workspace, collaboration, team, business, or organization billing route.

Use when

The purchase path is organized around workspace or team access rather than individual app access.

Do not use when

Team seats are only a feature inside a generic app subscription route.

02

Model coverage

Current formal records can combine this route with multiple commercial models. The model describes charging logic; the route describes the access path.
Models in current records

Observed commercial models

Canonical model patterns

Expected model contexts

03

Route facts

Route rows carry source URL, checked date, primary marker, and optional pricing owner boundary.
toolroute labelprimarypricing modelstarting priceunitpricing ownersourcechecked
GitHub Copilot
github-copilot
Primary official pricing routeprimaryHybrid$10monthCurrent entitygithub.com/features/copilot/plans2026-05-07
LangSmith
langsmith
DeveloperprimaryHybrid$39monthCurrent entitywww.langchain.com/pricing-langsmith2026-05-06
LangSmith
langsmith
PlusNoSeat Based$39 / seat per monthseat/monthCurrent entitywww.langchain.com/pricing-langsmith2026-05-06
Pinecone
pinecone
BuilderNoSubscription$20/monthmonthCurrent entitywww.pinecone.io/pricing/2026-05-06
Pinecone
pinecone
StarterNoFree$0Not presentCurrent entitywww.pinecone.io/pricing/2026-05-06
Salesforce
salesforce
Primary official pricing routeprimarySeat Based$25month billed annuallyCurrent entitywww.salesforce.com/sales/pricing/2026-05-07
Tabnine
tabnine
Primary official pricing routeprimarySeat Based$39month billed annuallyCurrent entitydocs.tabnine.com/main/welcome/readme/tabnine-subscription-plans2026-05-07
04

Evidence and ownership

Route facts should be source-backed. Missing source or owner fields stay visible rather than being inferred.
Route facts
7

Current records with this canonical route type.

Primary routes
4

Tool records where this route is the primary pricing route.

Source URLs
7

Route facts with a route-level source URL.

Owner boundaries
0

Route facts where exact prices belong to another canonical entity.

05

Evidence requirements

These requirements prevent route pages from becoming unsupported pricing claims.
Required evidence

Official team/workspace pricing source

Required evidence

Seat or workspace boundary

Required evidence

Pricing checked date