Connections get duplicated
Five products connect to the same 1C, each in its own way.
HummerFabricTechnology foundation
One technology fabric.
Independent products.
Identity, connections, context, analytics, policies, provability and orchestration are shared by all products. Small ships get a shared shipyard without merging into one liner.
15 layersShared by all products
Hover or focus a layer to see its role. Products use these layers yet remain independent applications.
Everyone rebuilds the same
Every product rebuilds the same things
Identity, connections, permissions, audit and model access are needed by every product. Built separately, products drift apart.
Permissions drift apart
Each product has its own role model, making a shared policy impossible.
Objects don't line up
The same counterparty looks different in every product.
Audit is assembled by hand
Proving a chain of actions across products is impossible.
AI Gateway
Native AiHummer and compatible providers
Integration depth differs — and the page says so plainly.
AiHummer in HummerFabric
The AI Gateway is part of Fabric. Every model call passes through it: model choice per task, limits, privacy and usage accounting.
- Native AiHummer uses Context, Trust, Proof and Flow directly
- Third-party models route through the same Gateway
- An organization can plug in its own models inside the perimeter
Third-party agents and models
Third-party products connect to Fabric via SDK, API and MCP. Depth depends on which contracts they implement: reading, actions, policy, proofs.
Routing goes through the AI Gateway, permissions through Hummer Trust. Setup takes extra work, and access to context and actions is limited by the organization's policies.
Connect your own agentA shared shipyard
A shared shipyard for independent ships
Fabric is not a monolith. It is a set of shared contracts and services that products use while staying independent in releases and interfaces.
- Shared contracts. products agree on a format, not on code
- Independent releases. each product updates on its own within the compatibility contract
- One policy. rules are set once and apply everywhere
- End-to-end audit. a chain of actions is traceable across products
- Extensibility. the Connector SDK and Agent SDK are open to partners and customers
Four paths
Four paths through Fabric
The same layers serve different kinds of requests.
01
The query path
The user asks — Context serves permitted data, Lens explains, the AI Gateway picks a model, and the answer returns with its source.
02
The data path
An external system publishes an event — Bridge receives it, the Canonical Model normalizes it, Context updates the read model.
03
The action path
A product initiates an action — Trust checks the policy, Bridge executes in the source system, Proof records the result.
04
The confirmation path
An operation exceeds the autonomy threshold — Flow builds the approval route, a human confirms, Proof stores the basis.
Fabric components
HummerFabric components
Each component solves one task and is available to every product.
Bridge
Exchanging events and actions with external systems.
Context
Permitted read models with provenance.
Canonical Model
One representation of objects.
Connection Vault
Connections, permissions and terms.
AI Gateway
Model routing and limits.
Lens
Analytics of causes and actions.
Trust
Policies and autonomy levels.
Proof
A provable history of actions.
Pact
Machine-readable agreements.
Continuity
States, queues and an offline cache.
Flow
Quick Flow and Advanced Flow.
Schema Registry
Schemas, versions and compatibility.
Connector SDK
Building your own connectors.
External BPM
The source of truth stays with you
An external BPM can own the whole process. Fabric then provides context, actions and proofs without taking over the route.
An external BPM can own the processFabric provides context and proofs
Quick Flow covers short scenarios with no developer. Advanced Flow and an external BPM handle complex processes with branches and deadlines.
All HummerTech productsDirectumELMA365Third-party BPMsInternal systems via the SDKMCP servers
Trust in the architecture
Trust inside the architecture
Identity, connections, permissions, confirmations and deployment — the ecosystem's shared mechanisms applied to this product.
Contexts in HummerFabric
Fabric has no context interface of its own — it enforces the boundaries defined by HummerAuth.
PersonalFamilyProfessionalCorporatePortal
How HummerID worksConnect once
The Connection Vault is a Fabric component. It is what makes the 'connect once' principle possible for the whole ecosystem.
The owner sees the list of connections, scopes and terms, can narrow the data volume and revoke access in one click.
Connection Vault in FabricPolicy before the action
Trust verifies authority before execution.
Proof after
Proof records the basis and the result.
Agreements between parties
Pact describes the terms in machine-readable form.
Continuity
Continuity never loses unfinished operations during failures.
Формат поставки
Cloud Fabric serves the ecosystem's products for individuals and small organizations.
Full Fabric deployment inside the organization's perimeter, including a private AI Gateway and local Proof logs.
Some components in the cloud, sensitive ones inside. The customer's architecture draws the line.
What's nearby
What HummerFabric works alongside
Products are independent. Your HummerID, connections, agents and settings move with you.
Available
AiHummer
The native agent runtime on top of Fabric.
OpenDevelopers
SDKs, schemas and the sandbox.
OpenIntegrations
System catalog and connector statuses.
OpenSecurity
The model of trust and provability.
OpenSoon
HummerEnterprise
Deploying Fabric inside an organization's perimeter.
OpenSoon
HummerStore
Extensions built on Fabric contracts.
OpenSoonThe technology foundation is in development. Publicly described as part of the ecosystem's architecture.
Let's walk the architecture on your landscape
The architecture session runs on your systems: what connects, which contracts are needed, and where the thin slice starts.
Powered byHummerTechThe mandatory master-brand badge
Application
Tell us about your task — we will get back with an answer and pilot details.
Request received
We will get back to you at the address provided. If it is urgent, write to info@hummer-tech.ru.