Context: Personal context
EcosystemA map of products and links
See how it works
in your exact case.
Pick a user type — the map shows the matching products, shared system components, the external systems that remain sources of truth, and the access boundaries.
Center — HummerFabricRing — the productsOuter ring — sources of truth
Hover or focus a product to read its role. External systems remain sources of truth and connect via Hummer Bridge.
Scenarios
Ten user types
The same set of technologies looks different depending on who uses it.
Mail, calendar, drives, banks, stores and delivery services remain your services.
AiHummer's rolePersonal agents work only in the personal context and never leave its boundaries.
Access boundariesThe employer and third-party apps see no personal data without explicit consent.
Context: Family context
A shared calendar, documents, trips and subscriptions assemble from the same personal services.
AiHummer's roleThe agent helps plan and remind, acting on behalf of a specific family member.
Access boundariesAccess is granted per member and revoked in one click.
Context: Professional context
The bank, the tax app, messengers, calendar and documents are the sources of truth.
AiHummer's roleAn AI team handles correspondence, prepares documents and tracks commitments.
Access boundariesProfessional data is separated from personal, and financial actions are confirmed.
Context: Professional context
The bank, accounting, e-documents and point-of-sale services stay where they are.
AiHummer's roleAgents reconcile payments, remind about deadlines and prepare documents.
Access boundariesThe right to initiate a payment is granted separately and is off by default.
Context: Corporate context
CRM, 1C, the bank, e-documents and communications connect once at the organization level.
AiHummer's roleAI employees get roles alongside people and work in the shared customer card.
Access boundariesRoles define who sees the money and who sees only their own customers.
Context: Corporate context with departments
CRM, ERP, e-documents, BPM, banks and office suites; an external BPM can own the process.
AiHummer's roleCross-functional agents work where the process crosses departments.
Access boundariesPolicy hierarchy: company rules are refined by a department but never weakened.
Context: Holding, legal entities, departments
SAP, Oracle, 1C, industry and internal systems via the Connector SDK.
AiHummer's roleAgents and models run inside the organization's perimeter via a private AI Gateway.
Access boundariesSegmentation by legal entity and region, with the Proof Ledger for provability.
Context: Portal context
Data shows as a permitted slice from CRM, ERP, e-documents and Service Desk.
AiHummer's roleThe portal assistant answers within one counterparty's data boundaries.
Access boundariesAn external party never enters the organization's internal systems.
Context: App context
Your app, your services and MCP servers connect as ecosystem clients.
AiHummer's roleYour own agents connect via the Agent SDK and the AI Gateway.
Access boundariesAn app gets minimal permissions and sees only permitted scopes.
Context: Customer project context
The customer's landscape: accounting, industry and internal systems.
AiHummer's roleAgents are configured for the customer's processes and policies.
Access boundariesWork happens in the customer's perimeter under their access rules.
HummerAuth
Identity, contexts and consents.
HummerHome
Sign-in, search, decisions and continuity.
HummerFabric
Connections, context, policies and provability.
HummerStore
Verified extensions for any product.
Four paths
How data, actions, AI and permissions flow
The same in every product: only the context scale and policy strictness differ.
The data path
Data does not move into the ecosystem wholesale. Hummer Context stores permitted read models with the source and retrieval time.
The action path
A change always runs in the source system and is confirmed by its response. No shadow database is created.
AiHummer's role
AiHummer is native: it uses Context, Trust, Proof and Flow directly. Third-party agents connect via API, MCP and adapters with limited permissions.
Access boundaries
Access is defined by six levels at once. Only the data owner or the organization's policy can loosen any of them.
The ecosystem's boundaries
What HummerTech will not do
The limits are fixed in the approved concept and do not change from product to product.
Does not replace mature systems
1C, CRM, the bank, e-documents, mail and BPM remain the sources of truth. The ecosystem connects them — it does not displace them.
Creates no shadow database
Hummer Context stores permitted read models with provenance — not a copy of your ERP or CRM.
Never acts without authority
Every action is checked against policy; significant operations are confirmed by a human.
No artificial lock-in
Retention is built on accumulated convenience, not on locks. Export of documents and legally required data is provided.
Never passes plans off as facts
Products carry a status, integrations carry their own statuses, and hardware products are marked Vision.
Leaves open questions open
The first commercial product, the first ICP, the MVP integration set, the build order and the sales channel are validated with evidence.