Qompute AI
Services · Private-AI deployment and integration

We plan it, build it with you, and hand it over so your people can run it.

Private AI on hardware you control, with identity, policy, and records someone can answer for. Assessment of what you already run, a written plan, implementation with your engineers, and operator and builder enablement. For a local stack you already have, or for qore.

Discuss a projectEngagements
Led by the engineers who build qoreScoped in writing before work startsService fees separate from any product license
Who does the work

Two engineers, not a bench.

Engagements are led by Derek Hinch and Joey Victorino, the two people who build and operate qore. There is no separate services team, so we take a small number of engagements at a time and say no when we are full.

Joey Victorino
Deployment infrastructure, security architecture, and incident response. More than a decade on nation-state intrusions, ransomware, and advanced persistent threats; CISSP and eleven GIAC certifications in forensics, malware analysis, and detection engineering. Builds and runs Qompute AI's own hosts.
Derek Hinch
qore's architect and principal author: inference runtime, agent engine, and cryptographic subsystems. Nearly three decades across U.S. Air Force electronic-warfare research and test, hyperscale cloud security, and Fortune 500 enterprise defense.
Formats
  • Remote, on your hardware over your screen-share
  • On site in the United States for isolated or air-gapped environments
  • Written deliverables in plain language, suitable for your compliance file
Fees and terms
Every engagement is scoped in writing after a discovery call, with fixed deliverables and a fixed price or a capped time-and-materials budget. Service fees cover the work. Where qore is part of the engagement, preview access is granted under the preview terms for the engagement period, separately from the service fee, and confers no license beyond it. The deployment assessment needs no qore license and covers a local stack you already run.

Backgrounds in full on the team page.

Engagements

Six engagements, each with what it includes and what you receive.

The deployment assessment covers a local inference stack you already run as well as qore, and needs no qore license. The other five assume a qore deployment is the agreed environment.

One to two weeks, remote

Deployment assessment

Before anything is installed: which deployment mode fits, what hardware it needs, and what qore will not do for you yet.

Led by Joey Victorino.

Discuss this engagement

Includes
  • Workload and boundary review: which documents, models, and tools, and where the data may and may not go
  • Review of a local inference stack you already run, if any, and what would change or stay
  • Hardware sizing from your models and context needs, using our measured data point and your own test runs
  • Choice of desktop, server, or container mode, with the reverse-proxy and TLS arrangement
  • Identity, roles, second-factor, and tool-policy design on paper before it is configured
  • A written list of the qore limitations that matter for your use, taken from the same registry this site is built from
You receive
A written deployment plan your security and platform teams can review. No qore license is needed to book the assessment.
Two to five days, remote or on site

Guided installation and hardening

We install qore with you, configure it to the plan, and leave a configuration record behind.

Led by Joey Victorino.

Discuss this engagement

Includes
  • Apple Silicon desktop build, or Linux server and container mode with an operator-supplied inference build for your architecture
  • Reverse proxy and operator-terminated TLS in front of the server modes
  • Accounts, roles, mandatory second factor, and the policy-decision audit trail switched from audit mode to enforcement where you want it
  • Model servers configured per model: boot policy, context size, GPU layers, and memory-pressure behavior
  • Encrypted stores, license token installation, offline grace check, and a signed settings-bundle export as the baseline
  • Optional: OIDC configuration, which is gated and untested in the current build, stated as such
You receive
A running installation and a configuration record listing every setting and why.
Half day to one day, remote or on site

Operator and governance workshop

For administrators, security staff, and the people who will approve agents and tools.

Led by Derek Hinch and Joey Victorino.

Discuss this engagement

Includes
  • Agent definitions, declared tools, allow-lists and deny-lists, and what an agent can and cannot reach
  • Reading the operational log, the forensic audit log, and the policy-decision trail; what is chained and sealed, what is encrypted, and what is neither
  • Signed export bundles and the datastore portability envelope
  • Where the current gaps are: no per-call approval gate, no enforced tool signature verification, no in-product egress policy, and how to compensate at the network and process layer until they ship
You receive
An operator runbook written for your installation.
One to two days, hands-on

Builder enablement

For engineers who will build agents and integrations on the installed system.

Led by Derek Hinch.

Discuss this engagement

Includes
  • The local API, agent workflows with declared tools, and MCP tools over HTTP and SSE
  • Retrieval over your documents, multimodal inputs, and phase-aware routing between model tiers
  • Prompt and workflow design for smaller local models, with the trade-offs stated
  • Evaluation practice: qore ships no evaluation harness today, so we help you stand one up beside it and record results you can compare over time
You receive
Working examples on your installation and a written set of patterns for your team.
Two to four weeks

Pilot leadership

A pilot with written success criteria before it starts and a joint review of the audit record when it ends.

Led by Joey Victorino.

Discuss this engagement

Includes
  • Pilot criteria agreed in writing: users, documents, tools, and what would count as success or failure
  • Weekly working sessions with your operators and builders
  • Joint review of the audit record against your evidence-handling or compliance standard
  • A closing report that says what worked, what did not, and what qore would need to change
You receive
A closing report you can use for a go or no-go decision. We publish nothing about it without your written consent.
One week, remote

Evidence-handling and incident-readiness review

How qore's records fit your incident-response and evidence-handling practice, reviewed by someone who has run that practice.

Led by Joey Victorino.

Discuss this engagement

Includes
  • What an investigator gets from each qore log and record, and what they do not
  • Where qore's records sit in your existing playbooks, retention rules, and chain-of-custody procedure
  • Export and preservation procedure for the forensic log and run records
  • Gaps stated plainly: the forensic log is encrypted but not hash-chained or signed today
You receive
A written procedure and a gap list for your incident-response lead.
Not offered yet

Ongoing operations, managed updates, and support contracts Not offered yet

Preview testers get support by email today. Contracted response times, managed updates, and operations retainers are not sold until the product has a public release cadence.

Not sold yet. Preview testers get email support from the founders; contracted response times and managed operations are not offered until qore has a public release cadence.

How an engagement runs

Four steps, nothing implied.

  1. Discovery callForty-five minutes. Your boundary, your workload, your timeline. We say whether qore fits and which offerings apply.
  2. Written scopeDeliverables, dates, who from each side, and a price. Nothing starts until it is signed.
  3. The workOn your hardware, with your people in the room or on the call. Every configuration decision is recorded.
  4. HandoverWritten deliverables, a runbook, and a named contact for preview support afterwards.
Not offered

What we will not sell you.

  • Windows or Linux desktop installations; those builds are Planned
  • Model training or fine-tuning; governed adaptation is Planned in the product
  • Compliance certification or attestation; we map controls with your team and say what is missing
  • Any promise about an assessment, audit, or accreditation outcome
  • Round-the-clock support or contracted response times

qore's own limitations are listed on the product page; an engagement does not remove them, and no engagement here requires you to adopt qore.

Discuss a project

Tell us your boundary and your goal.

Joey Victorino replies within two business days with whether we fit, which engagement applies, and a proposed call time.

Evaluating qore without help? Request access instead.

One or two sentences is enough. No credentials, secrets, prompts, or customer data here; detail moves under a signed agreement.
More detail (optional)
Inquiries marked as an active incident are read first and answered the same business day, US Pacific.

Derek Hinch or Joey Victorino reads it and replies personally, usually within two business days, with whether we fit and a proposed call time. Nothing is scheduled or committed by sending this form. Privacy notice.