The code is open-source and self-hostable on your own. These engagement models bring in a fractional CTO to implement it, tailor it to your workflow and compliance posture, and keep it running.
Engagement models
From a low-friction pilot to a full fractional-CTO retainer. Pick the model that matches how much involvement you want.
Implementation Path
Standard implementations follow this arc. Pilot is compressed (single user); Embedded extends post-week-6 indefinitely.
Interview the team. Catalog mail volume + types. Define category taxonomy. Identify integration points (Slack, CRM, ticketing).
Provision the host (cloud or on-prem). Install dependencies. Configure TLS. Set up monitoring integration.
Register OAuth apps with Google / Microsoft. Configure IMAP credentials. Set up Pub/Sub or Graph push subscriptions.
Initial classification on a backlog of historical mail. Operator-review of category assignments. Rule additions where the classifier needs reinforcement.
Sent-mail mining for writing-style profile. Initial drafted replies for operator-review. Captured-edit feedback loop established.
Push integration enabled. Real-time triage active. Daily / weekly digest schedule established. 30-day post-launch hypercare begins.
Monthly tuning calls. Quarterly category review. Security patch + version updates. For Embedded engagements, this continues as long as the retainer is active.
What's Included in Every Tier
Whether or not the customer is HIPAA-regulated. Demonstrates the privacy posture and surfaces gaps before deployment.
Two-bundle encrypted backup pattern, off-host storage guidance, restore-procedure rehearsal.
Built-in ACME (Let's Encrypt) issuance and automatic renewal over DNS-01 (RFC-2136) or HTTP-01 (standalone or webroot); or bring your own operator-supplied certificate; a self-signed cert is generated on first start so the app is HTTPS by default. Renewed certs hot-reload without a restart.
Nagios, Datadog, Prometheus, or your team's preferred system. Health endpoint exposure + alerting configuration.
Runbook, recovery procedures, escalation contacts. Tailored to your team's operational shape.
Bug response, configuration tweaks, and tuning during the most disruption-prone window after cutover.
Self-service vs a guided engagement
It's real and inspectable. Anyone with engineering chops can deploy it from the public repository at github.com/Unlimited-Data-Works-LLC/Email-Triage using the signed container image at ghcr.io/unlimited-data-works-llc/email-triage (verification recipe in the repo's docs/install.md). A guided engagement is for organizations where:
If your team has Linux/Podman fluency and an Ollama host already, self-hosting is straightforward. If you'd rather get to value without owning the implementation, that's what a guided engagement is for.
Beyond Email
For broader technology leadership engagements that extend beyond email automation — sovereign AI strategy, compliance program design, infrastructure modernization, OT/IT convergence — explore the matching consulting vertical.