korridor fits if…
- You cannot, or no longer want to, route your traffic through a hosted service.
- You need to connect remote sites without opening ports there.
- You want access granted to a person, for a set period.
korridor use case
Remote access without a third-party service
A hosted access service is easy to set up, but your traffic and identities pass through a third party, and its configuration escapes your reviews.
The short answer
With korridor, a remote site is published by connecting to your own entry point, without opening an inbound port. Roaming Linux devices reach the internal network with per-device rules. Traffic passes through no service operated by Koraisoft or any other third party.
Connecting a site without opening a port
The same korridor runs at both ends: the remote site calls the entry point, never the other way round.
- Inbound tunnel with no open port on the remote site
- Failover to the next point of presence if one does not respond
- An audit line when each flow opens and closes
Identity opens the network
A person proves their identity at the portal; the matching firewall rule opens, then closes when it expires.
- SSH, RDP or database access granted to an identified person
- Email code, authenticator app or passkey
- Device enrolment with explicit approval
- Removing a device also cuts its current tunnel
Is it the right tool for you?
Limits to know
- The roaming client currently runs on Linux.
- Web access goes through the portal, with no agent; network access from a device requires the korridor client.
- Pricing is still being defined.