Demo Stand
You can look at AiHummer before installing it. A permanent demo stand runs at https://demo.aihummer.ru — an ordinary installation of the platform, open to everyone without registration. Nothing to install, nothing to buy, no form to fill in.
This page covers what is worth knowing before you sign in: how to log in, what you will see, why the data disappears every hour, and which actions are closed on the stand.
[!NOTE] The stand exists so that you can look at the product. You cannot work on it for real: the account is shared by every visitor and the data lives no longer than an hour.
Address and sign-in
- Address:
https://demo.aihummer.ru - Username:
demo - Password:
demo
No registration is needed and there is no password to change: it is the same for everyone and printed here on purpose — that is exactly what the stand is for.
[!WARNING] What happens: everything you write or configure on the stand is visible to other visitors. Under what condition: always — the
demoaccount is shared, and you are inside the stand at the same time as other people. How to avoid it: never enter real credentials, passwords, phone numbers or any personal data on the demo. Real work needs your own instance — in the cloud or on your own server.
What you will see
The stand is not a trimmed-down showcase but an ordinary AiHummer installation. You are in the same web interface this documentation describes: the dashboard, AI employees, channels, memory, knowledge, settings. A good place to start is the Web UI overview — section by section it matches what is in front of you on screen.
What exactly is already set up on the stand — which AI employees exist, which channels are connected, which conversations sit in the history — is decided by the stand’s operator and changes over time. That is why it is not listed here: the current state is visible right after you sign in, while a list in the documentation would go stale silently.
[!NOTE] The chat on the stand runs on a scripted model, not a real one. It answers a handful of questions about the product, says plainly that it is a demo, and can hand out a code for connecting the mobile app. Do not judge AiHummer’s answers by it — in your own instance you connect a model yourself.
Connecting the mobile app
The AiHummer mobile app can be connected to the stand — that is exactly what the stand was built for, so that someone handed nothing but an address can walk the whole path. Its screens are described in the app overview.
- The standing connection code. The stand carries a code issued in advance — a QR
code and a connection string. It does not expire and it is reusable, so a QR
photographed once keeps working. The stand publishes it itself:
GET https://demo.aihummer.ru/v1/admin/demo, fieldpairing. The value is deliberately not printed here — it belongs to the stand, and only the stand always knows the current one. - An ordinary code from the chat. Ask the AI employee how to connect the app and it issues an ordinary code, with the ordinary lifetime — exactly as on your own server. A code asked for in the chat never becomes permanent.
The data resets every hour
Once an hour the stand returns to its initial state. Everything you created on it — conversations, AI employees, settings, uploaded files — disappears.
This is how the stand is built, not how the product behaves. In your own instance the data sits in your PostgreSQL database and stays there; the reset exists precisely so that the next visitor finds the stand as clean as you found it.
The reset does not cut work off in mid-sentence: a conversation written in during the last 15 minutes is skipped by the current pass and collected by the next one. Everything else goes at once.
[!NOTE] If something on the demo is worth keeping — a well-phrased instruction for an AI employee, say — copy it out immediately: in an hour it will be gone. The reverse is also true: there is nothing you can break here, because anything broken repairs itself within the hour.
What is closed on the stand
Some actions on the demo are deliberately switched off. What is closed falls into one of three groups:
- it would break the stand for everyone else — the stand is shared, and one unlucky setting would be inherited by every visitor after you;
- it would reach the outside world under someone else’s name — connecting production channels and sending messages, e-mails or calls to real recipients;
- it changes the stand itself — updating, restarting, changing the credentials, access to the server and to the installation files.
[!IMPORTANT] The exact list of closed actions lives in the stand itself, not here: a closed action answers with a clear refusal right on screen. It is deliberately not duplicated in the documentation — the set of restrictions changes together with the stand, so a list here would go stale silently and you would be reading yesterday’s truth with today’s confidence. If an action is refused on the demo, that is a limit of the stand, not a defect of the product.
The full set of capabilities is available in your own instance: there you are your own administrator and none of the above is closed.
Next steps
- Requirements — what the server needs if you install it yourself.
- Installation — how to get your own instance.
- First login — your own administrator and your
own password instead of the shared
demo.