Now taking first installs

Private AI, set up for the work you already do.

We install open-source AI on your own computers, shape it around your recurring work with the TresPies Harness, and stay on call to keep it useful. Built for nonprofits and small offices that handle records they can't send to someone else's servers.

runs where
On your machines. In private mode, nothing typed into it leaves the computer.
set up for
Your drafts, records, and bilingual notices, as routines your staff can run in English or Spanish.
supported by
A person. A monthly working session, a request line, and an upgrade every quarter.
Integration process

From first conversation to daily use in about a month

Every install follows the same six steps. The first five are setup. The sixth is the retainer, and it's where most of the value comes from, because the useful routines come from watching how your staff actually use the tools.

Week 1

Listen

Short intake sessions with the teams who'll use it. We list the work that repeats every week or month, and we map your data: what's routine, what's sensitive, and what must never leave the building.

Task listData mapPoint person named
Weeks 1 to 2

Check

We look at the computers you have. If none of them can run a capable model at a usable speed, we write a spec for one shared workstation that you buy directly, at cost, from any vendor you choose. We pick the open model to fit the machine.

Hardware checkWorkstation spec, if neededModel choice
Weeks 2 to 3

Install

OpenCode, a local model runtime, and the TresPies Harness go onto your machines. Private mode and the guardrails are on before anyone types a word. A commercial AI service can be added later for non-sensitive work, but only if you turn it on.

Private mode onGuardrails onSession log on
Weeks 3 to 4

Build

Three starter routines for your most common tasks, tested on real examples you pick from non-sensitive files. Each one comes with a two-page quick guide.

3 routinesQuick guides
Week 4

Train

Two hands-on sessions, in English or Spanish as your staff prefer. People work through their own tasks, not a demo.

2 sessionsEN / ES
Every quarter after

Run

One working session a month with whoever is using it. Email questions answered within two business days. New routines each quarter, chosen by you. Every quarter we update and test the software and the model, and you get a one-page record of what changed and what's next.

Monthly sessionRequest lineNew routinesQuarter record
The TresPies Harness

Three layers, and you own two of them

The engine is free, open-source software. The model runs on your hardware. The Harness is our layer on top: the setup that turns a general AI agent into something an office can trust with its daily work.

We supply and maintain
TresPies Harness

Named assistants, ready-made routines, guardrails, a private mode, house rules in your voice, and a session log. Licensed to you while the retainer runs. If you stop, you keep the version you have.

Open source · MIT
OpenCode

A widely used open-source AI agent that reads, organizes, and writes files in a working folder, and works with models that run entirely on a local machine. Yours to keep using with or without us. opencode.ai

You own
Machines and models

Your computers, running an open-weight model through a local runtime such as Ollama. No per-seat AI subscription is required.

assistants/

Named assistants

A drafter, a records clerk, a translation drafter, and a reviewer. Each has one job, its own instructions, and its own permissions, so the right tool picks up the right task.

routines/

Routines

Written playbooks for your recurring tasks: a monthly report section, a resident notice in two languages, a spreadsheet cleanup. Staff run them by name instead of writing prompts from scratch.

guardrails

Read-only until approved

Assistants can read the working folder. Every change to a file is shown and waits for a person to approve it. Shell commands are off.

private mode

Nothing leaves the machine

Only the local model is available, and web access is denied. This is the default, and the only mode allowed near sensitive records.

house rules

Your voice, your terms

A plain-language rules file with your organization's style, glossary, preferred Spanish terms, and a list of things the assistants must never do.

session log

A record of what happened

What was asked, what was produced, and what was approved, kept on your machine. It's how the monthly session finds what to fix next.

// opencode.json · Harness private-mode profile (excerpt)
{
  "$schema": "https://opencode.ai/config.json",
  "provider": {
    "ollama": {
      "npm": "@ai-sdk/openai-compatible",
      "name": "Office model (local)",
      "options": { "baseURL": "http://localhost:11434/v1" },
      "models": { "gemma3:27b": { "name": "Office model" } }
    }
  },
  "permission": {
    "*": "ask",
    "read": "allow",
    "edit": "ask",
    "bash": "deny",
    "webfetch": "deny",
    "websearch": "deny",
    "external_directory": "deny"
  },
  "agent": {
    "records-clerk": {
      "description": "Cleans spreadsheets; shows every change first",
      "mode": "subagent",
      "permission": { "edit": "ask" }
    }
  }
}

Nothing hidden in the setup

The guardrails are ordinary OpenCode settings, so your IT person (or anyone you hire later) can read exactly what the assistants are allowed to do.

  • Local model only. The only provider points at the runtime on the same machine.
  • Reads allowed, edits ask. Every file change is shown and waits for approval.
  • No shell, no web, no wandering. Shell commands, web fetches, web searches, and folders outside the working folder are all denied.
  • Per-assistant limits. Each assistant can be held to tighter rules than the defaults.
Services

A core retainer, plus add-ons when you need them

Every engagement starts with the same setup and quarterly retainer. Add-ons are scoped in a one-paragraph note (what, by when, how it's billed) before any work starts.

Core

Setup + quarterly retainer

  • Setup, one time. Intake, hardware check, install on up to three computers, private mode and guardrails, three starter routines, two training sessions.
  • Monthly working session. One hour with your point person and anyone using it.
  • Request line. Questions and fixes by email, answered within two business days.
  • New routines. Up to two a quarter, chosen by you.
  • Quarterly upgrade. Software and model updated and tested, with a one-page quarter record.
Add-ons

When the core isn't enough

  • AI use policy. A plain-language staff policy and a one-page guide, in English and Spanish.
  • Ask-your-files search. Answers drawn from a shared folder, each one citing its source file, running locally.
  • Grant and report kit. Routines built from your funders' templates and your past reports.
  • Bilingual review workflow. Translation drafts, a shared glossary, and a checklist for your fluent reviewer.
  • Records cleanup sprint. A fixed two-week project to clean and reconcile one set of records.
  • Staff workshop. A 90-minute hands-on session for a team, in English or Spanish.
  • Workstation sourcing. We spec, order with you, and set up the machine. Hardware at cost.
  • More teams or sites. Additional computers and a second working session each month.
  • Priority support. Next-business-day replies and an extra monthly session.

Pricing is set in the first conversation, by size and scope, with nonprofit rates.

Honest limits

What local AI is good for, and what it isn't

Open models running on one office machine are slower and less capable than the largest commercial services. That's the trade for keeping your records in the building. We set expectations to match.

Good at

  • First drafts that a person finishes
  • Pulling answers out of your own files, with the source named
  • Cleaning, reformatting, and checking lists and spreadsheets
  • Spanish and English drafts for a fluent reviewer to correct
  • Turning meeting notes into summaries and action lists

Not for

  • Legal, medical, or financial advice
  • Decisions about the people you serve
  • Sending anything on your behalf
  • Translations that go out without a fluent person's review
  • Work that needs the newest, largest models (we'll tell you when it does)
Next step

Thirty minutes, three tasks, one machine

Bring the three tasks that eat the most of your team's week and a sense of which computers you have. We'll tell you plainly whether local AI will help, and what the first month would look like.