Office employee
Managed device → customer LAN → private DNS/HTTPS → SkilakSpool interface
Customer IT governs the device, network segment, identity, and user approval.
Field guide · network and access
Where the box lives—and every path around it.
This is the plain-language view you can draw with a customer before the detailed network diagram exists. It defines the physical site, the user paths, the optional outbound paths, and who owns each decision.
Reference pattern
Private service, customer-governed access.
The public internet is not the front door. Approved office and remote users enter through customer-controlled network and identity services.
Authorized users
OfficePrivate LAN
RemoteManaged device
AdminPrivileged path
Private HTTPS · Remote access: MFA + VPN / ZTNA
Customer-controlled site
Approved network boundarySkilakSpoolLocked server room / secure IT space
01Private interface
02Model runtime
03Retrieval + data
Optional, approved egress only
IdentityUpdatesSupport
Access paths
Who can connect—and how.
Names, network segments, controls, and ownership are confirmed in the final design. Skilak does not assume authority over the customer’s identity or remote-access policy.
Remote employee
Managed device → MFA → customer VPN or ZTNA → private DNS/HTTPS → SkilakSpool interface
Customer IT governs remote-access posture. The interface remains private.
System administrator
Privileged workstation or admin segment → management interface → approved services
Administrative access is separated, limited, and documented.
Skilak support
No standing access by default; approved session or customer-operated procedure when support is required
The support path and authorization are agreed in the operating model.
Site discovery
What Skilak needs from the customer.
You do need to account for this setup—but you do not need to own every part of it. The playbook is to identify the customer owner, gather constraints, propose the design, and get approval before making changes.
- 01
Proposed room, rack or floor placement, available rack units, power, cooling, and physical access controls
- 02
User VLANs, server VLAN, management network, DNS, certificates, proxy, firewall, and time services
- 03
Local accounts or enterprise identity, group ownership, MFA, admin separation, and offboarding
- 04
Remote-access method, managed-device requirements, route availability, and user support ownership
- 05
Approved outbound destinations for identity, updates, monitoring, or support—or a fully disconnected operating decision
- 06
Backup target, recovery ownership, logging destination, retention rules, and maintenance windows
Your working boundary
What Skilak touches.
Skilak stages the appliance, installs and configures its software, connects it to customer-approved services, applies the agreed host and application configuration, validates the paths, and documents the result. Customer IT owns switches, firewalls, identity, endpoint policy, WAN/VPN/ZTNA, facilities, and authorization unless the statement of work assigns a specific task otherwise.
See the full delivery lifecycleReady when you are
Draw your first customer’s boundary.
Bring the site, users, remote-work model, and IT contacts. We can turn them into a solution brief and responsibility map before hardware is quoted.