The layer underneath all seven modules.
Anyone can ship a chatbot. The difficult part is the substrate beneath it — one resolved customer record, one set of grounded sources, one permission model, one measurement layer. That substrate is the product.
Four layers, in order.
Modules sit on top. Everything below them is shared, which is why the second module costs a fraction of the first.
Modules
The seven products. Each one is a set of behaviours, surfaces, and reports on top of the same foundation.
Orchestration & guardrails
What an agent may do, when it must confirm, when it must hand over, and how it is judged. Written once, applied everywhere.
Permission model
Per-action scopes and value thresholds, per module and per channel.
Escalation policy
Confidence thresholds, restricted intents, and routing rules to the right human.
Evaluation harness
Test sets from your own history, run before rollout and continuously after.
Grounding
Your catalog, policies, macros, and documentation, structured so an answer can always be traced back to the source it came from.
Source of truth
Policies and catalog data, versioned — so fixing a wrong answer means fixing a document once.
Citation
Every response carries the record it was derived from, visible to your team.
Conflict detection
Contradictory policies surface during onboarding, which is usually the first useful output.
Data & identity
Connectors into the systems you run, identity resolved into one profile per customer, with the full journey attached. Every layer above reads from here.
The second module is the cheap one.
The first module you deploy pays for the connectors, the identity resolution, the grounded policy set, and the permission model. Those are the expensive parts, and they are shared.
Every module after that inherits them. It is also why the modules get better together rather than merely coexisting — Uplift knows what Resolve just promised, Dial knows what Loop tier the caller is in, Atlas sees all of it.
Resolve + Uplift
A support conversation that ends in an accepted recommendation, measured as one journey rather than two systems claiming credit.
Dial + Loop
The voice agent knows the caller's tier and history, and can offer the reward that actually fits them.
Atlas + everything
One definition of repeat rate and margin, used by every module, so the numbers in two dashboards stop disagreeing.
Mesh + Forge
Custom internal agents coordinating through the same protocol layer as external ones, instead of point-to-point glue code.
Runs where your governance requires.
Managed cloud
The default. Fastest to deploy, with region selection for data residency.
Your cloud (VPC)
Deployed into your own environment where your policy requires it. Available for enterprise engagements.
Defined residency
Data stored and processed in a region you specify, with retention windows you set.
Bring your specific compliance requirements to the scoping call. We would rather tell you plainly what we do and do not support than discover the gap during procurement. Read the security overview
Walk through the architecture with us.
Bring your stack diagram. We will tell you what connects cleanly, what needs work, and what we would sequence first.