sha.chatPERSONALFriends · Family · Private wallet
PROFESSIONALTeams · Corporate directory · Policy
Messaging containers
Separate contact graphs and credentials create a real boundary between personal life and professional obligations.
Most of this page is still in English. Its Kugg text is being written.
Product · Personal / Professional
Two worlds,
yours by design.
sha.chat separates personal messaging from professional communication, contacts and transactions—then places calls, wallet actions, transactional agents and built-in LLMs inside the right context.
The interactive preview needs JavaScript.
preview · sample
Containerization, not cosmetic folders
Personal stays personal.
Professional stays governed.
Each container is designed to carry its own identity context, contact list, wallet permissions, agent delegations and LLM access. Preventing data from crossing between personal and professional spaces is a release requirement.
Corporate messaging can apply verified directories and regulatory policies without taking control of personal conversations or personal contacts.
Calls in context
Voice and video calls begin inside the correct container, preserving the conversation, identity and policy context around them.
Calls architecture →CONTACT→AGENT→REVIEW→SIGN
Transactional agents
Agents can prepare transfers, answer wallet questions and coordinate agent-to-agent workflows. Scoped delegation and explicit review remain between intent and execution.
LLMmemorytoolspolicy
Chat LLM built-ins
LLMs answer inside the thread. Model access, memory, tools and permitted data follow the active container instead of leaking across contexts.
Agentic team management
Coordinate inside the right space.
Agentic team management → Orchestrator → Agentic team
Configure scoped agents and their tools inside Personal or Professional. Delegation follows the active space; consequential actions remain subject to explicit review.
Explore modules with the assistant →Corporate policy layer
Split contact lists.
Clear regulatory boundaries.
Verified professional directoryCorporate contacts belong to the governed workspace, not the personal address book.
External-contact controlsOrganizations can define who may be contacted and which external domains are permitted.
Transaction policyThresholds, review steps and signing permissions travel with the professional container.
Scoped AI accessProfessional LLMs and agents receive only the tools and context authorized for that workspace.
Whitepaper principle
Identity = wallet = contact.
A sha.chat handle resolves the cryptographic identity used for messages, payment-channel updates and scoped agent delegation—inside the container where that identity is allowed to act.
Read the architecture →