Unclear what an extension requests
Data and action permissions usually hide in the fine print.
HummerStoreSystem product · Marketplace
Extend HummerTech
in one click.
Agents, connectors, products, industry solutions, workflows, models and themes. Any developer can publish, but every extension passes automated and manual review.
10 categoriesPublication after review
The Store is open from day one. Openness means the ability to publish, not the absence of review.
Openness and risk
An open catalog without review is a risk to the ecosystem
Extensions work with connections, data and actions. Without review, openness turns into a security problem.
Compatibility breaks
A platform update knocks an extension out without warning.
No one answers for quality
The user is left alone with a third-party developer's problem.
Publishing is closed to newcomers
Hand-curated catalogs shut out small developers.
Review before publication
Open publishing with mandatory review
Any developer can submit an extension. Before publication it passes automated checks and a manual review: permissions, behavior, compatibility and support.
- Open submission. publishing is open to any developer with a HummerID
- Automated review. contracts, permissions, security and compatibility
- Manual review. behavior, listing quality and support readiness
- Clear permissions. the user sees the requested access before installing
- Compatibility contract. compatibility with product versions is checked on update
Store modules
HummerStore modules
A catalog for users and a console for developers.
Catalog
Categories, search and extension listings.
Publisher Console
Submission, versions and updates.
Automated Review
Automated checks before publication.
Manual Review
Manual review of behavior and quality.
Licensing
Licenses and terms of use.
Revenue Share
An 80/20 revenue share and individual terms.
Install / Update
Install, update and rollback.
Compatibility
Compatibility with product versions.
Ratings & Support
Ratings, reviews and support channels.
An extension's path
How an extension reaches the user
The path from the developer to installation in an organization.
01
The developer submits an extension
The Publisher Console takes the package, description, requested permissions and support contacts.
02
Review and publication
Automated tests and a manual review. The outcome: publication, revision or a reasoned rejection.
03
Installation in an organization
The administrator sees the requested permissions, installs the extension into the right context and can narrow its scope.
Fabric contracts
The source of truth stays with you
Extensions work through the same Fabric contracts as native products. No separate back door to the data exists.
Open submissionMandatory review
An extension never gets more permissions than the administrator allowed at installation.
HummerAuthHummerHomeFabric contractsPayment servicesThe developer's CI/CD
Agents in the catalog
Native AiHummer and compatible providers
Integration depth differs — and the page says so plainly.
AiHummer in HummerStore
Agents are the Store's biggest category. Ready-made AI employees install into a product and get a role, boundaries and permissions just like native ones.
- An agent's permissions show before installation
- An extension's actions are recorded in the shared log
- The administrator can narrow the agent's working scope
Third-party agents and models
LLM providers publish as their own category. The organization picks a model per task, and routing goes through the AI Gateway.
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 agentExtension permissions
Extension permissions and catalog deployment
Identity, connections, permissions, confirmations and deployment — the ecosystem's shared mechanisms applied to this product.
Contexts in HummerStore
An extension installs into a specific context: personal, professional or corporate. Moving between contexts takes a reinstall and consent.
PersonalProfessionalCorporate
How HummerID worksConnect once
An extension gets no direct access to connection credentials. It works through contracts and within granted permissions.
The owner sees the list of connections, scopes and terms, can narrow the data volume and revoke access in one click.
Connection Vault in FabricPermissions before installation
The requested access shows to the administrator in advance.
Extension isolation
An extension works within the granted context.
Revocation and removal
An extension disconnects without losing the organization's data.
Update review
Every new version goes through review again.
Формат поставки
The cloud Store is available from HummerHome and from the ecosystem's products.
In a self-hosted deployment the organization runs its own catalog perimeter and admits only extensions it has verified.
The public catalog is open to browse, while installation is limited to the organization's approved list.
What's nearby
What HummerStore works alongside
Products are independent. Your HummerID, connections, agents and settings move with you.
Developers
The Publisher Console, SDKs and publishing requirements.
OpenAvailable
AiHummer
The platform's agents and plugins.
OpenSoon
HummerFabric
The contracts extensions run on.
OpenPartners
Partner programs and revenue share.
OpenSoon
HummerHome
The entry point to the catalog.
OpenSecurity
Extension permissions and their review.
OpenSoonThe Store opens with the ecosystem's first product. The revenue model is 80/20 plus individual terms.
Publish an extension from day one
We're gathering developers and integrators ready to ship agents, connectors and industry solutions at the catalog's launch.
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.