Private by default — no public SSH route on MVP instances

Cloud infrastructure without the exposed surface

Create and operate application infrastructure without needing to understand Proxmox, tunnels, or VLANs. Your servers get a private hostname and a stable project IP — reachable from your enrolled devices, and nowhere else.

GuildCloud is not an AWS replacement at launch. It is a focused, trustworthy private cloud first — and every claim on this page is written to match what has actually been tested.

Private access

No public SSH route on MVP instances

Clear recovery

Restores are tested before they are promised

Wallet-first

Costs stay visible before anything is created

A calm, dense operational console

DigitalOcean-style guided clarity with Hetzner-style compact operational detail. Slow work is never hidden — provisioning streams its stages, and failures tell you which stage failed.

console.guildcloud.io/instances/api-prod-1

Private hostname

api-prod-1.core.guild.internal

Hourly price

$0.062

Monthly maximum

$44.64

ssh saurabh@api-prod-1.core.guild.internal
PreparingCreatingConfiguring private accessTesting connectionReady

What GuildCloud promises

Each service ships with an explicit boundary. If something is not offered yet, it says so here rather than in a support ticket later.

Guild Instances

Private virtual servers with supported OS images, safe resize, volumes, backup, monitoring, and SSH keys.

Boundary: No public VPS IP or public SSH in the MVP.

Guild Kubernetes

One project-isolated shared managed cluster per site.

Boundary: Dedicated clusters are a future premium module.

Managed PostgreSQL

Private managed PostgreSQL with backup, recovery, and monitoring.

Boundary: MySQL is future work.

Object Storage

S3-compatible application and file storage with versioning.

Boundary: Storage classes expand later.

Guild Volumes

Expandable block storage for instances and persistent workloads.

Boundary: Disk shrinking is not offered in the MVP.

Guild Functions

Node.js and Python functions for HTTP, schedules, storage events, and PostgreSQL events.

Boundary: Container runtime is advanced/future.

Private access, without the homework

Public-IP server access creates exposure and setup work you did not ask for. GuildCloud instances have no public IP at all. Your laptop and your servers each establish outbound encrypted connectivity, and your project policy decides who can reach what.

  • A stable private project IP and a friendly private hostname per instance
  • Individual named administrator accounts with sudo — not shared root
  • SSH keys on by default; password SSH is opt-in, private-route only, and never stored by GuildCloud
  • Removing a teammate revokes network permission and server login together
  • A browser recovery console for exceptional recovery, not ordinary use

Network zones

ManagementNever customer reachable
TenantYour project users and workloads only
BackupNever customer reachable
EdgeFuture — only for explicitly published apps

You never talk to Proxmox directly. GuildCloud owns the control plane; Proxmox is the execution plane behind it.

Recovery you can actually check

A backup is not considered valid until a restore drill proves it can be used. These tiers describe workflows that have been run, not aspirations.

Standard

Included

Daily encrypted off-site backup, seven-day retention, and restore into a healthy site.

Included baseline on every resource.

Protected

Paid add-on

More frequent recovery points, a longer retention option, and priority restore handling.

For workloads where a day of loss is too much.

Warm Standby

Premium

A prepared secondary-site recovery workflow, offered only after real full-site drills pass.

Limited capacity. No active-active promise.

No untested SLA and no active-active promise. Multi-site application placement applies only to compatible stateless Kubernetes and function workloads — it is not ordinary VM protection.

Costs you can see before you commit

GuildCloud is wallet-first. Every metered event becomes an explainable ledger entry, and the hourly price and monthly maximum appear before anything is created.

Before creation

Hourly price, monthly maximum, protection, storage, and add-on costs.

One wallet

Per organization, with optional auto-reload you configure.

Local payment rails

Paystack and Flutterwave, with methods suited to your country and currency.

No silent deletion

Payment failures get retries, notice, and a documented grace period.

Plan sizes and prices are derived from measured site capacity. Nothing is advertised that cannot be consistently delivered.

Start building, or talk it through first

Anyone can sign up and explore. Email and payment verification are required before paid resources are created — and larger limits or custom recovery go through a conversation.