Networks & connectivity
Sencai has two different places that talk about “networks,” and they do different things. Live cloud → Networks changes the actual private network at your cloud provider. Networking & Edge → Networks keeps a record in Sencai - useful for planning and documentation, but it does not touch anything at the provider. This page covers both.
Live cloud → Networks (your real infrastructure)
Section titled “Live cloud → Networks (your real infrastructure)”Live cloud → Networks (/gravity/live-cloud/networks) reads and changes the actual private
network (VPC) at your connected cloud provider account. Creating a network
here creates a real network. Deleting one deletes it for good.
Before you do anything on this screen, pick the connected cloud account at the top of the page. A persistent bar always shows which provider, account, and organization you’re currently pointed at, plus when data was last loaded from the provider - if you haven’t connected a cloud account yet, do that first.
The network list shows each network’s name, its ID at the provider, IP range, zone, subnet and route counts, and how many servers are attached.
Creating a network
Section titled “Creating a network”- Click New network, give it a name and an IP range (the provider only
accepts a private range -
10.x,172.16–31.x, or192.168.x). - Optionally add a first subnet at the same time: a type, an IP range that falls inside the network’s range, and a network zone.
- Confirm. The network is created directly at the provider.
Subnets, routes, and IP range are separate actions
Section titled “Subnets, routes, and IP range are separate actions”Editing a network’s name only changes its name - the provider ignores subnet, route, and IP-range fields on that same request, so each of those has its own dedicated action instead of one combined “edit network” form:
- Add Subnet from the network’s expanded row; remove one with the Remove subnet at the provider button on the subnet’s row.
- Add Route - a destination CIDR and a gateway address that must fall inside one of the network’s subnets; remove one with the Remove route at the provider button on the route’s row.
- Change IP range - a separate, higher-friction action reached from an icon button in the network’s row: you type the network’s name to confirm, because the provider will refuse the change if any attached server would fall outside the new range, and a server that doesn’t fall outside can still lose connectivity briefly while the change applies.
Deleting a network
Section titled “Deleting a network”Deleting is immediate and irreversible at the provider. If servers are attached, they lose private connectivity through that network. You confirm by typing the network’s name.
Networking & Edge → Networks (your planning record)
Section titled “Networking & Edge → Networks (your planning record)”Networking & Edge → Networks (/gravity/networks) is a different
screen with a similar name - it keeps a record of networks in Sencai’s own
database, independent of what actually exists at any provider. Use it for
design intent, documentation, or planning; nothing you do here changes
real infrastructure. Fields include provider, region, and CIDR block, and
records can be created, edited, and deleted freely without touching your
cloud account.
The same section groups a few related planning tools:
- Network Policies (
/gravity/networks/policies) - named, priority-ordered rule sets you can enable or disable, useful for documenting the access rules you intend a network to enforce. - Policy Templates (
/gravity/networks/templates) - reusable starting points (allow web, restrict internal, zero trust, database only, or a custom template) you can apply to a policy instead of building one from scratch. - Cross-Cloud (
/gravity/networks/connectivity) - a status view of connections between networks across providers, showing latency, packet loss, and BGP session state where applicable, refreshing automatically. - VPN, from a network record’s own detail page
(
/gravity/networks/[id]/vpn) - gateway and connection records for that network, including a pre-shared key generated in your browser that is shown once and never stored anywhere in the interface after you save it.
What’s next
Section titled “What’s next”- Firewalls & security groups - the same live vs. record distinction, applied to firewalls
- DNS - same pattern again, for DNS zones and records
- Connect a cloud provider - required before Live cloud screens have anything to show
- Regions