Self-host Missived

Run Missived on your own server.

The whole app, open source under AGPL-3.0. Your hardware, your data, every feature switched on, no prices inside. The free self-hosted edition is ready for early testers on Linux, Mac and Windows. Start on your own computer, then invite your group using a domain you control.

Install it, step by step Which path is for me?Use your own AI agent

Ready for early testersSelf-hosted edition 1.1.0. Linux is recommended for real use; a Mac or Windows PC for trying it out and small groups (about 25).

# a Linux server, a Mac or a Windows PC with Docker
$ git clone <public repo> missived
$ cd missived && scripts/selfhost/setup.sh

  Missived setup · 8 questions
  1. Your address     chat.gracechapel.org
  2. Server size      small · ≤ 25 people
  3. Sending email    Postmark / Resend / other SMTP
  …
$ scripts/selfhost/doctor.sh
✓ 0 FAIL
✓ open https://chat.gracechapel.org

Free self-hosted edition

Your server. Every feature on.

Run the whole app with no plan limits. You manage the hardware, domain and backups; certificates renew automatically.

You run it with the same Platform Console we use: capacity, plans and limits, notices and analytics, no tracking.

Want help with the domain, updates or a home tunnel? See what's coming next.

Ready for early testers

Do it yourself

For people with their own domain who like to run things.

Your domain, your certificates (automatic)
Update when you choose with upgrade.sh: backup first, rolls back on failure
Every feature on, no plan limits
Community help

Install guide

Step by step

Install it on your computer, start to finish

Never hosted anything before? Answer three questions, then follow the steps for your computer. Every step ends with how you know it worked.

Which path is for me?

1. Where will Missived run?

2. What kind of computer is it?

3. Do you already own a domain name, like gracechapel.org?

Pick an answer to each question and we'll point you to the right steps below.

The public repository opens with the first public release. Until then the git clone lines show a placeholder and the guide links say "coming soon". Want to try it early? Write to [email protected].

Ready for early testersRecommended for groups and anything people depend on

Ubuntu 24.04 (tested), or any Linux with systemd
2 vCPU · 4 GB memory at least (sizes for more people)
Docker Engine with the Compose plugin, plus git curl openssl

Email
For real delivery, use your own Postmark or Resend account, or other SMTP. Set up email in 5 minutes. Missived (us) never sees your mail. Console is fine for this computer-only test.

Get the code

git clone <public repo> missived && cd missived

a missived folder with scripts/ inside.

Run the setup for this computer only
```
scripts/selfhost/setup.sh --host localhost --mail console --email [email protected] --yes
```
Use your own email: it becomes the first account. "Console" mail means codes go to the server's log instead of an inbox.
it prints the next commands.
Start it
```
docker compose -f deploy/selfhost/docker-compose.yml up -d --build
```
The first build takes a few minutes.
every container says Started or Healthy.
Check it
```
scripts/selfhost/doctor.sh
```
0 FAIL. On this computer-only trial, DNS, mail and outside-reachability lines are warnings, which is expected.
Open it and register
Go to https://localhost (the browser warns about the certificate: continue). Register with the email you gave setup, then find the code in the log:
```
docker compose -f deploy/selfhost/docker-compose.yml logs server | grep 'Missived code'
```
you're signed in and can start a voice call. Only this computer can join for now.

