Request a pilot
Skilak KeepRequest a pilot

Guide · resources

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.

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.

See the reference architecture on the deployment and security page.

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.

  1. Office employee — Managed device → customer LAN → private DNS/HTTPS → Skilak Keep interface · Customer IT governs the device, network segment, identity, and user approval.
  2. Remote employee — Managed device → MFA → customer VPN or ZTNA → private DNS/HTTPS → Skilak Keep interface · Customer IT governs remote-access posture. The interface remains private.
  3. System administrator — Privileged workstation or admin segment → management interface → approved services · Administrative access is separated, limited, and documented.
  4. 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.

Remote users reach the system from a customer-managed endpoint over the customer’s own VPN or ZTNA path. The system itself never becomes internet-facing.

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.

  1. Proposed room, rack or floor placement, available rack units, power, cooling, and physical access controls
  2. User VLANs, server VLAN, management network, DNS, certificates, proxy, firewall, and time services
  3. Local accounts or enterprise identity, group ownership, MFA, admin separation, and offboarding
  4. Remote-access method, managed-device requirements, route availability, and user support ownership
  5. Approved outbound destinations for identity, updates, monitoring, or support—or a fully disconnected operating decision
  6. Backup target, recovery ownership, logging destination, retention rules, and maintenance windows

Your working boundary

What Skilak touches.

Skilak stages the system, 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 lifecycle

A single rack in a controlled customer space—dedicated compute, blanking panels, UPS, and dressed cabling. Placement, power, and physical custody stay with the customer’s IT organization.

Ready to scope it?

Start with one workload.

Tell us who uses it, what it can read, and what must stay inside. We will map the build.

Request a pilot