Getting started
The beta is closed: an account needs an invite code. The code comes from the project Administrator. General discussion happens in the OpenIPC chat – the same place that answers questions and hands out the agent build for your camera.
When you ask for a code, give your Telegram nickname: a code belongs to one person and arrives in a direct message. Without the nickname the request goes unanswered – there is nowhere to send it.
An account
Open the panel – cloud-panel.openipc.ru – and the "Registration" tab. It asks four things: the invite code, an email, a password of at least ten characters, and, if you like, a name for your network.
The account is created at once, and a network of your own is cut for it. Everything you connect later lands in that network; other testers' cameras never appear in it, and yours never appear in theirs.
There is no password recovery by email anywhere here. If the password is lost, only the owner of the instance can reset it – and that is who to ask, in the chat.
The second factor
The "Sign-in" section of the panel is where a password and a one-time code (TOTP) from any authenticator app are bound. Until the code is bound, signing in takes the password alone; once it is, the code is always asked for. Bind it right away: the panel holds access to every camera you own.
Your first enrolment token
A device joins your network with a one-shot token. It is minted in the "How to connect" section, with the "Mint a token" button.
Three things about it matter:
- one token, one device: the second camera takes a new one;
- it lives an hour – after that you simply mint another, and nothing bad has happened;
- while it is alive, anyone holding it can put a device into your network. Do not paste it into a group chat.
Which string goes where
What people mix up here is rarely what a string means – it is which way it travels: what goes into the camera and what comes out of it. There are five strings in all, and you never make one up – each is handed to you by something.
| String | From | To | What for |
|---|---|---|---|
| Invite code | a direct message from the Administrator | the panel, "Registration" tab | creating the account; spent once |
Enrolment token (tok_…) | the panel, "How to connect" | the camera – it is already in the install command | putting the camera into your network and making it yours at once |
| Claim code | the camera: the installer prints it, cerberus status shows it again | the panel, "Add" | only when you did not mint the token: proving the camera is in your hands |
| RTSP login and password | the camera itself – you set them | the panel – it asks for them once the camera connects | letting the cloud fetch the stream when there is no direct path to the camera |
| App token | the panel, "Sign-in" → "Sessions" | the app, "Cloud (Streq)" | connecting the viewer to the cloud; one per app |
Your own camera is one string going one way: the enrolment token, from the panel into the camera. Nothing has to be carried back out of it.
Next
Connect a camera – the agent goes on the camera itself, and it takes four steps.
The agent build for your camera comes from the project Administrator: write to them in the chat and name the camera model. Or watch the official public discussions – some builds will be published there. There is deliberately no "Downloads" page during the beta – there are dozens of testers and every one of them has different hardware.