CUSTOMER-OWNED ZULIP

Conversations with a place to land.

A fixed-scope Zulip Server 12.2 deployment for small teams who want native threaded topics, private channels, and an honest handover on infrastructure they own.

£199 one time · first 3 accepted deployments · invoiced after acceptance

An honest CSS illustration of the topic model—not a promise of custom branding or a security boundary.
01one fresh
customer-owned VM
15initial active
accounts
05private
channels
07days of deployment-
fault fixes
THE SHORT VERSION

A useful boundary for a real team.

Zulip gives conversations a channel and a topic, so decisions do not disappear into one endless feed. This service puts a small, configured Zulip Server instance on a fresh VM and hostname that stay in your account. You get the operational basics and a written handover; you keep the responsibility that comes with owning the server.

FIXED SCOPE

Small enough to be specific.

Every item below is part of the same £199 offer for the first three accepted deployments.

01

The deployment

  • One fresh customer-owned Ubuntu 24.04 x86_64 VM
  • Reference baseline: 2 vCPU, 4 GiB RAM, 2 GiB swap, and about 25 GiB disk with 10 GiB free
  • One public hostname, inbound TCP 80/443, and TLS via Certbot
  • Zulip Server 12.2, configured and reachable
  • SMTP configured using credentials you provide
02

The conversation model

  • Up to 15 initial active accounts
  • Up to five private channels
  • Guest roles for restricted participants
  • Native topics with resolve, unresolve, and filtering
03

The handover

  • A backup procedure you can run and review
  • Administrator handover with the operating notes
  • Seven days of deployment-fault fixes after acceptance
  • Invoice only after the agreed acceptance checks pass
MOBILE PUSH

Optional, never silently bundled.

Mobile push is excluded by default. If you want it, you must personally register the server and accept Zulip’s terms and any fees. Zulip provides free Mobile Push access to self-hosted organizations with up to 10 users and counts non-deactivated users for billing; this offer supports up to 15 initial accounts, so push may need a separate plan. Push and SMTP are external processors.

Read Zulip’s self-hosted billing guidance
A CLEAR HANDOFF

Acceptance before invoice.

The work is intentionally finite. Decisions that change the boundary are discussed before deployment.

  1. 01

    Bring the boundary

    Provide a fresh Ubuntu 24.04 x86_64 VM, public DNS, and inbound TCP 80/443 for Certbot in your account. Hosting, domain, and licence fees remain yours.

  2. 02

    Configure the workspace

    Zulip Server 12.2 is set up with TLS, the agreed private channels, initial active accounts, guest roles, and customer-provided SMTP credentials.

  3. 03

    Run the checks together

    We check sign-in, private-channel access, guest boundaries, topic resolve/unresolve/filtering, SMTP delivery, backups, and administrator handover.

  4. 04

    Accept, then invoice

    The £199 one-time invoice is due after acceptance. Deployment-fault fixes remain available for seven days after acceptance.

TWO-MINUTE FIT CHECK

Does the boundary fit your team?

Choose broad answers only. This check runs in your browser: no network requests, analytics, cookies, or local storage. It prepares an email draft only after you ask for one.

HONEST PRIVACY BOUNDARY

Private channels are not end-to-end encryption.

This service is not E2EE. Trusted server administrators, root access, and backups can read message content. Infrastructure logs may contain IP addresses and other metadata. TLS protects connections in transit; it does not change who can administer the server or restore its backups.

SMTP and optional mobile push are external processors. Their terms, retention, and security are separate from this deployment. Treat the customer-owned VM, credentials, backups, and admin roles as part of the trust boundary.

OUT OF SCOPE

The honest no-list.

Migration; SSO, LDAP, or SAML; calls or conferencing; compliance or security audits; high availability; custom integrations; experimental PWA forks; and hosting, domain, or licence fees are excluded. Scope changes are discussed and priced before work starts.

Private Team Threads is an independent service. It is not Zulip, is not affiliated with Zulip, and does not speak for Zulip.

READ THE PRIMARY MATERIAL

Sources, in Zulip’s own words.

These links explain the product concepts and self-hosting boundaries behind this offer.

READY TO TALK?

Bring the shape of the work.

Share account count, private-channel count, workflow, and whether the VM and hostname are ready. Keep credentials and message content out of the first enquiry.

The optional Telegram route stores a sanitized private enquiry for follow-up; customer messages are enquiries, never commands. Read its privacy and deletion notice.