Plexus
Work · Infrastructure · production

Private office infrastructure

Virtualized office computers, secure remote desktops, one account per person, an internal dashboard.

Problem
Staff needed to work on office machines remotely, with separate accounts and lines.
Built
Virtualised office computers reached through the browser, one account per person.
What changed
Around twenty people work remotely with nothing open to the internet.
Employee → Browser → Guacamole → VM → Office networkAnywhereGatewayOfficeEmployeeBrowserGuacamoleVMOffice network
Office machines from any browser, nothing open to the internet.

The story

  1. 01 · Problem

    Staff needed to work remotely on office machines with separate accounts and separate internet lines, without exposing the office.

    What had to change
    Who needs which machine, through which line, with what visibility for managers.
  2. 02 · System

    Virtualised office computers, secure remote desktops from a browser, one account per person, an internal dashboard showing who's online, two separate internet lines.

    Connected
    Guacamole REST API; MikroTik with two static lines.
    Automated
    Who is online, who is working on what, cleanup of stale sessions.
  3. 03 · Implementation

    Hosts, remote desktops in the browser, accounts and access per person, online monitoring, daily and monthly statistics.

  4. 04 · Result

    Around twenty people working remotely on office machines with nothing open to the internet.

Technical detail
Architecture in detail
Virtualized hosts (ESXi, vCenter), two Guacamole servers (one per line), a pool of connections per employee in a database with row locking, an internal desktop app for staff and managers.
Layers
Infrastructure Network Software Security
Stack
ESXi vCenter Guacamole MikroTik C#

Have a system like this to build?

Tell us about the operation behind it.

Let's talk

Start with the problem.

Tell us how your business works, what you want to improve, and what is getting in the way. You don’t need to know what technology you need; we’ll reply with what we think it needs.

For example: what you use today, what you want to improve, connect or automate, and whether you think you need a new system. No technical terms needed.

Your message is used only to reply to you. Privacy Policy