Corporate gateway on Xray and nginx for an IT team
for an IT company: work tools available again, on its own servers
A corporate gateway for an IT company: secure traffic routing on the company's own servers, so the whole team can use Canva, Notion, Jira and AI tools again without public workarounds.
The task
Because of regional restrictions, an entire IT company's team lost access to Canva, Notion, Jira and AI tools at once. Work stopped and deadlines were burning. Public workarounds risked leaking corporate data and violated the company's security policy.
The solution
We deployed a sovereign corporate routing infrastructure on the company's own servers. Routing means directing traffic to the right resources by set rules. Sovereign here means the servers and data stay under the company's control, with no intermediaries.
- End-to-end traffic encryption.
- Role-based access control for employees.
- A single entry point: stable, transparent one-click access to all work resources.
How it works
A single entry point for employees
An employee connects to the corporate gateway, and work traffic then flows through it to the required services. The gateway runs on the company's Linux servers; the stack includes Xray (a proxy-protocol core) and nginx (a web server at the entrance). Access rights depend on the employee's role.
Results
- The team's tools are accessible again.
- Corporate data stays inside the company's perimeter.
- Connecting takes an employee one click.
Technologies and why
- Self-hosted β everything on the company's servers, no third-party cloud.
- Linux β the server foundation.
- Xray β traffic routing and encryption.
- nginx β the gateway's entry point.
Status
Completed. The client asked us not to disclose the company name. Other details about the client are not disclosed.
Questions about this project
What problem does the corporate gateway solve?
Where does the gateway run and who owns the data?
How is employee traffic protected?
Is it hard for an employee to connect to the gateway?
Why not use public services for bypassing restrictions?
More in this area
Peregovorka (ToshaStream): streaming server and team voice chat
our own product in production, version 1.50.0: voice, chats and a private stream
VPN infrastructure: Russian entry node, European exit
our own product: a relay in Russia, a persistent tunnel and a node in the Netherlands
A private server for several websites on Docker and nginx
our own product: site isolation, HTTPS, self-hosted mail and backups
Need something similar?
Tell us about the task β we'll show how we solved it and estimate the scope.