Your apps. Your infrastructure.
Anywhere.
Jiji makes it simple to deploy and run applications across the machines you control. Cloud, bare metal, or your own hardware. Docker or Podman. One workflow to deploy, connect, and manage your apps without locking your infrastructure to a platform.
curl -fsSL https://get.jiji.run/install.sh | shDEPLOY ON YOUR SERVERS.
ROLL OUT SAFELY.
Turn the Linux servers you already control into one repeatable deployment target, with health-gated rollouts, automatic HTTPS, private networking, and service discovery built in.
YOUR INFRASTRUCTURE
Cloud VMs, dedicated servers, bare metal, or hardware at home. If it runs Linux and you control it, Jiji can make it part of your deployment workflow.
KEEP COSTS PREDICTABLE
Pay infrastructure providers directly and grow on your terms. Keep the same deployment workflow as you add servers and move across providers.
PRIVATE NETWORKING BUILT IN
Jiji connects your servers with an encrypted WireGuard network and private DNS, so services can communicate across hosts without exposing internal traffic publicly.
ONE PRIVATE NETWORK. EVERY SERVER.
Add servers wherever you need them across cloud providers, datacenters, or your own hardware. Jiji connects them with private networking and service discovery, so your applications can communicate across machines by name.
Below is an example of how a multi-server Jiji deployment can fit together.
web1 Containers(2 active)
Tracked in the project's service catalog, reachable by name from any server
WHERE JIJI FITS
Match your deployment approach to the size of your application, infrastructure, and operations team.
DOCKER COMPOSE
Great for single-server setups, but it does not provide Jiji's multi-server coordination, health-gated rollout workflow, or built-in private mesh networking.
JIJI ORCHESTRATOR
Multi-server coordination, private networking, and health-gated routing without standing up a separate control-plane cluster.
KUBERNETES
Powerful and flexible, but it brings substantially more infrastructure, operational machinery, and a steeper learning curve.
PRODUCTION TOOLS, READY TO USE
Deploy and operate applications across your servers from one CLI, with networking, HTTPS, health checks, logs, and scheduled jobs built in.
AUTO SSL / TLS
Issue and renew HTTPS certificates automatically through jiji-proxy without manual Caddy or Nginx boilerplate.
FAIL-SAFE HEALTH CHECKS
Discard failed candidate containers while the currently healthy version keeps serving live production traffic.
SECRETS MANAGEMENT
Load secrets from environment files without placing them in deployment command strings or Jiji's own logs.
STANDARD CONTAINER REGISTRIES
Use standard container registries such as GHCR, Docker Hub, ECR, or Artifact Registry, or use Jiji's local registry workflow over SSH.
AUDIT TRAIL
Inspect deployment history and stream application logs in real time across your server fleet.
SCHEDULED JOBS
Run service commands on a cron schedule in isolated containers with durable execution status and log history.
WHAT TEAMS ASK BEFORE DEPLOYING
Deep dive into architecture, rollbacks, registries, and multi-server setup.
The Jiji CLI runs on your machine or CI runner. It connects over SSH to the selected servers and any hosts that own affected state, applies the deployment, and exits. A per-project jiji-agent remains on each server to maintain networking, DNS, and service state, while jiji-proxy handles configured ingress.
# Execute from your local machine or GitHub Actions / GitLab CI $ jiji deploy --build
YOUR NEXT DEPLOY
CAN BE BORING.
Go from a fresh Linux server to a healthy HTTPS deployment with one configuration file and a repeatable, health-gated rollout.