example handover checklist
Example: backup run recorded, admin access handed over.
CUSTOMER-OWNED ZULIP
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
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.
Every item below is part of the same £199 offer for the first three accepted deployments.
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 guidanceThe work is intentionally finite. Decisions that change the boundary are discussed before deployment.
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.
Zulip Server 12.2 is set up with TLS, the agreed private channels, initial active accounts, guest roles, and customer-provided SMTP credentials.
We check sign-in, private-channel access, guest boundaries, topic resolve/unresolve/filtering, SMTP delivery, backups, and administrator handover.
The £199 one-time invoice is due after acceptance. Deployment-fault fixes remain available for seven days after acceptance.
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.
Your mail app opens with the eight broad choices. Review before sending; never add passwords, SMTP credentials, private messages, recovery material, or customer data.
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.
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.
These links explain the product concepts and self-hosting boundaries behind this offer.
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.