IAM Group · Product Portfolio

Product portfolio 02

The security wedge enters through traffic control; the portfolio creates expansion and platform moat

IAM products in the public catalogue

families by buyer job

markets — B2B core + B2C option

IAM Group is not 14 unrelated startups. It is a composable portfolio: products sell standalone, while shared identity, policy, routing, runtime and evidence increase the value of using them together.

Source: iamgroup.ru/#atlas; as of 05.08.2026. Figures describe portfolio shape, not traction.

Product portfolio 03

Each product solves a distinct job; the platform emerges where connectedness is required

Control & Trust

Core · Router
Secure · Identity

Policy, routing, access, audit

Build & Run

Agent · Marketplace
Hosting

Build, package, run

Knowledge

Docs · Bot

Sourced knowledge → dialogue and action

Communications

Comm · Meet
Voice · Speech

Media, conversation, recording, analytics

Personal AI

Mind

Local memory and a professional workspace

Sister product · AGL — Architecture as Code: DSL, diagrams, docs, code / IaC, drift detection. Connected to IAM through artefacts and MCP, not as a Core module.

Evidence-based status 04

Working surfaces are deployed, but we present maturity conservatively

Deployed

controlled use

Core · Identity · Router*
Secure · Comm · Bot

There is a production deployment or a working use case. *Router: non-stream confirmed, streaming needs remediation.

Pilot-ready

verified

Docs · Voice · Speech

Functionality and scenarios are confirmed, but commercial, security or scale readiness is limited.

Release candidate

product

Agent · Marketplace
Hosting · Meet

A working runtime or preview exists; packaging, hardening, billing and distribution remain before GA.

AlphaPreview

early

Mind

Local memory, citations and privacy controls. Mass B2C, installer and team layer are not claimed yet.

Status reflects a specific surface and its evidence as of 05.08.2026, not a promise about the whole suite.

Control & Trust 05

Control & Trust answers two enterprise questions: what may be sent, and where

Deployed

Registry, tools, agent sessions
Auth / tenant context, route, audit
A single agent / API / MCP fabric

Production SSO

Users, tenants, roles, sessions
OIDC / SSO, scope isolation
Federation and device flows are maturing

Conditional

Sensitivity → policy route
local / on-prem / external
Residency, provider and cost control

Deployed

Prompt / response / tool inspection
DLP: mask, block, reroute
Shadow AI, audit, SIEM export

Build & Run Agents 06

Agent, Marketplace and Hosting create a path from tool to ecosystem

01 · BUILD

Chat · Cowork
Code · MultiWork

→

02 · PACKAGE & DISCOVER

Catalogue · install
moderation

→

03 · DEPLOY & GOVERN

Runtime · lifecycle
wake / reap

B2C / prosumer potential. Personal automations → curated agent packs → creator ecosystem. The initial wedge is first-party scenarios and one-click install; an open marketplace is the next stage.

Knowledge 07

Docs and Bot turn knowledge from an archive into an interface for decisions

Functional B2B pilot

OCR and intake of contracts / scans
Hybrid search and structured extraction
Answers with supporting excerpts
Legal · procurement · finance · R&D

Deployed use case

RAG dialogue over knowledge
Qualification and funnel stage
Citations + handoff to an operator
Web · Telegram · CRM / webhook

DOCUMENT
↓
CITED ANSWER
↓
DIALOGUE
↓
CONTROLLED ACTION

B2C / pro option:
private archive + Mind

Communications 08

Comm, Meet, Voice and Speech form a loop — from conversation to evidence

Deployed foundation

SIP / WebRTC control, sessions, TURN, tenant isolation

Controlled preview

Video, screen share, waiting room, moderation, PWA

Advanced pilot

ASR / VAD → scenario / LLM → TTS → human handoff

Pilot evidence

ASR, diarization, QA evidence, reports / fact tables

MEDIA→LIVE DIALOGUE→RECORDING→TRANSCRIPT→QA EVIDENCE

Personal AI · sister product 09

Mind opens a local-first B2C / pro path; AGL adds developer acquisition

AlphaPreview

Owner-scoped memory · citations · restart / deletion
B2C: subscription for engineers and researchers
B2B: private R&D workstation; team layer later

Sister product · AGL

Git-first AaC: diagrams · docs · code / IaC
MCP / IDE integration + drift detection
B2B architects; OSS / prosumer acquisition wedge

Product strategy 10

Five outcome packages simplify selling fourteen technologies

Protected AI Access

Identity + Secure + Router

Where data goes, what is allowed, who has access

Governed Agent Delivery

Agent + Marketplace + Hosting + Secure

Build, publish and run an agent under policy

Knowledge → Action

Docs + Agent + Core

Cited evidence becomes a controlled action

Contact Center Loop

Comm + Voice + Speech + Bot

Dialogue, handoff, recording, QA and follow-up

Local Professional AI

Mind + Agent

Personal memory and working agents; still a growth hypothesis

Product strategy recommendation · we sell outcomes and reveal modules during solution design.

Enterprise sales motion 11

