/ home›/ products›private networks

Private Networks

// subnets · firewalls · internal dns

Carve out a private network for your services. VMs talk to each other over a private IP space, the database isn’t on the public internet, and your firewall rules read like English.

Create a VPC Read the spec →
coming soon
subnets
/16 to /28
free with
every vm
internal dns
included
what you get

The good parts of private networks,
without the gotchas.

Sensible defaults so you can ship today, with the knobs you need when you grow up.

  • Private /16 by defaultplenty of room for an MVP
  • Firewall rules grouped by tag (e.g. tagweb → tag:db on 5432)
  • Internal DNS so you canhit `db.rumpty.local` from any VM
  • Multi-VPC peering when you needto split staging from prod
  • Egress rules per VMdefault-deny if you want it
  • Network ACLs you can readout loud and understand
$ rumpty vpc create --cidr 10.42.0.0/16 --name app-net → vpc "app-net" created · 65,534 hosts available
$ rumpty fw allow tag:web tag:db --port 5432 → rule "web→db:5432" added to app-net
the cli

One command
from idea to deployed.

Install the Rumpty CLI with one command. It's pipe-friendly, scriptable, and uses the same verbs on Linux and macOS.

curl -fsSL https://get.rumptycloud.com | sh
View on GitHub ↗Read the docs →
questions

People in Nigeria usually ask

Does RumptyCloud have a VPC in Nigeria yet?

Private networks are coming soon. Today, managed databases already sit on private networking, and firewall policies control inbound access to VMs and databases in Lagos.

What will a RumptyCloud VPC do?

A private IP space for your VMs, internal DNS, and tag-based firewall rules — so a web box can reach a database without putting that database on the public internet.

Private Networks is coming.

Drop your email and we'll ping you the day it goes live.

Create a VPC