AI development company for Winnipeg agritech, insurance, financial services, and Manitoba healthcare.

We do not operate a Winnipeg office. Aiinfox runs from our Mohali, India HQ and a Frisco, TX office — Frisco shares Winnipeg's time zone exactly (Central Time year-round). For on-site engagements at Portage and Main, the Exchange District, the Cargill or Richardson HQ, the Great-West Life HQ, Shared Health Manitoba sites, or the University of Manitoba campus (kickoff, milestone reviews, security walk-throughs), we travel to Winnipeg on a scheduled cadence rather than maintaining a sub-scale local presence. The senior engineer on your kickoff is the senior engineer through launch.

One of the strongest TZ overlaps in our portfolio for any Canadian market — and unusually for a foreign vendor, we genuinely share your workday. Winnipeg runs Central Time year-round (UTC-6 in winter, UTC-5 in summer); our Frisco, TX office runs Central Time as well. A standard 9am-to-5pm CT shift in Frisco lines up exactly with the Winnipeg working day. Our Mohali team adds an early-IST start that picks up Winnipeg afternoons (our 7:30pm IST is your 9am CT) for a clean morning overlap window before Frisco comes online. Twice-weekly demos run in Winnipeg business hours; written async updates from Mohali land before your standup.

Yes. Manitoba PHIA (the Personal Health Information Act, administered by the Manitoba Ombudsman) imposes obligations on trustees of personal health information that go beyond PIPEDA's federal commercial baseline — duties of trustees, consent rules, the right to access and correct, breach reporting, and specific provisions for foreign-based service providers handling Manitoba PHI. For Shared Health Manitoba-adjacent, Health Sciences Centre-adjacent, and University of Manitoba Faculty of Medicine-adjacent healthtech, BAAs or equivalent DPAs are signed before any PHI is shared; deployments default to AWS ca-central-1 (Montreal) inside customer-controlled Canadian clouds so personal health information never leaves Canada; every model and tool call is audit-logged with input, output, prompt version, and operator identity — exportable for the Manitoba Ombudsman or the contracting trustee's privacy officer.

Yes. Manitoba FIPPA (the Freedom of Information and Protection of Privacy Act) governs public-body data handling and imposes obligations on service providers processing public-body personal information. For Government of Manitoba ministry engagements and Manitoba Crown-corporation engagements (Manitoba Public Insurance, Manitoba Hydro, Manitoba Liquor and Lotteries), we structure data flows so personal information remains in Canada through every step of the pipeline — including inference — which typically means AWS ca-central-1 or self-hosted Llama 3 on vLLM inside the customer's Canadian VPC with zero data egress. Audit logs are exportable for the Manitoba Ombudsman.

Yes. OSFI B-13 (operational risk and resilience, including third-party-risk management — which applies to engagements where we are the third party) and OSFI E-23 (enterprise-wide model risk management, which explicitly covers AI/ML models in OSFI-regulated federally-incorporated insurers and banks) are operative for Great-West Lifeco, Canada Life, IGM Financial, and Wawanesa engagements. We wire E-23 patterns into the build from week one — model documentation, performance monitoring, independent validation hooks, ongoing performance assessment — so the model-risk function at the contracting insurer has the artefacts required for a Section 30 OSFI examination. For Manitoba Public Insurance specifically (provincially-regulated, not OSFI-supervised), we mirror equivalent patterns to the same standard.

Carefully and explicitly. For Cargill, Richardson International, Viterra, and broader Prairie agritech engagements where the data is largely commercial-confidential — proprietary yield models, contract terms with growers, internal logistics optimization, export-market pricing strategy — the engagement defaults to source-available delivery (your repo, your IP) with self-hosted Llama 3 on vLLM inside the customer's Canadian VPC where the trade-secret posture requires zero third-party inference. Audit logs capture every prompt and tool call against the trade-secret boundary, and we are explicit on the first call about which classes of data can transit a managed inference API and which cannot.

Your call. We default to AWS ca-central-1 (Montreal) because it is the lowest-latency in-Canada region for Winnipeg with full AWS service coverage including Bedrock for Claude inference and HIPAA / PHIA-comparable controls. Azure Canada Central (Toronto) is the standard Azure route. AWS ca-west-1 (Calgary) is supported and is the closest in-Canada region geographically — useful for Western-data-residency engagements that need to land in the Prairies physically. For FIPPA-scoped public-body engagements or agritech engagements with high trade-secret posture, we self-host Llama 3 on vLLM inside the customer's Canadian VPC for zero third-party inference.

Most v1 engagements at Aiinfox land between CAD 35,000 and CAD 160,000 fixed-price for a focused build — an AI agent, a RAG system, a voice pipeline, a document-intelligence pipeline, or a bespoke ML model. Larger multi-quarter engagements with fine-tuning, OSFI E-23-aligned model-risk work, PHIA-aligned healthcare work, or agritech computer-vision systems over satellite-and-drone imagery typically reach CAD 220,000 to CAD 420,000. Pilots are usually CAD 12,000 to CAD 28,000. Winnipeg clients invoice in CAD via bank transfer or USD by preference. Cost difference versus a Toronto consultancy is roughly 40 to 60 percent on senior rates.