One security wedge creates a sequential path from assessment to platform

01 · ASSESS

Exposure Assessment

AI flows · data classes · risks

02 · ENFORCE

IAM.Secure

Inspect · policy · evidence

03 · ROUTE

IAM.Router

Perimeter · provider · model

04 · EXPAND

Identity + Core

Actor · tenant · orchestration

05 · PLATFORM

Agent + Hosting

Governed runtime · lifecycle

Evidence gates · paid assessment → pilot conversion → production traffic → module expansion.

Commercial wedge 12

AI Traffic Control is the primary commercial wedge; the portfolio becomes its expansion layer

Why this is a timely B2B wedge

An urgent board-level problem: uncontrolled enterprise AI
Clear buyers: CISO, CIO, AI platform and data leaders
Verifiable output: traffic map + policy + route evidence
Expansion into Identity, Core, Agents and Hosting

LAND

Exposure Assessment

Traffic inventory · risk map · target policy

ENFORCE

IAM.Secure

Inspect · allow / mask / block · audit

ROUTE

IAM.Router

Perimeter · provider · model decision

PLATFORM

Identity + Core

Actor context · orchestration · expansion

Product recommendation · security-first focus, not a claim about current revenue or scale.

Go-to-market 13

Four segments give different entry points while reusing the same capability layers

Segment	Land product	Buyer job	Expansion
Regulated enterprise	Router + Secure	Control AI traffic and data	Identity · Core · Docs
Contact centers	Speech	QA and evidence for conversations	Voice · Comm · Bot
Engineering / R&D	Agent + Docs	Working AI inside a private perimeter	Secure · Hosting · Core
Professionals	Mind	Personal memory and automations	Agent · Marketplace · Team

Focus principle · pick two primary segments; keep the rest as adjacent potential.

Monetisation hypotheses 14

Monetisation can combine seats, usage, platform fee and Marketplace

Per seat

Mind · Agent · Meet

Validate willingness-to-pay and retention.

Usage

Router · Secure · Speech
Voice · Hosting

Measure cost-to-serve per workload.

Platform

Core · Identity · Docs · Bot

Annual / monthly subscription + limits.

Marketplace

Take rate / revenue share

Only once supply and demand exist.

Dedicated / on-prem

Deployment fee + support

Separate product from implementation.

Support / SLA

Enterprise tier

After the reliability envelope is confirmed.

Pricing tests

Interviews · pilots · packaging

Gross margin by workload type.

Not a financial model

Pricing validation required

No invented prices, ARR or unit economics.

Potential moat 15

The moat comes from connectedness and operational assets — not individual features

Policy

Identity · DLP · routing

A single model for permissions and audit

Runtime

Core · Agent · Hosting

Contracts, lifecycle, evidence

Distribution

Marketplace · Mind

Creator and user acquisition loops

Potential moat — depends on adoption. A standalone gateway, RAG or agent is copyable. It is harder to reproduce compatible policy, runtime, identity, deployment evidence, integrations and a distribution loop once they accumulate around real workflows.

Proposed roadmap 16

The next 18 months convert technology into three repeatable products

0–6 MO.

Prove

Cross-product UX
Vertical templates
Deployment automation
Lighthouse evidence

6–12 MO.

Package

Canonical readiness
3 solution packages
Onboarding + demos
Pricing discovery

12–18 MO.

Distribute

Curated Marketplace
Developer / creator program
B2C → team experiments
Ecosystem metrics

Source: IAM Group product strategy recommendation; as of 05.08.2026. Horizons are a proposed roadmap, not a commitment.

Use of proceeds 17

Capital turns technology into products, evidence and distribution

Product

Leadership · UX
Packaging · onboarding
Shared reliability

Evidence

Security / compliance pack
Pilots · pricing research
Architecture / IP room

Distribution

Solution GTM
Partners · developer ecosystem
Customer success

The investment task: not to widen the catalogue, but to assemble a limited number of repeatable solutions with transparent readiness, measurable value proof and controlled unit cost.

Enterprise AI Traffic Control

The security wedge enters through traffic control; the portfolio creates expansion and platform moat

Each product solves a distinct job; the platform emerges where connectedness is required

Working surfaces are deployed, but we present maturity conservatively

Control & Trust answers two enterprise questions: what may be sent, and where

Agent, Marketplace and Hosting create a path from tool to ecosystem

Docs and Bot turn knowledge from an archive into an interface for decisions

Comm, Meet, Voice and Speech form a loop — from conversation to evidence

Mind opens a local-first B2C / pro path; AGL adds developer acquisition

Five outcome packages simplify selling fourteen technologies

One security wedge creates a sequential path from assessment to platform

AI Traffic Control is the primary commercial wedge; the portfolio becomes its expansion layer

Four segments give different entry points while reusing the same capability layers

Monetisation can combine seats, usage, platform fee and Marketplace

The moat comes from connectedness and operational assets — not individual features

The next 18 months convert technology into three repeatable products

Capital turns technology into products, evidence and distribution

Thank you