Skip to content

Commit e43c821

Browse files
committed
fix why portal
1 parent 70e696c commit e43c821

1 file changed

Lines changed: 5 additions & 9 deletions

File tree

README.md

Lines changed: 5 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -10,17 +10,13 @@
1010

1111
## Why Portal?
1212

13-
Publishing a local service usually requires:
13+
Publishing a local service to the internet is often complicated.
14+
It usually requires opening inbound ports, configuring NAT or firewalls, managing DNS, and terminating TLS.
1415

15-
- Opening inbound ports
16-
- Configuring NAT or firewall rules
17-
- Managing DNS records
18-
- Terminating TLS at a gateway
16+
Portal removes this complexity by inverting the connection model.
17+
Applications establish outbound connections to a relay, which exposes the service to the public internet and routes incoming traffic back to the application while preserving end-to-end TLS.
1918

20-
Portal removes most of this setup by inverting the connection model.
21-
Applications establish outbound connections to a relay.
22-
The relay runs on a public base domain, assigns each service a subdomain,
23-
and routes incoming traffic while preserving end-to-end TLS.
19+
Unlike other tunneling services, Portal is self-hosted and permissionless. You can run your own relay on your domain or connect to any relay.
2420

2521
## Features
2622

0 commit comments

Comments
 (0)