TECHPARTNER CONSULTING

Codester demo · Business software

MeetServer — Your Own Video Meeting Server

A full video meeting server on your own server — your rooms, your accounts, your domain — with no per-host fee and no per-minute charge.

$149 on CodesterBoot test: partial — services started and the welcome page served in the packaging sandbox; the video router's image and the meeting-control link were blocked by sandbox faults, stated plainly belowOnly host accounts can start a meeting

Booted and checked during packaging

Real lines from the packaging boot test: the sign-in service and the web service started from the shipped configuration, the welcome page answered over HTTPS with the kit's name settings served in its configuration, and a host account was created with the kit's own documented command. Two parts could not be proven in the packaging sandbox: the video router's container image would not download (the sandbox's container store faulted), and the meeting-control service's internal link was defeated by the sandbox's name-resolution setup. Both are sandbox limits, named here rather than hidden — the same stack on a normal Docker host uses its own private network, which is the supported route. No screenshot is shown: the welcome page's heading is part of the pinned program build (see the branding note in the listing), so a capture would show the stock heading, and this page does not dress that up as the product.

MeetServer boot test — 2026-11-18, sandbox VM (podman run equivalents of the shipped docker-compose.yml; host networking is forced on this VM)
--- prosody (sign-in and room service) ---
ms-prosody Up 2 minutes
ms-jicofo Up 2 minutes
ms-web Up About a minute
2026-11-18 07:17:16 portmanager         info	Activated service 'c2s' on [::]:5222, [*]:5222
--- web service ---
GET https://localhost/ -> HTTP 200 (24,160 bytes, the real welcome page app)
GET https://localhost/config.js -> served; hosts.authdomain present (sign-in on)
GET https://localhost/interface_config.js -> served; kit name settings appended at the end:
interfaceConfig.APP_NAME = 'MeetServer';
interfaceConfig.NATIVE_APP_NAME = 'MeetServer';
interfaceConfig.PROVIDER_NAME = 'MeetServer';
interfaceConfig.SHOW_BRAND_WATERMARK = false;
--- host account through the kit's documented command ---
--- what did NOT connect in the sandbox ---

What it does