Managed ingress
QUIC-native entry designed for fast connection setup, resilient sessions, and operator-friendly deployment.
Managed edge platform
Run private network access like a clean SaaS product.
Kuro Edge Cloud provides managed transport ingress, controlled outbound routing, and a polished HTTPS surface for distributed clients, automation, and operator-owned workloads.
Managed certificates
Multi-egress routing
Always-on supervision
Managed Transport
ACME Lifecycle
Policy Routing
Edge Observability
Regional egress
Multiple outbound profiles for separation, verification, and destination-aware traffic handling.
Policy controls
Private-range blocking, route hygiene, and explicit service shaping for safer default behavior.
Operator visibility
Traffic statistics and supervised runtime logs for troubleshooting, review, and capacity planning.
Service surface
Expose a normal HTTPS front end for browsers while keeping transport-specific access paths available for approved clients.
Routing profiles
Operate a direct path alongside isolated egress profiles for validation, regional testing, and controlled origin identity.
Delivery model
Deploy with isolated services, managed certificates, and system supervision while keeping a clean public-facing experience.
Platform snapshot
Public application face, private transport core.
The platform serves normal browser traffic over HTTP and HTTPS while transport ingress remains available for provisioned client connections.
- Application surfaceHTTP/80 and HTTPS/443
- Transport ingressManaged Hysteria over UDP
- Certificate lifecycleACME-managed domains
Workflow
From frontend trust to controlled outbound delivery.
Present
Users and scanners land on a stable HTTPS property with normal redirects, valid certificates, and predictable responses.
Connect
Approved clients negotiate transport through managed listeners while service boundaries stay isolated.
Route
Traffic exits through the selected profile while private and local ranges remain denied by default policy.
Managed ACME certificates across primary and egress service names.
Direct plus three controlled outbound routes for validation and separation.
Private ranges blocked, services isolated, and runtime supervised by default.
Operations status
Operational. Automated certificate renewal, service supervision, and route separation are enabled.
Provisioning model
Use approved client profiles for access. Service changes are maintained through operator-owned configuration and domain control.