RTX 4090-class GPU
24 GB-class accelerator target for capable local inference and workflow demonstrations.
MK-II local AI server
MK-II is the proposed private AI productivity server: a single workstation-class system designed to run useful local models, approved business data, and tailored workflows across a private LAN.
Email and report drafting, data analysis, private file and database access, and tailored workflows—with people reviewing consequential actions.
01 · Hardware target
The MK-II target prioritizes a practical single-GPU system that can demonstrate credible local workflows without implying that every future installation needs the same configuration.
24 GB-class accelerator target for capable local inference and workflow demonstrations.
Headroom for local services, document processing, databases, and CPU-assisted inference.
Operating system, containers, applications, active models, and working data.
Separate capacity for approved files, databases, vector indexes, backups, and expansion.
Private LAN access for authorized devices, with 10 GbE as a preferred expansion path.
Protected shutdown and short-duration continuity for a workstation-class system.
Workstation-class airflow, a high-quality power supply sized near 1600 W, a dedicated 120 V circuit where appropriate, and an expected peak system envelope of roughly 800–1200 W would be evaluated during assembly.
02 · Proposed platform
The software choices are an initial architecture, not permanent dependencies. The goal is a maintainable private platform with clear boundaries and recoverable data.
Ubuntu Server LTS and containerized services managed with Docker Compose.
Ollama as the initial local model runtime, with room to evaluate other serving engines.
Open WebUI for authorized browser access from devices on the private network.
n8n for carefully scoped automations, approvals, and repeatable business processes.
PostgreSQL and Qdrant for structured records, document retrieval, and cited local search.
Caddy for local service routing and Restic for encrypted, testable backup routines.
03 · Prototype demonstrations
A successful prototype is not simply a machine that can produce text. It should complete useful private workflows, show its sources, preserve human review, and reveal the real operational cost.
04 · Funding objective
The prototype budget would be tied to a visible sequence of assembly, platform setup, workflow validation, and documented results. The target is proof, not mass production.
Purchase and integrate the compute, memory, storage, networking, cooling, power supply, and UPS within the target envelope.
Harden the operating system, deploy the local service stack, define permissions, and confirm backup and recovery behavior.
Demonstrate an approved document or data workflow from ingestion through cited output and human review.
Record response speed, memory use, power demand, setup time, limitations, and the requirements for a real pilot installation.
Specifications, costs, availability, and software choices remain subject to prototype validation. This page is not a product listing, preorder, investment offer, or performance guarantee.
Help move MK-II forward
Potential pilot users and in-kind hardware partners can contact the project without making a financial commitment.
Contact the project