Installation overview
Understand the delivery and the deployment journey before opening the private installation manual.
What you prepare
You need a server you control, access to upload files and run the supplied commands, and a plan for your domain or IP-based test address. The installer sets up the platform services and database; you still supply your own identity, provider accounts and enabled integrations.
Basic familiarity with files, SSH, DNS and a VPS is expected. The buyer documentation explains this product’s installation and configuration; it is not a course in programming or server administration. If those tasks are unfamiliar, work with an administrator or developer.
Installation journey
- Read the buyer ZIP’s start page and requirements before uploading. Keep the original archive and its documentation together.
- Create a clean supported server. The private guide includes a DigitalOcean Droplet example and file transfer guidance using SFTP tools such as FileZilla.
- Upload the supplied installation files, run the documented preparation command, and open the generated installation address. A blank server cannot install itself merely because its IP is opened in a browser.
- Choose your addresses, platform identity and services in the wizard. Complete privileged account setup using the private instructions.
- Configure your own providers, policies, catalog and client builds. Test the published client and another viewer before opening your service.
Subdomains, folders and IP tests
The installation supports separate subdomains or one domain with paths. An IP-based test uses paths; an IP address cannot act as a collection of named subdomains. Use the addresses generated for your installation rather than guessing API or portal routes.
| Mode | How visitors reach surfaces |
|---|---|
| Separate subdomains | Distinct hostnames for the surfaces selected in the installer. Configure DNS for those hosts. |
| One domain with paths | A shared hostname with separate app and portal paths. Keep those paths when configuring clients. |
| IP-based installation | Use the server address with the generated paths. Follow the private guide for HTTPS prerequisites and compatible services. |
Versions and launch responsibility
Use the exact toolchain versions documented in your buyer release. Changing Flutter, Node.js, native build tools or dependencies may require additional fixes; compatibility with every future version is not implied. The Windows build chapter describes its Microsoft build-tool requirements.
Server sizing depends on simultaneous viewers, bitrate, media provider and workload. A successful installation is not a capacity guarantee. Measure your workload before increasing traffic; external media services have separate accounts, costs and limits.
First administrator and server operations
Included in the buyer ZIP. The complete instructions are available exclusively in the private documentation supplied with the source code purchased through Codester. Authentication, credentials and recovery procedures are not published on this website. No private chapter is loaded or hidden behind this notice.
Supported server and toolchain
| Component | Buyer release reference |
|---|---|
| Server operating system | Ubuntu 22.04, 24.04 or 26.04; Debian 12 or 13. Fresh Linux server, x86-64 or arm64, with a public IPv4 address. |
| Starting resources | 4 vCPU, 8 GiB RAM and at least 25 GiB free, plus space for uploads, backups and container images. This is an engineering starting point, not a viewer-capacity guarantee. |
| Flutter clients | Flutter 3.44.4. Retain the supplied dependency lockfiles. |
| API / database | Node.js 24.18.0 (Node 24 series), TypeScript 5.9.3 and PostgreSQL 17. |
| Own media / HTTPS | Go 1.27, Pion 4.2.23 and Caddy 2.11 in the documented buyer stack. |
| Windows Studio | Windows x64, Node 24, Electron 45.0.0 and electron-builder 26.15.3. The desktop application does not install the backend. |
There is no one-click Windows backend installer in this release. The deployment target is Linux. Use the private manual for privileged server setup; the table above describes compatibility, not commands to execute.