CloudRivetworking nameJoin the beta
Private design-partner beta · roadmap open

Your servers.
Heroku-like deploys.
We operate the platform.

CloudRivet is the managed control plane for teams that want simple Git deployments on affordable infrastructure—without owning every upgrade, certificate, backup, and 2 a.m. recovery.

Apply for the beta See how it works

No payment or server credentials are collected on this website. Beta onboarding is human-led.

fleet / production All systems healthy
GOOD MORNINGYour fleet
production-nycUbuntu · Dedicated VM
RUNTIMESupported
APPS4 running
Healthy
Latest deployment2m ago
↗
api · main8c2f1a4 · Fix invoice retry
Live
ReceivedBuiltReleasedHealthy
Managed operationsThis week
  • ✓TLS renewedshop.example.com
  • ✓Backup verifiedRestore test passed
  • ↻Update availableAwaiting canary
◇

Dedicated runtime boundaryOne customer or organization per VM

↗

Outbound-only managementNo permanent root SSH key in the control plane

✓

Recovery that gets testedIntegrity checks plus restore drills

THE OPERATIONS GAP

You wanted affordable infrastructure.
You got another on-call rotation.

Self-hosting cuts platform markup, but it quietly hands your team the work behind the platform. CloudRivet is designed to own the repeatable operational layer while your applications remain on servers you control.

01

Connect a clean server

Admission checks, runtime bootstrap, node identity, and fleet health in one guided enrollment.

ZERO-TOUCH TARGET
02

Ship from Git

Traceable deployments, domains, TLS, config, logs, restart, and scale—without exposing a browser shell.

TYPED OPERATIONS
03

Recover with evidence

Encrypted backups, integrity metadata, safe runtime canaries, and restore tests you can actually inspect.

MANAGED RELIABILITY
HOW IT WORKS

A control plane above.
A dedicated node below.

The customer-facing product stays separate from the open-source runtime. A small agent accepts only known, typed actions and calls supported runtime interfaces on the node.

What ships in the MVP

Apps, deployments, environment configuration, domains, TLS, logs, restart, scale, fleet health, managed updates, billing, and a PostgreSQL/config backup beta.

What does not

Shared hostile-tenant Docker hosts, browser terminals, arbitrary shell execution, Kubernetes clustering, custom build systems, or enterprise SSO.

BUILT AROUND OPERATIONS

The dashboard is the receipt,
not the whole product.

Every surface is designed around a real operational outcome: what changed, who requested it, what node ran it, whether it passed, and what happens next.

↗

Git-triggered deploys

Signed webhook intake, queued releases, deployment history, and clear failure states.

P0 · MVP
⌁

Fleet health

Heartbeats, runtime version, disk/load signals, app health, and upgrade readiness.

P0 · MVP
◇

Domains + TLS

Known domain operations and certificate lifecycle without handing users a root shell.

P0 · MVP
◈

Safe configuration

Encrypted writes, redacted reads, secret-safe logs, scoped permissions, and audit events.

P0 · MVP
↻

Canary updates

Internal validation, preflight backup, post-update checks, and a human stop path.

P0 · MVP
✓

Backup + restore beta

PostgreSQL and config first, with encryption, hashes, retention, and restore evidence.

P1 · BETA
PROPOSED BETA PACKAGING

Pay for operational ownership,
not another pretty console.

DEVELOPER

Keep one server calm.

$19/ server / mo
  • Dashboard and Git deployments
  • Domains, TLS, logs, and health
  • Managed update notifications
  • Community-priority support
Request beta access
DESIGN-PARTNER FIT
PRO

Operate production with backup.

$49/ server / mo
  • Everything in Developer
  • Backup and restore beta
  • Alerts and longer event history
  • Priority managed-operations support
Apply as a design partner
TEAM

Give a small team guardrails.

$99/ server / mo
  • Everything in Pro
  • Members and role-based access
  • Audit history and export
  • Priority response target
Discuss your fleet
Pricing is a beta proposal, not a live checkout offer.No payment flow is connected, and final packaging will be validated with design partners.
EIGHT-WEEK BUILD ORDER

Revenue-ready means
the risky work is visible.

The roadmap starts with identity, isolation, and typed operations; it earns the right to add billing only after the runtime boundary is testable.

  1. 01
    Weeks 1–2Commercial and technical foundation

    A legally separated product boundary and a testable control-plane skeleton.

  2. 02
    Weeks 2–3Secure server enrollment

    A fresh customer VM can become a known, observable, dedicated runtime node.

  3. 03
    Weeks 3–5Daily application operations

    Customers can safely run the common application lifecycle without a shell.

  4. 04
    Weeks 5–6Git delivery and revenue loop

    A design partner can connect code, deploy it, and enter a paid managed-service relationship.

  5. 05
    Week 7Recovery and safe upgrades

    The product can prove recovery instead of merely claiming that backups exist.

  6. 06
    Week 8Design-partner paid beta

    A deliberately small cohort pays for managed reliability and produces evidence for the next build.

Open the full MVP roadmap
STRAIGHT ANSWERS

Before you hand a platform your production server.

Is CloudRivet a hosting provider?

The MVP is a managed BYO-server control plane. Your applications run on a dedicated VM you own or provision for your organization. Fully managed hosting is post-MVP.

Does this copy or rebrand Dokku Pro?

No. The plan is an independently designed control plane and node agent using public interfaces from the open-source Dokku runtime. It does not use Dokku Pro code, UI, or assets.

Can the browser run arbitrary commands?

No. The MVP contract explicitly excludes browser terminals and generic shell RPC. The agent accepts a versioned allowlist of typed operations with identity, expiry, and idempotency controls.

Is the product already production-ready?

No. This repository is the website and execution foundation for a private design-partner beta. The roadmap, security gates, and issue tracker define what must be proven before any broader launch claim.

LOOKING FOR DESIGN PARTNERS

Bring the server.
Keep the ownership.
Lose the platform chores.

Tell us what you run, where it is hosted, and which operational burden costs you the most time.

Apply for the private beta