How it works
Fit it to the office.
Prove it with real work.
We start with the jobs you want done, write down the network and privacy choices, configure the machine, then test the complete setup before handover.
We are ready to start a closed pilot of the platform with businesses. On-site installs and demonstrations are coming soon; register your interest now.
Register interest for a pilot See machine optionsScope · configuration record · install · acceptance checks · handover
First, decide what belongs on it.
A good install starts with a short list of useful jobs and a clear list of what may connect outside the appliance.
1. Work through the jobs
We look at the documents, repeated typing, research, meetings and small calculations that take time now. Use approved sample material or material you are comfortable testing; do not send confidential client files through the public website form.
We will also say when a local appliance is more machinery than the job needs.
2. Write down the boundary
We record users, private and shared work, folders, retention, backup, the office network and any systems that need to connect. Web research, updates, an external integration, remote support and off-site fine-tuning are named exceptions to the base offline setup.
The quote and configuration record should show the choices before the build starts.
Set up the system around the office.
Accounts and access
We set up local accounts, roles, private and shared areas, network access and the local HTTPS address. Staff normally open the Harness in a browser. A desktop app is not required, though devices may need network and certificate setup.
Models and workflows
The chosen models, staff presets, skills and allowed folders are matched to the machine. Your acceptance list names the capabilities your office actually signed off, so there is no argument later about what was included.
Repeatable deployment
The Harness services are packaged with Docker so installation and recovery can follow the same steps. Models stay on the host machine. The exact operating system and hardware are recorded for the job.
Install
The machine arrives set up.
The setup itself is deliberately simple, because nearly all of the work happens before we get there. Your accounts, models, industry packs and your own templates are configured on the machine in advance, so the visit itself is short: plug it in, put it on your network, and check every computer and phone in the office can reach it.
Then we walk your team through the jobs they asked for and hand over the administrator details. Most installs are done inside a morning.
On-site work is available in the listed service areas. A remote setup needs somebody at the machine for power, sign-in and the network step; everything else we can do from here.
No standing remote connection is needed for ordinary use. Any support session is a separate connection you request.
Check the whole path, not the welcome screen.
A feature is only useful when it works on the supplied machine, through the supplied browser, with the permissions and network rules agreed for that office.
- Chat
- Sign in, choose a preset, send a prompt and receive a complete response.
- Documents
- Upload an agreed test file, index it, ask a question and open the cited source.
- Accounts
- Check roles and confirm one user cannot fetch another user's private work.
- Network
- Confirm HTTPS access, the default block and every approved allowlist exception.
- Models
- Load, answer and release as expected, with the model name and source recorded.
- Backup
- If included in the configuration, run a recovery check against the installed target rather than assuming it works.
- Optional workflows
- Research, mail, meetings, exports and integrations are switched on where they suit the job and left off where they do not.
Handover
Show people the jobs they will use.
Training stays close to the agreed work: where to start a chat, how to add a file, how to check a citation, what belongs in a private area and who can change network access.
Generated text, calculations and citations can be wrong. Material output still needs source checking and the professional review the work normally requires.
The handover includes the administrator details, the configuration record, the named exceptions and the chosen support route.
The Harness keeps changing
Improvements are included in the support plan rather than billed as a new licence. Applying a Harness update needs a temporary connection for the update and checks, then that connection is closed again.
Support stays scoped
Remote support happens through a session you request and start. On-site work, health checks, model changes and recovery work depend on the support terms in the quote. We do not turn a support option into a blanket uptime or recovery promise.