Quickstart

Mezite has two quickstart paths. Both end with you SSH-ing into a node through a Mezite proxy in a single sitting. Pick whichever matches how you want to run the hub.

Path A — Managed mezhub (cloud.mezite.com)

You sign up on cloud.mezite.com, pick a workspace slug, then create a hub in your chosen region — the managed control plane provisions a mezhub for you. Three short pages take you from "I have nothing" to "I have an SSH session":

  1. Managed mezhub — sign up, provision the hub, log in with mezctl, and mint a node-join token.
  2. mezd — install the node agent on a Linux host, join the managed hub with the token from the previous step, and watch the reverse tunnel come up.
  3. msh — install the client CLI on your laptop, log in to the hub, and SSH (and scp) into the node you just enrolled.
Pick this path if you want someone else to operate the hub — upgrades, TLS, and the database are all handled for you. The managed hub is also the fastest way to evaluate Mezite end to end.

Path B — Self-Hosted

You run mezhub yourself on a Linux or macOS host backed by SQLite or PostgreSQL, and connect to it from mezd on the same host or another machine.

  • Self-hosted quickstart — a single-page, single-host walkthrough that boots the server, enrolls one node, and opens an SSH session.
Pick this path if you want full control of where the hub runs, or you want to evaluate Mezite without creating a cloud account. The Systemd and Podman guides cover production hardening once you are past the quickstart.

Not sure which to pick?

Start with the managed quickstart. It removes the most variables — no host to provision, no database to install, no TLS to manage — so you can confirm the end-to-end model fits your use case before deciding whether to self-host.