Reoclo Docs

Reoclo is a DevOps-as-a-Service platform built for teams that want to deploy on their own infrastructure. Connect any Linux server with an IP address, link your GitHub repositories, and ship releases without handing your runtime over to a single cloud vendor.

What You Can Do with Reoclo

• Connect any Linux server: Install the Runner agent. Works with Hetzner, AWS, DigitalOcean, bare metal, or anything running Linux.
• Link GitHub repositories: Install the GitHub App once. Reoclo receives push webhooks and generates short-lived clone tokens. No long-lived credentials stored.
• Deploy with Docker: Images are built directly on your servers. No central registry. No image transfer overhead.
• Blue-green deployments: Automatic health checks and rollback. Old containers restart on failure, removed on success.
• Team-based access control: Manage multiple teams with role-based permissions. Users can belong to multiple organizations.

Getting Started

Start here if you’re new to Reoclo:

• Quickstart: First deployment in under 10 minutes
• Core Concepts: Understand organizations, servers, applications, and deployments
• GitHub App Setup: Connect your repositories and enable auto-deploy

How It Works

Reoclo follows a four-step deployment model:

1. Install the GitHub App: Connect your repositories. Reoclo receives push webhooks and generates short-lived tokens for cloning.
2. Add a server: Install the Runner agent with a one-line command. Reoclo verifies connectivity and marks the server ACTIVE.
3. Create an application: Map a repository, branch, and Dockerfile to a server. Configure runtime settings (port, health check, environment variables).
4. Deploy: Click “Deploy” or push to the configured branch. Reoclo clones the repo, builds the Docker image on your server, starts the new container, runs health checks, and cuts over traffic.

All builds happen on your servers. Images never leave the target host.

Platform Architecture

Reoclo is provider-agnostic. Any Linux server with Docker, git, and curl can be a deployment target. You can also connect cloud credentials (Hetzner, DigitalOcean, AWS, Vultr, Linode) for managed provisioning and power operations.

Runner Agent

Every server connects via the Runner agent — a lightweight Node.js agent installed on your server. The agent makes an outbound WebSocket connection to Reoclo. Commands are relayed through this connection, so no inbound ports are required. The agent handles reconnection automatically.

Deployment Pipeline

When you trigger a deployment (manually or via git push), Reoclo schedules the deployment and runs the pipeline on your server:

1. Precheck: Verify git, docker, and curl are installed.
2. Clone: Securely clone the repo onto the target server using a short-lived token.
3. Build: Run docker build directly on the target server. Images are built locally.
4. Deploy: Stop the existing container, start the new one with environment variables. Blue-green swap within the same host.
5. Health check: Poll the configured health check path via curl on the server.
6. Cleanup/Rollback: On success, remove the old container. On failure, restart the old container and mark the deployment FAILED.

All deployment execution happens on your server. Reoclo orchestrates, but the build and runtime stay on your infrastructure.

Next Steps

• Servers Overview: Learn about server lifecycle, health monitoring, and connection types
• Deployments Overview: Understand the deployment pipeline and rollback behavior
• Security: Encryption, access control, and organization isolation
• API Reference: Integrate Reoclo into your workflows

If you run into issues, check the deployment logs in the dashboard or contact support.