Private Client Room

CUSTOMER-OWNED COLLABORATION

A private client room without another data-hungry workspace.

A fixed-scope deployment of Element and the open Matrix protocol on infrastructure you control. Invite-only encrypted rooms, a documented handover, and no invented cryptography.

Ask about a pilot privately Prefer email? £199 one time · first 3 accepted deployments
A customer-owned server connecting invited team members and clients to three separate conversation rooms.
An illustrated deployment boundary—not a network diagram. The server stays in the customer’s account; the documented metadata and recovery limits still apply.
Your serverThe VM and domain remain in your account.
Established protocolMatrix and Element, not home-grown encryption.
Measurable handoverAcceptance checks before the invoice is due.

TWO-MINUTE FIT CHECK

Find out whether the fixed pilot fits.

Choose broad, non-sensitive answers. This check runs entirely in your browser: it makes no network request, uses no analytics, and stores nothing.

FIXED SCOPE

Enough to put a real client room into service.

EXECUTABLE DELIVERY

A locked deployment workspace, not a hand-built mystery server.

The public delivery kit pins the reviewed upstream automation. Before access is granted, its read-only preflight produces a private customer report for the documented Ubuntu, systemd, architecture, memory, Python, sudo, and Matrix/Element DNS prerequisites. It does not log in remotely or change the server.

After review, the kit prepares a private owner-only inventory without printing its generated secrets and applies the pilot defaults: no public registration, public room directory, telemetry, or federation.

After installation, a public-endpoint check verifies Matrix client discovery and the Element homeserver mapping without logging in or reading a room. Device verification, invited and refused access, backup recovery, and removal of temporary operator access stay visible as customer-controlled acceptance checks.

LOCKED UPSTREAM c0681e4 READ-ONLY PREFLIGHT delivery/preflight.sh REFERENCE RELEASES Synapse v1.159.0
Element Web v1.12.26 Inspect the delivery kit →

HONEST PRIVACY BOUNDARY

Private does not mean invisible.

End-to-end encryption is designed to keep room contents from the homeserver, but the server still handles account and delivery metadata. Infrastructure logs may contain IP addresses. Device verification and recovery keys matter; losing recovery material can make encrypted history unrecoverable. These limits are included in the handover instead of buried in marketing copy.

The deployment operator does not need message plaintext, recovery keys, or a permanent administrator login. Temporary deployment access is removed at handover.

ACCEPTANCE

You pay after the agreed checks pass.

  1. Two fresh devices can sign in and verify one another.
  2. An invited client can join the intended room, while an uninvited account cannot.
  3. Messages and an attachment sync between verified devices.
  4. A backup completes and the documented restore preflight succeeds.
  5. Temporary operator access is removed and the customer holds the administrator and recovery material.

Not included

Compliance certification, penetration testing, guaranteed anonymity, custom clients, data migration, regulated-data approval, federation, ticket or resolved-topic workflows, calls, conferencing, screen sharing, or third-party licence and hosting fees. Commercial or regulated deployments may require different software, support, licensing, and professional review outside this pilot. Scope changes are quoted before work starts.

Read the practical guide to evaluating this as a private Slack alternative.

Start with a two-paragraph fit check.

Tell us your team size, guest pattern, required conversation structure, and whether you already control a server and domain. Do not send credentials, messages, customer data, or recovery keys.

Send the private browser request Email [email protected]