Layers admin panel
Your whole server in one panel
Who signed in, from which device and what they did — plus a button to cut off access. The admin panel of your Layers server opens in the browser.
90-day trial · license pricing on request
The problem
How a self-hosted server is usually run
No panel
- ✗Cutting off a former employee means a database query or a script
- ✗No way to tell who deleted a document
- ✗Email, search and calls are configured in different files
- ✗Guesswork about what applies now and what needs a restart
01 · Launch
A node ready in six steps
The checklist takes you through the steps top to bottom, and the panel checks the server itself to see what’s done.
A first-run checklist
Domains, email, sign-in and the rest, top to bottom. An item is marked Done from the server’s actual state, not because someone opened the screen.
Only the modules you need
Projects, Forms, Flow, Cloud and the other modules each have their own switch. Turn off what you don’t need in one click.
02 · Connect
Email, search, files and calls — no config files
Node services are set up through forms. Each form says what the user gets and when the change takes effect.
Test email before you save
A test email goes out with the form’s current settings, so the password and encryption are checked before anything is saved.
Node services
Search, storage, calls and emails
Search
Automatic, Elasticsearch, Manticore or built-in (Lucene) — pick the engine from the list.
Storage
Files go to local storage or to S3 — pick the type from the list.
Calls
Your own LiveKit server: with the switch on, chats and channels get call and screen-sharing buttons.
Email templates
Registration, password reset, invitation, invite accepted, role change — each email has its own HTML template.
03 · People
Everyone on the server, in plain view
How many people there are, who signed in, how many sessions are open and where sign-in failed. Blocking and new passwords take effect immediately.
Every account on the node
Total, signed in over 30 days, open sessions, sign-in failures in 24 hours. Search by name, address or handle, and filters: active, no email, access disabled.
Access is cut off with one button
Disable access: sign-in is blocked and all of the person’s sessions are closed. The same button restores access.
04 · Audit log
See who did what
An audit log for the whole node: opened, changed, deleted, downloaded — and who was denied access.
An action log for the whole node
A feed of events with filters: period, person, action, significance. Pick “delete” and only deletions remain.
Who was denied access
The Access denials filter leaves only attempts to open what isn’t theirs: who, when and what exactly.
Evidence
A person’s actions and log export
A person’s actions
A person’s card shows their actions over 30 days: when, what, on which object and the outcome.
Export and integrity check
Export saves what the filters selected; Check integrity walks the hash chain if the node admin has turned it on.
05 · Operations
No surprises after a restart
Every setting says when it takes effect. What’s waiting for a restart is listed on its own screen.
What applies now and what after a restart
Settings that are read only at startup are listed under Waiting for a restart. The rest take effect after Apply without restarting.
Every day
Health, quotas, the email queue and panel sign-in
System status
Server, web app and panel versions — you can see exactly what’s running on the node.
Workspace quotas
An exception for one workspace: storage in GB and number of members. Takes effect immediately, no restart.
Email queue
How many emails are waiting, sent and failed — and which ones the queue has given up on.
Signing in to the panel
The panel password is stored as a hash: the plain password from the file is replaced on the first sign-in. You can change it right here.
06 · License
The key never blocks work
The first 90 days are a full-speed trial. After that you need a license; pricing is on request. The key is pasted as one line and verified on the server itself.
A trial at full strength
The panel shows how many trial days are left. Without a key, people and data are not blocked — only machine jobs slow down: meeting transcription and export. License pricing is on request; installation and support are separate, by agreement.
Discuss self-hosting →Node modules
Modules with a switch in the panel
Where does the panel open?
On your server at /godmode; sign in with the node admin’s username and password. The panel password is stored as a hash and is changed under God Mode access.
How much is the key, and what happens without it?
The first 90 days are a full-speed trial. After that you need a license. Pricing on request: we’ll discuss your team size, support and license terms. Without a key, sign-in and data are not blocked, but machine jobs slow down — meeting transcription and export.
Which sign-in methods can I turn on?
Google, Yandex, VK and Gosuslugi (ESIA). The button appears on the sign-in screen once the app keys are filled in and the switch is on.
Do I need to restart the server after changing settings?
Not always. Every setting says when it takes effect; Restart and apply shows what’s waiting for a restart and reloads everything else without one.
What does the audit log show?
Who opened, changed, deleted and downloaded, and who was denied access, with filters by period, person, action and significance. Export follows the selected filters.
Does the panel back up the database?
No. The Backup section saves the state of the app store; back up the PostgreSQL database with your own tools.
Can I limit a single workspace?
Yes: quotas set storage in GB and the number of members for a specific workspace. They take effect immediately.
Your whole server in one panel
The app and the panel run in Docker together. Six first-run steps — from domains to connecting an AI model.
90-day trial · then a license, pricing on request
