Separate team workspaces
Scrims, VOD, strategy, tasks, chat, and permissions remain scoped to the team that owns the work.
Product for organizations
Run every roster without flattening how teams work.
Give each VALORANT team its own kogni workspace, then add an organization layer for plans, permissions, activity, and operational visibility across the club.
Team workspaces stay independent. Organization owners gain the shared view above them.
The organization layer
Central control without a shared-data mess.
Each roster keeps its own review workflow while authorized organization staff see the signals needed to coordinate resources and support.
One organization view
Track activity, roster pressure, practice rhythm, and workspace health without entering every team manually.
Plans per roster
Mix Entry and Pro teams in the same organization and match the product level to each roster's needs.
Operating model
One club. Multiple team realities.
The organization does not replace team workspaces. It connects them through a controlled management layer with organization owners, team owners, and scoped roles.
- Independent roster data and team workflows
- Organization-level ownership and administration
- Cross-team signals only for authorized roles
- Entry or Pro assigned independently per team
Organization
Shared management layer
Owners, plans, access, and health signals
Organization capabilities
The controls a multi-team operation actually needs.
Workspace administration
- create and manage multiple teams
- organization and team owner roles
- team invitations and scoped access
- advanced role permissions
Cross-team visibility
- workspace activity and engagement
- practice cadence and review rhythm
- roster pressure and member limits
- team health signals
Flexible plans
- mix Entry and Pro teams
- organization rate per managed team
- monthly or yearly billing
- combined organization setup
Team-level product
- PRACC history and analytics
- VOD LAB and round evidence
- AI-assisted review on Pro
- strategy and team operations
Security boundaries
- team-scoped data by default
- authorized organization oversight
- local Riot session handling
- role-based administration
Private deployment
- private hosting and storage
- custom routes or subdomain
- optional SSO or SAML
- custom retention, integrations, and SLA
Custom organizations
Need a private kogni environment?
Custom deployments can add private infrastructure, branded routes, dedicated parser delivery, identity integrations, retention requirements, and a scoped support model.
Build the organization above your team workspaces.
Start with at least two Entry or Pro teams, choose each roster's plan, and keep every team's work properly scoped.