Every Nevia Computer and Database gets its own name, URI and ready-to-use endpoint secured with TLS. Private networking and egress controls are on the roadmap.
Every Nevia Computer and Database gets its own name, URI and ready-to-use endpoint secured with TLS. Private networking and egress controls are on the roadmap.
| Public endpoints | Private networking | |
|---|---|---|
| What it is | A DNS name and TLS endpoint per machine | Private connections between your Computers and Databases |
| Best for | Apps, APIs and databases reached from anywhere | Applications that communicate across Computers and Databases without public endpoints |
| Protocols | HTTPS (HTTP/1.1, HTTP/2), Postgres over TCP with TLS | — |
| Status | Available | Roadmap |
Public endpoints
Each machine is named in DNS and reached through an ingress proxy on its host, which routes traffic to the destination VM. Computers get HTTPS URLs for the ports they publish, with TLS handled for you. Databases are reached via a standard Postgres TCP connection, with TLS passed straight through to the database instance.
Benefits
- Ready to connect: Create a machine and it is already addressable. No load balancers, certificates or DNS records to set up.
- Wakes on connection: A sleeping machine resumes when a client connects.
- Control traffic stays off your network: Shell, console and file transfer use a separate channel, so they never touch the machine's network or its rules.
Private networking and egress control
We are building private connections between your workspace Computers and Databases, with default-deny egress with per-machine allowlists. You decide what each machine can reach.