Case study
Meridian Federal Credit Union
18 days from kickoff to production traffic on Google Workspace
A 1,400-employee credit union replaced three intake handoffs and a stack of internal docs with a sovereign MillenniumOS agent running inside their Google Workspace boundary. The full deployment — residency, audit, identity, and model rollout — shipped inside one quarterly change window. Watch the agent run on production-shaped data →, or review install pricing for an engagement shape like this.
Deployment timeline
18 days
kickoff to production traffic on Google Workspace
Users onboarded
1,400
members of staff across intake, KYC, and member service
Data residency region
us-central1
inside the credit union's existing Google Cloud project
The challenge
Meridian was losing two business days per week between intake, KYC review, and member-service handoffs. Internal docs were living in three different Drive folders, the regulated LLM endpoint their risk team had approved could not be used because the runtime leaked prompts to a managed endpoint, and a regulator inquiry on residency had frozen a planned workflow rollout. The ask was narrow: stand up an agent that worked on production-shaped member data, kept every prompt inside the tenant boundary, and produced an audit trail their examiner could read without a translator.
The solution
MillenniumOS installed the sovereign runtime into the credit union's existing Google Cloud project — model weights, inference servers, and the audit log all landed inside the tenant VPC the team already governed. The first workflow shipped against member-intake triage in Gmail, with every prompt-and-completion receipt written to the existing Cloud log sink. Browser-isolated actions against the internal admin portal were wired through scoped service identities, so the agent never authenticated as a human user from the normal fleet. The same boundary then graduated onto KYC summarisation and member-service reply drafting in the second sprint — no new vendor, no new data path. See the sovereign runtime questions this answers →
The deployment
Install ran against an existing Google Workspace tenant — Drive, Gmail, Calendar, and the internal admin portal — so the deployment timeline was measured in working days, not months. Residency, IAM, and the audit sink came online in the first sprint; the first production workflow shipped the following week; the second and third workflows were added behind the same change window. Audit receipts were wired in alongside each workflow rather than retrofitted, which is what made the regulator inquiry on residency close out in a single review session.
The results
Three high-friction workflows now run end-to-end against the sovereign boundary, with the audit trail the examiner asked for already on disk. Member-intake triage time dropped from hours to under twenty minutes, KYC summarisation that used to take an analyst two days now finishes inside one agent run, and the reply-drafting workflow gives the member-service team a vetted first pass instead of a blank inbox. None of it crosses the tenant boundary, none of it depends on a third-party endpoint, and the same boundary is now the default surface the credit union graduates new workflows onto.
“We had three internal teams blocked on the same residency question. MillenniumOS installed inside our existing boundary in under three weeks — the audit receipts the examiner asked for were already on disk, and the agent is now the default surface we graduate new workflows onto.”