Teams
The Jorv Builder Team tier is $39/seat/month and adds shared brainstorms, team experts, audit export, and seat management on top of the Solo cockpit. BYOK at every seat — no shared key pool, no team-wide token cap.
This page covers what's included, how to set it up, and the operational notes for running a team installation.
What's included
Shared brainstorm artefacts
When one seat creates a brainstorm, every seat on the same workspace can see it (read-only by default, editable with permission). This is the main collaboration primitive — brainstorms become a shared design artefact rather than a per-developer doc.
Team experts
Define custom Expert Audits for your team. Each expert is a markdown spec describing:
- Domain (e.g. "Internal Stripe SDK conventions")
- Triggers (file patterns, PR labels)
- Review criteria (markdown rubric)
- Severity mapping
Team experts run alongside the 21 built-in Expert Audits. They're seat-aware: a Solo-tier user calling a Team-tier audit gets a clear upgrade prompt.
Audit export
Export PROV chain in CSV, JSON, or markdown. Useful for:
- Pulling weekly engineering metrics
- Feeding the audit chain into your SIEM / log aggregator
- Generating retrospective summaries
Triggered from Compliance Center → Export or via the export CLI.
Seat management
The Team admin dashboard at https://jorv.ai/team/<workspace> (Team tier) shows:
- Seat list with per-seat status (active, idle, suspended)
- Per-seat provider spend (BYOK metering from provider APIs)
- Team experts catalogue
- Workspace settings
Invite via email; SCIM provisioning is available on Enterprise tier.
Setting up a workspace
- Buy seats — visit /pricing?tab=builder and contact us for Team. (Self-serve checkout in Phase 4 of the strategy refresh.)
- Create workspace — admin runs the workspace setup wizard in Jorv Builder → Settings → Team.
- Invite seats — admin emails invites; each seat installs Jorv Builder, signs in, and adds their own BYOK keys.
- Configure shared brainstorm root — workspace setting points at a git repo (or directory) where brainstorms persist.
BYOK at the seat level
Every seat brings their own keys. There is no team-wide key pool by default. This matches what most teams already do (per-developer cloud accounts; per-developer provider billing) and avoids the principal-agent problem of "whose API key got rate-limited."
For teams that want a shared key pool — usually for corporate billing reasons — the Enterprise tier adds Corporate-BYOK admin tooling. See /docs/byok-setup#corporate-byok-enterprise-tier.
Operational notes
Brainstorm conflicts
Multiple seats can edit the same brainstorm. Conflicts are resolved with the usual git-style merge tooling. The PROV chain records all edits.
Per-seat audit identity
Each seat has a distinct audit identity. Brainstorms, approvals, merges all carry the identity in the PROV chain. Two-key merge (Enterprise tier) checks identities are different.
Removing a seat
When a seat leaves:
- Their Jorv Builder local install can still open projects they have read access to (BYOK keys are theirs).
- The Team admin revokes their workspace seat — they lose access to shared brainstorms and team experts.
- Their PROV history remains in the chain (you can't tamper with the audit log) but their account is marked
inactive.
Pricing math
For a 5-seat team:
- 5 × $39/mo = $195/mo licence
-
- 5 × per-seat provider spend (BYOK, paid to Anthropic / OpenAI directly)
Compare to Cursor Business (5 × $40 + token overage) or Copilot Enterprise (5 × $39 + LLM caps). The crossover for moderate use is around month 1.
Further reading
- /builder/pricing
- /docs/byok-setup#corporate-byok-enterprise-tier
- /docs/compliance — audit chain semantics