Bring your own server

Connect a server you already own. We orchestrate it.

Wemazu is the hosted control plane for servers you control. You deploy from GitHub over SSH or FTP, map branches to environments, watch server health and roll back when you need to. You install nothing and you maintain nothing. There's no agent to run and no daemon to keep alive.

Works with any VPS, over SSH or FTP, fully self-hosted.
wemazu.com/dashboard
Simuze music community ● live
Deployments
145
Success
99.1%
Servers
3
main → staging ● Queued
Managed, zero maintenance

You install nothing.

Most platforms rent you their infrastructure. Wemazu does the opposite. It's the hosted control plane that drives a server you already own, so there's no agent to babysit, no daemon to keep alive and no platform to patch.

The structural moat

Reaches where Docker can't.

SSH gets you onto your VPS. FTP reaches the humble shared host that has no root and no daemon, the kind of place Docker-based tools simply can't go. One control plane, both reaches.

Inside the control plane

A calm command centre for your servers.

Overview
Overview
Fleet health, live deploys and what needs a look, in the first three seconds.
How it works

From zero to live in under two minutes.

01
Connect your Git provider
GitHub today, with GitLab, Bitbucket and self-hosted Gitea coming soon. Authenticate, pick a repository, and Wemazu reads your branches, nothing else.
02
Add your server
SSH with automatic key generation, or FTP credentials for shared hosting.
03
Link domain & branch
Map a branch to an environment and deploy path. Staging and production, separated.
04
Deploy
Push to deploy, or trigger by hand. Watch staged progress and live logs in real time.
One push, every server

Watch it reach each box you own.

You push once. Wemazu fans the deploy out over SSH and FTP, lighting up every environment in turn, then flips the domain live.

Your Git repo
push to main
Wemazu
waiting for push
Everything you need

Built for reliability, not complexity.

Branch → environment
Map each branch to a server and deploy path. Staging and production stay separate.
Domains & auto-SSL
Add domains, watch certificate status, multiple domains per project.
Health monitoring
CPU, memory, disk and reachability per server, with historical metrics.
Instant rollback
Revert to any previous deployment in one move. Safe, obvious, reassuring.
Live logs
Streaming, searchable console with severity levels and a per-deploy debug override.
Database sync
Move data between environments deliberately, with the direction made explicit.
Team & roles
Invite members, assign roles, control who can deploy where.
Orchestration
One control plane conducting every server, deploy and domain you own.
Predictive by default

It warns you before the deploy breaks.

Most tools tell you a deploy failed. Wemazu watches the two things that actually cause it — a disk filling up, a host going quiet — and flags them before you push. When a health check does fail, it already knows which build was the last good one, and offers to roll back in a single tap.

  • ▹Disk and reachability watched per server, so a failure never surprises you.
  • ▹Health-gated go-live — nothing ships until the server answers healthy.
  • ▹One-tap rollback to the last green build, on desktop or your phone.
Wemazu noticedbefore it became a problem
!
Nefos VPS 1 disk is nearly fullPredicted
92% used. Your next deploy will likely fail. Free space before it runs.
↺
Roll back to the last healthy deploySuggested
#146 failed its health check. #144 was the last green — one tap restores it.

What is Wemazu?

Wemazu is a deployment orchestration platform for Git repositories. It connects to servers you already own over SSH or FTP and deploys your code when you push. There are no CI/CD pipelines to configure and no vendor lock-in, and nothing about it is a black box.

You map branches to domains, roll back to any previous deployment, monitor server health, sync databases and work together as a team. It runs on any VPS provider, whether that's DigitalOcean, Hetzner, AWS or a bare-metal box in a cupboard, and it reaches the shared hosts that Docker-based tools can't. Your infrastructure stays yours.

Latest from the blog

View all posts →
Nov 18, 2025 · 5 min read
Feature flags and real rollback
A feature flag system with a bounded kill-switch is one table, one function, one circuit breaker. That's what rollback looks like for small teams.
deployment
Nov 11, 2025 · 6 min read
Git hooks for deploy discipline
A three-line pre-push hook stops a specific class of Monday-morning incident. The hook is in the repo. The habit is in the hook.
git
Nov 3, 2025 · 5 min read
The 30-second deploy timeout
mod_fastcgi's idle timeout is exactly 30 seconds. Under cgi-fcgi, flush() does nothing. The only fix that worked was calling exit() right after.
deployment
Wemazu Desktop · macOS

Deploy without opening a tab.

A command palette on ⌘K, native notifications when a deploy lands, and the same zero-footprint promise. The .dmg is out now. Windows and Linux follow.

Download for Mac 1.1.0 · 10.0 MB · macOS 13+
⌘K Deploy main → production ↵
Simuze deployed to Nefos VPS 1 now
Windows and Linux coming later
In the wild

Built for the people who run their own servers.

We run fifteen client sites on shared hosting. Wemazu is the first tool that deploys to all of them without anyone touching FTP by hand.

JV
Joost Verheijen
Founder, agency in Utrecht

The health check that waits before cutover saved us twice. A bad build never reached visitors, it just did not go live.

AA
Aïsha el Amrani
Freelance Laravel developer

I deploy to my own VPS, but I wanted to stop babysitting the box. Wemazu drives it from the outside and I install nothing.

TN
Tomáš Novák
Solo SaaS, Prague
Trusted with production by teams running WordPress Laravel Vue Astro How we keep it safe →

Start deploying in minutes.

Connect your repository, add your server, and you're deploying.

Create account