The Customer portal (my.aihummer.ru) is AiHummer’s customer-facing portal:
here you register, choose a plan, pay, and manage your managed cloud instance,
and get personal install links for self-hosting. It is not the product admin
console — configuring agents, channels and models lives in the
Web UI.
This documentation group describes every portal screen: what it is for, how to
use it, and what you configure.
Portal vs Web UI
The portal is about billing, plan, payment, instance lifecycle, documents
and consents. Access is a customer account (e-mail + password).
The Web UI is about working with AI employees inside an already-deployed
instance.
A new account goes through the onboarding wizard: profile → path choice
(cloud or self-hosted) → plan and requisites (before payment) → payment →
provisioning — or minting an install link on the self-hosted path. The full
portal opens once the wizard completes. Details in
Registration and login.
Ideas and voting
The “Ideas” section is a public product-suggestion board with two tabs:
My ideas — your suggestions and their statuses: new / under review /
planned / done / rejected. Files can be attached to an idea (up to 3 files,
2 MB each).
All ideas — ideas from all customers that passed vendor moderation,
sorted by votes. You can vote for an idea with the ▲ button — one vote per
idea; idea authors are never revealed.
Ideas are available on every plan, including Community. Support tickets
(the “Support” section) are filed the same way — with attachments and a
conversation per ticket; portal support is available on paid plans.
How access works
The customer session is stored in a secure cookie and lasts up to 30 days with
sliding renewal. Public pages are login, registration, e-mail verification and
password reset; everything else needs authentication. Data and documents are
strictly scoped to your account.
The **Customer portal** (my.aihummer.ru) is AiHummer's customer-facing portal:
here you register, choose a plan, pay, and manage your **managed cloud instance**,
and get personal install links for self-hosting. It is **not** the product admin
console — configuring agents, channels and models lives in the
[Web UI](/en/v1.0/webui/overview).
This documentation group describes every portal screen: **what it is for, how to
use it, and what you configure.**
## Portal vs Web UI
- **The portal** is about billing, plan, payment, instance lifecycle, documents
and consents. Access is a customer account (e-mail + password).
- **The Web UI** is about working with AI employees inside an already-deployed
instance.
## Portal sections
- [Registration, verification, login and onboarding](/en/v1.0/portal/registration).
- [Profile and requisites](/en/v1.0/portal/profile).
- [Plans and storefront](/en/v1.0/portal/plans).
- [Order, payment and documents](/en/v1.0/portal/order-payment).
- [Instance dashboard and install](/en/v1.0/portal/instance).
- [Subscription management](/en/v1.0/portal/subscription).
- [Custom domain](/en/v1.0/portal/custom-domain).
- **Ideas** and **Support** — see below.
## Onboarding
A new account goes through the **onboarding wizard**: profile → path choice
(cloud or self-hosted) → plan and requisites (before payment) → payment →
provisioning — or minting an install link on the self-hosted path. The full
portal opens once the wizard completes. Details in
[Registration and login](/en/v1.0/portal/registration#onboarding-after-registration).
## Ideas and voting
The **"Ideas"** section is a public product-suggestion board with two tabs:
- **My ideas** — your suggestions and their statuses: new / under review /
planned / done / rejected. Files can be attached to an idea (up to 3 files,
2 MB each).
- **All ideas** — ideas from all customers that **passed vendor moderation**,
sorted by votes. You can vote for an idea with the ▲ button — one vote per
idea; idea authors are never revealed.
Ideas are available on every plan, including Community. **Support** tickets
(the "Support" section) are filed the same way — with attachments and a
conversation per ticket; portal support is available on paid plans.
## How access works
The customer session is stored in a secure cookie and lasts up to 30 days with
sliding renewal. Public pages are login, registration, e-mail verification and
password reset; everything else needs authentication. Data and documents are
strictly scoped to your account.
## Next
- [Customer portal (commercial)](/en/v1.0/commercial/personal-account) — a short
overview.
- [Registration and login](/en/v1.0/portal/registration) — where to start.
- [Licensing](/en/v1.0/commercial/licensing) — what a plan grants.
