Your AI. Your rack.Your rules.
An on-premises private AI system with local models, governed document search, and an operating handoff your IT team can own.
Own the operating boundary
Useful AI, under your control.
Local models, governed search, and a complete operating handoff, inside the environment you own.
Control
AI on infrastructure you own
Models, retrieval indexes, prompts, and generated answers are designed to remain inside the customer-controlled environment.
Access
Built for the way your team works
Office users connect over private HTTPS. Approved remote users connect through the customer's VPN or zero-trust access path with MFA.
Operations
Delivered as a working system
Skilak stages, tests, transports, installs, and validates the system with your IT and security teams, not as a box left at the loading dock.
Where it sits · who touches it
One system. No public front door.
Local users connect over your network. Remote users come through your VPN or zero-trust path.
Authorized users
Customer-controlled site
Approved network boundaryOptional, approved egress only
Right-sized systems
Start small. Scale after proof.
Choose a planning tier, then validate the final hardware against the work.
5–25 named users
Solo
A compact private-AI starting point for an executive team, proposal shop, engineering cell, or controlled pilot.
- Platform
- Tower / compact rack
- Memory
- 48–128 GB GPU / 96–192 GB unified
- Concurrency
- 1–5 active
- Private chat and document Q&A
- Optional retrieval with source citations
- Local user administration
- Acceptance testing and operator handoff
20–150 named users
Team
A rack-mounted deployment for shared departmental use, stronger identity integration, and sustained internal workloads.
- Platform
- Rack / paired systems
- Memory
- 96–384 GB GPU / 192–512 GB unified
- Concurrency
- 6–24 active
- Microsoft Entra ID or compatible SSO
- Governed retrieval and citations
- Role-based access and audit logging
- Monitoring, backup, and restore runbooks
150–500+ named users
Enterprise
A site-specific architecture for multiple workloads, larger concurrency targets, or specialized model requirements.
- Platform
- Multi-server / segmented
- Memory
- 384 GB–1.5 TB+
- Concurrency
- 25–100+ active
- Site survey and capacity planning
- Network and identity architecture
- High-availability options where justified
- Phased rollout and operational enablement
Prove the system
Acceptance is evidence, not a promise.
Each engagement defines what must work and what evidence will demonstrate it before handoff.
See the validation modelDisconnected rehearsal
The approved AI workflow remains available without a public internet path.
Grounded retrieval
Answers based on approved documents return traceable source citations.
Recovery
The service and approved knowledge base can be restored from the defined backup set.
Model quality
The selected model produces coherent, useful output for the agreed priority workflows.
Continuity
What you keep if we are not here.
The honest answer to a young vendor's biggest objection is not a promise about our longevity. It is that the system does not depend on it.
The software is open source
Nothing in the stack is ours to withdraw, and none of it phones a license server. A system that stops hearing from us keeps serving.
There is no vendor backdoor
No standing remote access, no permanent tunnel, and no unmanaged support account. Support runs through a path you approve and can revoke. Removing us is a firewall rule, not a migration.
The runbooks are yours
Install, backup and restore, egress verification, and network and access design are written procedures handed over at acceptance, not knowledge held in one person's head.
The hardware is bought, not leased
You own the machine outright. There is no per-seat AI fee to lapse and no subscription that bricks the box.
Pilot
Start with one workload.
Tell us who uses it, what it can read, and what must stay inside. We will map the build.