Email
For real delivery, use your own Postmark or Resend account, or other SMTP. Set up email in 5 minutes. Missived (us) never sees your mail. After starting, run scripts/selfhost/doctor.sh --send-test [email protected] with your address and check your inbox.
Prepare the server
Open the firewall for 80, 443 and 7881 (TCP), and 3478 and 7882–7891 (UDP). SERVER_SETUP has the firewall and kernel settings line by line.
sudo ufw status (or your provider's firewall) lists those ports.
Point your domain at it
At your domain company, add three A records with the server's public IP (203.0.113.10 is an example):
Type Name Points to

A chat 203.0.113.10

A livekit.chat 203.0.113.10

A turn.chat 203.0.113.10
dig +short chat.gracechapel.org answers with the server's IP.
Get the code and run the setup
```
git clone <public repo> missived && cd missived
```
```
scripts/selfhost/setup.sh
```
It asks 8 questions (your address, size, how to send email…) and writes one settings file.
it prints the next commands.

Type	Name	Points to
A	`chat`	`203.0.113.10`
A	`livekit.chat`	`203.0.113.10`
A	`turn.chat`	`203.0.113.10`

Start it

docker compose -f deploy/selfhost/docker-compose.yml up -d --build

every container says Started or Healthy.

Check it
```
scripts/selfhost/doctor.sh
```
It tests DNS, certificates, ports, email and calls, and says in plain words what to fix. Run it again after each fix.
0 FAIL.
Back up the encryption key
Copy DATA_ENCRYPTION_KEY from deploy/selfhost/.env somewhere safe, away from the server. Without it, uploaded files can't be read back.
the key is in your password manager.
Open your address and register
Go to https://chat.gracechapel.org, register as the first account (the Owner) and invite people.
a phone on mobile data joins a call.

No domain? Missived names are on the waitlist; you can buy your own domain to use these steps today.

Full guides: SELF_HOSTING · SERVER_SETUP · REQUIREMENTS

Stuck? Run scripts/selfhost/doctor.sh: every FAIL says what to fix. Then see GETTING_HELP.

Ready for early testersGood for trying it out and small groups (up to about 25). For more, use a Linux server.

A Mac, Apple silicon or Intel, on a supported macOS
8 GB memory (16 GB is comfortable) and 20 GB free
Docker Desktop: free for personal use, education and small businesses (fewer than 250 people and under $10M a year); larger organisations need a paid Docker subscription, which is theirs to hold. OrbStack also works.

Email
For real delivery, use your own Postmark or Resend account, or other SMTP. Set up email in 5 minutes. Missived (us) never sees your mail. Console is fine for this computer-only test.
Install Docker Desktop
Download it from Docker's website (pick Apple silicon or Intel to match your Mac). In its Settings: General → "Start Docker Desktop when you sign in"; Resources → memory at least 4 GB, disk at least 40 GB.
the whale in the menu bar stops animating.
Install git
In Terminal:
```
xcode-select --install
```
git --version prints a version.
Get the code
```
cd ~ && git clone <public repo> missived && cd missived
```
Keep it in your home folder, not in Desktop, Documents or iCloud Drive (syncing gets in Docker's way).
you're in the missived folder.

Set it up and start it

scripts/selfhost/setup.sh --host localhost --mail console --email [email protected] --yes
docker compose -f deploy/selfhost/docker-compose.yml up -d --build
scripts/selfhost/doctor.sh

The first build takes 5–15 minutes.

doctor shows 0 FAIL (sleep, DNS and mail warnings are expected on a trial).

Open it

Go to https://localhost in Safari, Chrome or Firefox and continue past the certificate warning. To make the warning go away, trust Missived's local certificate:

docker compose -f deploy/selfhost/docker-compose.yml cp proxy:/data/caddy/pki/authorities/local/root.crt ./missived-local-root.crt
sudo security add-trusted-cert -d -r trustRoot -k /Library/Keychains/System.keychain missived-local-root.crt

the sign-in page loads.

Register
Use the email you gave setup. The code is in the server's log:
```
docker compose -f deploy/selfhost/docker-compose.yml logs server | grep 'Missived code'
```
you're signed in. Only this Mac can join for now.

Check this first: does your home have its own public address? Open your router's status page and find its WAN (internet) address. If it starts with 10., 100.64–127., 172.16–31. or 192.168., your provider shares one address between many homes (carrier-grade NAT), and this path won't work. DNS + Tunnel will, when it's ready.

Email
For real delivery, use your own Postmark or Resend account, or other SMTP. Set up email in 5 minutes. Missived (us) never sees your mail. After starting, run scripts/selfhost/doctor.sh --send-test [email protected] with your address and check your inbox.
Point your domain at your home
Add three A records — chat, livekit.chat and turn.chat — pointing at your home's public IP.
dig +short chat.gracechapel.org answers with your home's IP.

Set it up for your address

scripts/selfhost/setup.sh --host chat.gracechapel.org --email [email protected]
docker compose -f deploy/selfhost/docker-compose.yml up -d --build

Setup notices it's on a Mac and picks the layout that works there.

every container says Started or Healthy.

Forward ports on your router
Forward TCP 80, 443, 7881 and UDP 3478, 7882–7891 to the Mac's address on your network (System Settings → Wi-Fi → Details → TCP/IP). In the router, reserve that address for the Mac (a "DHCP reservation") so it doesn't change.
the router's port-forward table lists all five lines.
Allow it through the firewall
If macOS asks whether com.docker.backend may accept incoming connections, click Allow.
Keep the Mac awake
System Settings → Energy (desktop) or Battery → Options (laptop) → "Prevent automatic sleeping…". Or in Terminal: sudo pmset -c sleep 0. A closed laptop lid still sleeps.
doctor's host: sleep line passes.
Check it, then test from outside
```
scripts/selfhost/doctor.sh
```
0 FAIL, and a phone on mobile data (Wi-Fi off) opens your address and joins a call.
Back up the encryption key
Copy DATA_ENCRYPTION_KEY from deploy/selfhost/.env to your password manager.

Calls on a Mac. Calls work for almost everyone. People on networks that allow only web traffic (some offices, hotels and schools) can chat but not join calls; a Linux server fixes that.

Full guide: MAC · REQUIREMENTS

Stuck? Run scripts/selfhost/doctor.sh: every FAIL says what to fix. Then see GETTING_HELP.

Ready for early testersGood for trying it out and small groups (up to about 25). For more, use a Linux server.

Not yet tested on a real Windows PC. The Windows checks run in our automated tests, and the setup scripts are tested on Linux and a Mac, but we haven't yet run a complete install on a real Windows PC through to a call from another device. If you try it, tell us how it went.

Windows 11, or Windows 10 22H2 or later
8 GB memory and 30 GB free; an administrator account once
Docker Desktop, with the same licence note as on a Mac: free for personal use, education and small businesses (fewer than 250 people and under $10M a year)

Email
For real delivery, use your own Postmark or Resend account, or other SMTP. Set up email in 5 minutes. Missived (us) never sees your mail. Console is fine for this computer-only test.
Install WSL and Ubuntu
Right-click PowerShell → "Run as administrator", then:
```
wsl --install
```
Restart when asked. The Ubuntu window opens and asks you to make a Linux username and password.
the Ubuntu window shows a prompt.
Install Docker Desktop
Keep "Use WSL 2" ticked in the installer. In its Settings: General → "Start Docker Desktop when you sign in"; Resources → WSL integration → turn on Ubuntu.
docker version in Ubuntu shows both Client and Server.
Get the code (in Ubuntu)
```
sudo apt update && sudo apt install -y git curl openssl
```
```
cd ~ && git clone <public repo> missived && cd missived
```
Keep it in your Linux home folder, not under /mnt/c (your Windows drives are slow and confuse Docker from there).
you're in the missived folder.

Optional: check the Windows side

In PowerShell (use your Linux username in place of you):

powershell -ExecutionPolicy Bypass -File \\wsl.localhost\Ubuntu\home\you\missived\scripts\selfhost\setup.ps1 -Check

every line says PASS.

Set it up and start it (in Ubuntu)

scripts/selfhost/setup.sh --host localhost --mail console --email [email protected] --yes
docker compose -f deploy/selfhost/docker-compose.yml up -d --build
scripts/selfhost/doctor.sh

doctor shows 0 FAIL (sleep, DNS and mail warnings are expected on a trial).

Open it

Go to https://localhost in Edge or Chrome and continue past the warning. To trust Missived's local certificate, in Ubuntu:

docker compose -f deploy/selfhost/docker-compose.yml cp proxy:/data/caddy/pki/authorities/local/root.crt /mnt/c/Users/Public/missived-local-root.crt

then in PowerShell:

certutil -user -addstore Root C:\Users\Public\missived-local-root.crt

the sign-in page loads.

Register
Use the email you gave setup. The code is in the server's log (in Ubuntu):
```
docker compose -f deploy/selfhost/docker-compose.yml logs server | grep 'Missived code'
```
you're signed in. Only this PC can join for now.

Check this first: does your home have its own public address? If your router's WAN address starts with 10., 100.64–127., 172.16–31. or 192.168., your provider shares one address between many homes, and this path won't work. DNS + Tunnel will, when it's ready.

Email
For real delivery, use your own Postmark or Resend account, or other SMTP. Set up email in 5 minutes. Missived (us) never sees your mail. After starting, run scripts/selfhost/doctor.sh --send-test [email protected] with your address and check your inbox.
Point your domain at your home
Add three A records — chat, livekit.chat and turn.chat — pointing at your home's public IP.
nslookup chat.gracechapel.org answers with your home's IP.

Set it up for your address (in Ubuntu)

scripts/selfhost/setup.sh --host chat.gracechapel.org --email [email protected]
docker compose -f deploy/selfhost/docker-compose.yml up -d --build

every container says Started or Healthy.

Forward ports on your router
Forward TCP 80, 443, 7881 and UDP 3478, 7882–7891 to the PC's address (PowerShell: ipconfig, the IPv4 Address of your Wi-Fi or Ethernet), not Ubuntu's. Reserve that address for the PC in the router.
the router's port-forward table lists all five lines.

Allow it through the firewall

Set your network to Private (Settings → Network & internet → your network → Network profile type), and allow "Docker Desktop Backend" on private networks when Windows asks. Or add the rules yourself in PowerShell (admin):

New-NetFirewallRule -DisplayName "Missived TCP" -Direction Inbound -Protocol TCP -LocalPort 80,443,7881 -Action Allow -Profile Private
New-NetFirewallRule -DisplayName "Missived UDP" -Direction Inbound -Protocol UDP -LocalPort 3478,7882-7891 -Action Allow -Profile Private

Keep the PC awake
Settings → System → Power → when plugged in, sleep Never (or powercfg /change standby-timeout-ac 0), and set Windows Update's active hours so it doesn't restart while people use it.
setup.ps1 -Check's sleep line says PASS.
Check it, test from outside, back up the key
```
scripts/selfhost/doctor.sh
```
Then copy DATA_ENCRYPTION_KEY from deploy/selfhost/.env to your password manager.
0 FAIL, and a phone on mobile data opens your address and joins a call.

Calls on Windows. Calls work for almost everyone. People on networks that allow only web traffic (some offices, hotels and schools) can chat but not join calls; a Linux server fixes that.

Why WSL? The setup scripts are Linux scripts and Missived's parts run as Linux containers. Ubuntu is built into Windows through WSL, and Docker Desktop uses it anyway.

Full guide: WINDOWS · REQUIREMENTS

Stuck? Run scripts/selfhost/doctor.sh in Ubuntu (and setup.ps1 -Check in PowerShell): every FAIL says what to fix. Then see GETTING_HELP.

Set it up with your own AI agent

Your own Claude Code, Codex or similar local assistant can follow our runbook to install Missived, configure email and sign-in, check calls, and help with backups and upgrades. You choose the accounts, costs and changes.

Run it on the server or in a repository checkout on the machine you want to install on. Paste this starter prompt:

Read docs/self-hosting/AGENTS.md in this repo and follow it to install / configure Missived on this machine; stop at every 🛑 and ask me.
If this is the public repository, read the root AGENTS.md instead. For an existing install, use Configure after install and preserve its data and secrets. Review commands with me before running them. Never print secrets. Keep backups and test a restore before upgrades or destructive changes.

Read the agent runbook — coming with the public repo. The public export puts AGENTS.md at the repository root.

Review commands before approving them. Keep the agent's tool approval prompts on, enter credentials privately, and never let it print secrets. Keep the encryption key and tested backups off the server. Stop signs (🛑) mark decisions that belong to you.

Already installed? Connect your assistant to your own install from Settings → Developer → Connect an AI assistant to set up channels, roles and client portals through MCP. The bundled proxy serves it at https://<your host>/api/mcp. Choose its permissions and check changes in Activity; your assistant's provider can see the content you let it read.

What you need

Server sizes

Calls and video decide the size far more than chat does. These are our estimates; the media numbers haven't been load-tested on production hardware yet (how to measure your own).

People	Layout	Minimum	Recommended
Up to 25	one box	2 vCPU · 4 GB RAM · 40 GB SSD	4 vCPU · 8 GB · 80 GB
Up to 150	one box	4 vCPU · 8 GB · 80 GB	8 vCPU · 16 GB · 200 GB
Up to 500	two boxes	app 4 vCPU · 8 GB; media 8 vCPU · 8 GB	app 4 vCPU · 16 GB; media 8 dedicated vCPU · 16 GB

Which computer

Computer	Good for	Guide
A Linux server (a VPS or your own box; Ubuntu 24.04 tested)	Every size above, and anything that must stay up	SELF_HOSTING, SERVER_SETUP
A Mac with Docker Desktop or OrbStack	Trying it out; a small group (up to about 25)	MAC
A Windows PC with WSL 2 and Docker Desktop	Trying it out; a small group (up to about 25). Not yet tested on a real PC.	WINDOWS

Why only small groups on a Mac or PC: Docker runs in a virtual machine there, so people on web-only networks can't join calls; and a desktop sleeps, restarts for updates and shares a home connection's upload.

InstallClone the release and run setup.sh. It asks 8 questions and writes one settings file.

Checkdoctor.sh tests ports, certificates, email and calls, and tells you in plain words what to fix.

Upgradeupgrade.sh backs up first and rolls back if anything fails.

Set up email in 5 minutes

Choose Postmark, Resend or any SMTP provider. These are your own accounts with those services: your server sends directly to them. Missived (us) never sees your mail.

Allow about five minutes of setup; domain approval and DNS records can take longer. Keep open and click tracking off in your provider's dashboard.

Postmark

Sign up at Postmark and create a transactional server.
Add your sending domain. Publish the DNS records it gives you for DKIM and the Return-Path (SPF), then wait for verification.
Enable SMTP and copy the Server API token, not the Account token.
In setup's Email question choose postmark. Paste the token (hidden), then a sending address on your verified domain.

Resend

Sign up at Resend and add your sending domain.
Publish the SPF and DKIM DNS records it supplies, then wait for verification.
Create an API key allowed to send from that domain.
In setup's Email question choose resend. Paste the key (hidden), then a sending address on your verified domain.

Other SMTP

Use your mail provider's SMTP service and verify your domain with its SPF and DKIM records.
Get its host, port, username and SMTP password or app password.
Choose smtp in setup. Enter those settings and your verified sending address. Use 587 for STARTTLS or 465 for implicit TLS.

Just looking around? Choose console: codes go to the server log, never an inbox.

After starting the stack, send yourself a test (use your own address):

scripts/selfhost/doctor.sh --send-test [email protected]

Check your inbox and spam, plus the provider's delivery log if it doesn't arrive. A successful SMTP send means accepted for delivery; check the inbox before inviting your group. Full email settings and troubleshooting.

Do it yourself

Already run Cloudflare Tunnel? Do it yourself

You can publish the web app and chat through your own cloudflared tunnel, using your own Cloudflare account (including its free plan). This is separate from our planned DNS + Tunnel service.

Cloudflare decrypts the traffic at its edge. It can see sign-ins, cookies, messages and files passing through the tunnel. HTTPS encrypts each leg, but this is not TLS passthrough. Tell your group before choosing this route.

Calls need a separate media path. Cloudflare Tunnel does not carry calls' UDP for public visitors. Without another path, chat works but a call may stay connecting or have no sound or video.

Forward media ports: with a reachable public address, forward 3478/udp, 7882–7891/udp and 7881/tcp to your box (use setup's actual range). Calls use your home upload; carrier-grade NAT prevents this.
Use a TURN server elsewhere on TCP/TLS 443: it must also reach your LiveKit media server. This needs extra configuration, bandwidth and usually a paid server; TCP can make calls stutter when packets are lost. Adding a TURN hostname alone does not solve carrier-grade NAT.
Stay chat-only: no inbound ports needed for the web app and chat. Tell members calls are unavailable.

Setup outline for Linux, Mac and Windows

Follow the OS setup above with your own hostname, such as chat.example.com. In the single-box configuration, set LIVEKIT_WS_URL to wss://chat.example.com so call signalling also uses the app's proxy.
Give that proxy an origin certificate, or use a local certificate with the tunnel's noTLSVerify setting only on the local route. Set the origin server name and HTTP Host Header to chat.example.com.
In your Cloudflare tunnel, map the public hostname to https://localhost:443 when cloudflared runs on the host. A container must use an address that reaches the proxy; its own localhost is a different container. Keep WebSockets on and bypass caching for this hostname.
Test chat from outside your network, then test calls only after setting up a media path. The full guide covers certificates, Docker Desktop, WSL and what doctor can check.

Full Cloudflare Tunnel guide in the self-hosting docs (public repository coming soon). This is a documented DIY recipe; we have not tested an install with a Cloudflare account.

Before routing uploads or video through it, read Cloudflare's current terms, service-specific terms and video policy. Their plan limits and content rules apply; a free account is not an unlimited media service. WebSocket connections can also reconnect after edge restarts.

Coming next

Coming next — join the waitlist

Not production ready yet

Missived DNS, DNS + Tunnel, managed updates and the phone push relay are in development. Nothing here can be bought or activated today; prices and fair-use limits below are proposed. Join the waitlist for your setup code when they open.

The planned stack is Cloudflare DNS for names, WireGuard from your box, and Caddy (layer-4, SNI passthrough) on our relays. WireGuard and Caddy are open source, so you can run the same relay stack yourself; you can choose your own DNS provider too.

Early access, when it opens

Hosted names will open in weekly batches

When they open, the certificate authorities we use limit how many new certificates a domain gets each week, so we'll open new hosted names in weekly batches, oldest request first. You'll get one email with your setup code when your turn comes. Bringing your own domain will skip the line entirely.

Join the waitlist

A list of people waiting, not a sign-up: no account, nothing to pay.

Explore the planned services and proposed prices

Missived DNS

$50 / year, proposed

or $5 a month

For a server with a public address: a VPS, a colo box, a home connection with port forwarding.

A name like yourgroup.missived.app
Certificates set up and renewed for you
Managed, signed updates with a backup first and automatic rollback
Phone notification relay included when the phone app ships

Join the waitlist

DNS + Tunnel

$100 / year, proposed

or $10 a month

For a computer at home or behind a router you don't control. No port forwarding, works behind carrier-grade NAT.

Everything in Missived DNS
An encrypted tunnel from your box to our relay
Calls and video relayed too
Fair use for a real group, in plain numbers below

Join the waitlist

	Do it yourself	Missived DNS	DNS + Tunnel
Price	Free	$50/yr or $5/mo (proposed)	$100/yr or $10/mo (proposed)
Every Missived feature	✓	✓	✓
Your own domain	✓ required	✓ optional, or ours	✓ optional, or ours
Certificates handled	Automatic with your domain	✓	✓
Updates	You run `upgrade.sh`	Managed: backup, update, roll back if needed	Managed: backup, update, roll back if needed
Works without a public IP	—	—	✓
Phone notification relay	Planned add-on	Included (with the phone app)	Included (with the phone app)
Who can read your messages	Only your server	Only your server	Only your server; the relay passes encrypted traffic through

How it will work

Hosted names and the home tunnel, step by step

This is the plan for Missived DNS and DNS + Tunnel, so you can see exactly what would happen and who does what.

You do thisWe do thisHappens automatically

DNS + Tunnel with a Missived name

Your group gets yourgroup.missived.app, your server sits at home, and you never touch your router.

$100/yr or $10/mo, proposedNo router changesLive in about 2 minutes, once open

1
YouGet a computer that stays on
A small PC or mini-PC running Linux is ideal; a Mac or Windows PC works for small groups while it's awake. Up to 25 people: 2 cores, 4 GB of memory, 40 GB of storage.
2
YouPick your name and pay
Choose yourgroup on this page; we check it's free. Pay through Stripe's checkout page. We never see your card.
2 minutes
3
WeSend your setup code
A one-time code appears on screen and in your email. During early access it arrives when your batch opens (see Early access below).
4
YouRun two commands on the computer
Download Missived and run the setup with your code. It asks a few plain questions, like how to send email.
git clone <public repo> missived && cd missived
scripts/selfhost/setup.sh --launcher YOUR-CODE
About 10 minutes
5
AutomaticYour computer opens an encrypted tunnel to us
WireGuard dials out to two of our relays, so no inbound port forwarding is needed on your router. Your network must allow outbound UDP; a TCP fallback is planned. If one relay goes down, the other carries on.
6
WePoint your name at your tunnel
Our relays learn that yourgroup.missived.app belongs to your tunnel. No waiting on DNS: every Missived name already points at the relays.
Under 90 seconds
7
AutomaticYour computer gets its padlock certificate
Let's Encrypt issues it straight to your computer through the tunnel. The key stays on your machine, and we never hold it.
8
YouOpen your new address and make the Owner account
Go to https://yourgroup.missived.app, sign up as the Owner, and invite your people. From then on, members' traffic passes through the relay encrypted, and only your computer can read it.
9
AutomaticUpdates look after themselves
When we release a version, your computer checks its signature, backs up, updates, and checks itself. If anything looks wrong, it rolls back to the last good version and tells you.

DNS + Tunnel with your own domain

Use chat.gracechapel.org instead of a Missived name. Your server is still at home behind the tunnel.

$100/yr or $10/mo, proposedNo router changesNo early-access queueLive in minutes, once open

1
YouGet a computer that stays on
Same as above: a small PC that stays connected.
2
YouChoose "Use my own domain" and pay
Type the address you want, for example chat.gracechapel.org. A subdomain like chat. works best.
3
WeShow you three records to copy
Your setup page lists them, filled in for you:
Type Name Points to

CNAME chat k7f2.relay.missived.app

CNAME livekit.chat k7f2.relay.missived.app

CNAME turn.chat k7f2.relay.missived.app
4
YouAdd them where you bought your domain
Log in to your domain company, open the DNS settings, add the three records, and click Check on your setup page.
5 minutes, then usually a few minutes for DNS to update
5
WeConfirm the domain is really yours
We look up the records from the public internet. Only someone who controls the domain can create them, so nobody can claim yours. We check again daily.
6
YouRun the setup with your code
The same two commands. The tunnel opens and our relays start passing your names through.
7
AutomaticYour certificate, with no waiting
The weekly certificate limit belongs to each domain. Yours has its own allowance, so you skip our early-access queue entirely.
8
YouOpen https://chat.gracechapel.org
Make the Owner account and invite people. Updates work exactly as above.

Type	Name	Points to
CNAME	`chat`	`k7f2.relay.missived.app`
CNAME	`livekit.chat`	`k7f2.relay.missived.app`
CNAME	`turn.chat`	`k7f2.relay.missived.app`

Missived DNS with a Missived name

Your server has its own public address (a VPS, an office server, or a home connection where you can open ports). Traffic goes straight to it; it never passes through us.

$50/yr or $5/mo, proposedNeeds a public IP and open portsLive in about 2 minutes, once open

1
YouGet a server with a public address
A VPS from any hosting company works. Open these ports in its firewall: 80, 443 and 7881 (TCP), 3478 and the call range 7882–7891 (UDP).
2
YouPick your name and pay
Choose yourgroup.missived.app and check out with Stripe.
3
WeSend your setup code
On screen and by email, when your early-access batch opens.
4
YouRun the setup with your code
The same two commands, ending in setup.sh --launcher YOUR-CODE. It tells us your server's public address.
5
WeCheck your server, then publish your name
We confirm a Missived server answers at that address, then create the DNS records so yourgroup.missived.app points straight at it.
Under 2 minutes
6
AutomaticYour server gets its certificate
From Let's Encrypt, straight to your server. Its key never leaves it.
7
YouOpen your address and make the Owner account
Members connect directly to your server. Run scripts/selfhost/doctor.sh any time to check ports, email and calls in plain words.
8
AutomaticManaged updates
Signed releases, a backup first, automatic rollback if anything fails.

Missived DNS with your own domain

Your server, your domain. We don't publish anything; the plan pays for hands-off updates (and the phone notification relay when the phone app ships).

$50/yr or $5/mo, proposedNeeds a public IP and open portsNo early-access queue

1
YouGet a server with a public address
Open the same ports: 80, 443, 7881, 3478 UDP and the call range.
2
YouPoint your domain at it
The same three A records as in "Your own domain" above.
3
YouChoose "Use my own domain", pay, get your code
The code links your server to the update service.
4
YouRun the setup with your code
Give it chat.gracechapel.org as the address.
5
AutomaticCertificate from your domain's own allowance
No queue. Your server is live as soon as setup finishes.
6
AutomaticManaged updates
Signed, backed up, rolled back if needed.

Words you'll see

A short glossary

Domain

A name you own on the internet, like gracechapel.org. You rent it yearly from a domain company. Our names (yourgroup.missived.app), once they're ready, mean you won't need one.

DNS record

An entry that says "this name lives at this address". Adding one takes a minute in your domain company's settings; changes usually spread within minutes.

Public IP address

The address the internet uses to reach a machine. Rented servers have one. Home connections often share one with the whole street, which is why the tunnel is planned.

Port forwarding

Telling your home router to send certain traffic to one computer. It's fiddly and some internet providers block it. The tunnel will mean you don't need it.

Certificate

What puts the padlock in the browser and encrypts the connection. Let's Encrypt issues them free; your server renews them automatically.

Tunnel and relay

Your computer keeps an encrypted line open to our relay. Members reach the relay, and it passes their encrypted traffic down the line to you without opening it.

How the tunnel will work

We'll carry the traffic. We can't open it.

Your server keeps its own certificate and its own keys. Cloudflare DNS points names at our relays without proxying the traffic. Caddy (layer-4, SNI passthrough) reads the destination hostname, then passes TLS through WireGuard to your box. It does not decrypt it. Calls have a separate UDP forwarding path through the tunnel.

Your membersbrowser · desktop · phone

relay.missived.appCaddy layer-4 · SNI passthrough

Your serverat home, holds the keys

What we'll be able to see

Client IP addresses, destination hostnames, connection times and traffic counts (to enforce fair use)
The hosted name, your billing details and your account email
When the updater checks in: its version and address

What we can't see

Messages, files, calls, member lists or anything inside your server
Your certificate's private key: it never leaves your box
Anything at all if you choose Do it yourself

Tunnel fair use (planned)

Plenty for a real group. Not a free CDN.

The tunnel is being sized for a church, a guild or a team running Missived from a spare computer. It isn't for hosting thousands of people through an old desktop; at that size, a server with its own address is the right fit.

400 GBthrough the relay each month

50 Mbpssustained

40people in calls at once

10 Mbpsif you go over, after a notice, never cut off silently

Questions

Straight answers

If it's open source, why would anyone pay?

You don't have to. The planned paid plans cover things that cost us money to run: the domain and certificates, the relay and its bandwidth, and the service that would update your server for you. The software and every feature are the same either way.

Can I buy Missived DNS or DNS + Tunnel today?

See Coming next — join the waitlist for the planned services. The free self-hosted edition is ready for early testers now.

When the paid plans open, what happens if I stop paying?

Your server keeps running and your data stays on it. The plan is to hold your hosted name for 60 days after 14 days of payment grace, and nothing is deleted without notice. You can switch to your own domain at any time and keep updating from the public releases.

Can I use my own domain?

Yes, on every path. Do it yourself needs one. On the planned paid plans your own domain also skips the certificate queue.

How is this different from the hosted Missived?

Hosted Missived is us running everything for you, priced by plan. Self-hosted is your server: every feature is on, there are no plan limits or prices inside the app, and you're responsible for backups and the hardware.

Do the desktop and phone apps work with my server?

Members use your server in any browser, and can install it as an app from the browser on computers and phones. The Missived desktop app connects to the hosted service only, for now.

My Mac or PC goes to sleep. Does that matter?

Yes: while it sleeps, nobody can reach your server. For a trial that's fine. For a group, keep it awake when plugged in (the Mac and Windows steps above show how), and know that a closed laptop lid still sleeps and Windows Update may restart it. For anything people depend on, use a Linux server.

Do I need a Docker Desktop licence?

Docker Desktop is free for personal use, education, non-commercial open source and small businesses (fewer than 250 people and under $10 million a year). A larger organisation needs a paid Docker subscription, which is yours to hold, not ours. On a Linux server you use Docker Engine, which has no such licence. On a Mac, OrbStack also works (check its licence too).

Why does Windows need WSL?

Missived's setup scripts are Linux scripts, and its parts run as Linux containers. WSL is Linux built into Windows, and Docker Desktop runs on it anyway. A separate PowerShell version would be a second copy to keep in step, so setup.ps1 only checks the Windows side and hands over to Ubuntu.

Has it been tested on Windows?

The Windows checks run in our automated tests on Windows, and the setup scripts are tested on Linux and macOS. A complete install on a real Windows PC, through to a call from another device, hasn't been run by us yet. If you try it, we'd like to hear how it went.

Can I fork it?

Yes, under AGPL-3.0. A public fork needs its own name and logo under our trademark policy, so nobody confuses it with Missived's releases.