VPS

Virtual Private Servers (VPS) on tasmanian.cloud provide self-service compute through the REST API, with the portal, CLI, and SDK available as clients.

Overview

Our VPS offering is designed for:

• Self-hosted applications you want full control over
• Private workloads that need Tasmanian sovereignty
• VPN-only access via encrypted mesh VPN for secure external connectivity
• Development environments with predictable performance

What We Don't Offer

We intentionally do not provide:

• Public IPs or floating IPs (limited IPv4 resources)
• GPU instances (no L40S hardware)
• General-purpose compute at hyperscale prices

Instead, we focus on sovereign, self-hosted solutions with private networking.

Architecture

flowchart TB
    subgraph "Your Infrastructure"
        PORTAL[Customer Portal]

        subgraph "Private Network"
            VPS1[Your VPS]
            VPS2[Your VPS]
        end

        subgraph "Access Methods"
            VPN[Encrypted VPN]
            CONSOLE[Web Console]
        end
    end

    subgraph "Compute Cluster"
        NODE1[Compute Node 1]
        NODE2[Compute Node 2]
    end

    PORTAL --> VPS1
    PORTAL --> VPS2
    VPS1 --> VPN
    VPS2 --> VPN
    VPS1 --> CONSOLE

    NODE1 --> VPS1
    NODE2 --> VPS2

Instance Types

All instances run on AMD EPYC 7443 processors with NVMe storage.

Getting Started

1. Access Customer Portal

Contact us at hello@tasmanian.cloud to get access to the customer portal.

2. Create a VPS

Create via CLI:

tc vps create \
  --name my-server \
  --size standard-4vcpu-8gb \
  --image ubuntu-24.04 \
  --ssh-key ~/.ssh/id_rsa.pub

Or use the web interface:

1. Click "Create VPS"
2. Select your instance type
3. Choose an OS image (Ubuntu, Debian, Alpine)
4. Add your SSH public key
5. Select or create a private network
6. Deploy

3. Connect via VPN

Since instances don't have public IPs, access is via encrypted VPN:

Connect to VPN (using your setup key from the dashboard):

vpn-client connect --setup-key YOUR_SETUP_KEY

Then SSH to your VPS:

ssh ubuntu@your-vms-private-address

4. Web Console

For emergency access without VPN, use the web console in your dashboard:

1. Go to VPS > Your Instance
2. Click "Console"
3. Authenticate with your credentials

Networking

Private Networks

All VPS instances are deployed into isolated private networks. You can create custom networks for isolated environments.

VPN Access

External access is exclusively via encrypted mesh VPN:

Why VPN-only?

• Enhanced security by default
• No accidental public exposure
• Sovereign network boundaries
• Zero-trust architecture

Inter-VPS Communication

VPS instances in the same private network can communicate directly using their private addresses.

Images

Available operating systems:

Custom images can be uploaded via API:

tc vps images upload --name my-custom-image --file ./image.qcow2

Storage

Root Disk

• NVMe-backed storage
• Minimum 50 GB
• Expandable up to 2 TB
• Snapshots supported

Additional Volumes

Attach block storage to your VPS:

Create a volume:

tc storage volume create \
  --name my-data \
  --size 500GB

Attach to VPS:

tc vps attach-volume my-server --volume my-data

Snapshots

Create point-in-time snapshots:

# Create snapshot
tc vps snapshot create my-server --name "before-update"

# List snapshots
tc vps snapshot list my-server

# Restore
tc vps snapshot restore my-server --snapshot "before-update"

Security

By Default

• No public IP exposure
• Firewall blocks all inbound (you configure allow rules)
• Automatic security updates enabled
• Fail2ban installed
• Unattended-upgrades for critical patches

SSH Access

Add your SSH key during VPS creation via the customer portal for secure access.

Firewall

Configure firewall rules via the customer portal to control inbound access to your VPS.

Pricing

Example: standard-4vcpu-8gb with 100GB storage = $52/month

Troubleshooting

Can't SSH to VPS

1. Verify VPN connection is active
2. Check firewall rules in your dashboard
3. Use web console for emergency access
4. Verify SSH key was added correctly

Network Issues

1. Verify VPS is in correct private network
2. Check VPN connection status
3. Test connectivity to your gateway

API Reference

See API documentation for full REST API details.

Related Documentation

• Templates - One-click app deployments
• Kubernetes - Managed K8s clusters
• Networking - VPN and private networks
• CLI Reference - Command-line tool