Let us take it in order
Why a company needs secure access and what it covers
While the whole team sat in one office, access sorted itself out: the server was in the next room and could not be reached from outside. As soon as there are remote staff, a branch office or simply a work laptop on a trip, the picture changes. Access to internal systems has to be opened outwards — and that is when it turns out it is usually opened to everybody at once.
Secure access solves exactly that: an employee reaches the company's internal network through an encrypted channel, while for everybody else it is as if the network did not exist. The data travelling between a laptop and a server cannot be read on the way — not on hotel Wi-Fi, not in a café, not at the carrier.
What happens when it is missing
We usually see the same set: the server control panel exposed to the internet “temporarily, just while we set it up”, a database reachable at a public address, and eight people knowing the shared-folder password, two of whom no longer work there. Nothing happens right up until the day it does — and then it has to be reconstructed afterwards, with no logs and no idea whose access was used.
What exactly is encrypted
All work traffic between the employee's device and your infrastructure: files, database queries, internal panels, work correspondence in corporate systems. Personal traffic is not routed into the tunnel and is none of our business — in a properly configured setup it goes direct, which is a question both of speed and of respect for the employee.
What the work consists of
- Audit: what is already exposed, who uses what, and which access rights should have been closed long ago.
- Map: which roles exist in the company and what each of them should be able to reach.
- Setting up the access server on your side — on your own hardware or your own virtual server.
- Connecting devices: a separate key for each, any of which can be revoked.
- Split tunnelling, so that speed and calls do not suffer.
- Handover: documentation, administrator training, and the right to change everything without us.
Plainly about the limits
This is a corporate data-protection tool, not a universal answer to every security question. We set up secure access to your infrastructure — and to nothing else. If the database password is written in a shared file inside the network, encrypting the channel will not cure that: first order in the access rights, then the tunnel. We say so at the audit stage, even when the order was worded differently.
How long it takes
A standard setup for one company takes two to five working days, depending on the number of staff and the state of the infrastructure. The first connections usually work on day one. After that a week goes on quiet fine-tuning: there is almost always one employee with unusual equipment and one program that behaves differently from its documentation.
What is included
An access map
We work out who needs access to what: servers, databases, internal panels, file shares. The result is a map where every role has its own zone, instead of one shared door for the whole company.
An encrypted channel
We stand up an access server on your side. Traffic between an employee and your infrastructure travels in an encrypted tunnel rather than in the clear through a café, a hotel or a home Wi-Fi network.
A key per device
A separate key for each laptop, phone and workstation. Somebody leaves or a phone is lost — one key is revoked in a minute and the rest keep working.
Split tunnelling
Only work traffic goes through the tunnel; everything else goes direct. Speed does not suffer, and video calls and ordinary services behave exactly as they did before.
Linking offices and branches
A permanent secure channel between sites: shared folders, accounting systems and internal tools are reachable from any office exactly as from head office.
Handover and documentation
The server, the keys and the documentation stay with you. We show your administrator how to connect new staff and close access, so you never have to wait for a contractor.
We run the same setup ourselves
Our company is distributed: people, servers and internal services sit in different places and are linked by a secure channel. So we know not only how it is set up, but what starts misbehaving a week after launch.
Your own infrastructure, your own keys
Our internal services — the server, the bots, the working panels — are reachable by the team only through an encrypted channel, with a key issued per device. This is not advice copied from an article: we live with this setup every day.
Split tunnelling tested in practice
We know where it breaks in real life: a clash with corporate software, the wrong packet size, an application that stubbornly routes around the tunnel. Those things surface not during setup but in the second week of use.
We have dealt with real mobile networks
The classic complaint “it works on home Wi-Fi but not on mobile” is almost always the carrier's settings rather than a broken server. We have a worked-out diagnostic routine, so such cases are closed in an evening rather than a week of correspondence.
No shared password for the whole company
The “one login for everyone” approach falls apart at the first resignation: it has to be changed for everybody at once. We do not build it even when asked because it is faster — it costs more later.
Price list
The exact price follows an infrastructure auditReady to talk?
Tell us how many of your staff work remotely and which internal systems they need to reach — we will say which setup fits and what it will cost.