The product is more than the chassis

An open software baseline your technical owner can inspect.

The configured appliance uses mainstream components, pinned and documented for the agreed workload. Open-source-first means inspectable and portable; it does not mean maintenance-free.

Talk through your requirements Review claims and sources

A private deployment starts with the permitted data path, access policy and logging boundary.

Operational ownership

The handover should make responsibility easier to see.

01 / Owner: Name who controls updates, access, recovery and incidents.
02 / Record: Make versions, tests and handover evidence visible.
03 / Exit: Keep portability and supplier boundaries written down.

GPU server remote management dashboard with system status, access logs and sensor monitoring panels — Supplier screenshot of the platform management interface. The final management features and access policy depend on the ordered system. OEM supplier reference image.

A deliberately small supported stack

Ubuntu LTS, a validated NVIDIA driver/CUDA pairing, Docker Engine and NVIDIA Container Toolkit form the base. Ollama, vLLM or llama.cpp is selected according to ease, throughput and model needs.

Open WebUI or a reviewed equivalent provides browser access. A vector database is added only when retrieval is in scope.

Pinned versions
Software bill of materials
Model source and licence record
Update and rollback note

Request Reason, owner and affected service.
Test Focused acceptance and rollback plan.
Approve Named person accepts the change.
Record Version, date and result recorded.

Silent model, runtime or access changes make later assurance harder. Apply to: A deliberately small supported stack

Diagram showing approved documents moving through a searchable index to an answer with a source citation — A retrieval workflow should connect each useful answer to approved source material and defined refusal behaviour. GPU Servers technical illustration.

Diagram of an evidence pack containing an asset schedule, burn-in record, health readings, workload test and admin guide — A credible handover records the supplied assets, checks, operating evidence, instructions and unresolved items. GPU Servers technical illustration.

One route to production, not a showcase of logos

Installing every fashionable framework increases the attack surface and support burden. The order identifies the primary model server, interface, authentication route and monitoring profile.

Alternative runtimes can be tested as separate profiles without changing the accepted baseline.

Equipment Hardware fault and warranty route.
System Build record, settings and secrets.
Data Backup, retention and restore authority.
Service Fallback, incident and return to use.

A backup claim is incomplete until restoration ownership and a test route are clear. Apply to: One route to production, not a showcase of logos

Models have licences and operating characteristics

Open weights do not always mean unrestricted commercial use. Model source, version, licence and intended use are recorded before handover.

Updates can change quality, memory and speed. A model change should trigger a focused evaluation rather than happen silently.

Export Data, settings and useful records.

Rebuild Documented components and versions.

Replace Alternative runtime or supplier route.

Close Deletion, access removal and asset handling.

Portability still needs testing. Open components do not remove migration work. Apply to: Models have licences and operating characteristics

The customer owns the environment

Administrative credentials and recovery materials are handed to the customer. Opace does not propose a hardware-bound proprietary licence for the baseline.

Optional support can advise on reviewed updates; it does not create an unbounded obligation to maintain every community component.

Questions answered

Straight answers to common questions

Do you install Ollama?

Ollama is one possible supported profile. vLLM or llama.cpp may be a better fit depending on model, throughput and operating needs.

Is Open WebUI included?

It is the standard browser interface or can be replaced by an agreed equivalent in the order.

Are the models included?

Only agreed models whose source, licence and fit have been reviewed. Commercial model/API fees are separate.

Continue the decision

Useful next steps

Next decision

Turn this guidance into a testable requirement.

The brief asks about workload and operating conditions - not just budget.

Tell us what you need Compare server systems