AI development company for Edmonton energy services, AMII-adjacent research, engineering, and Alberta healthcare.

We do not operate an Edmonton office. Aiinfox runs from our Mohali, India HQ and a Frisco, TX office. For Edmonton clients, our Frisco pod runs Central Time (one hour ahead of Edmonton — a standard 9am-to-5pm CT shift covers Edmonton 8am-to-4pm MT cleanly), and our Mohali team picks up Edmonton mornings via an early-IST start (8:30pm IST is 9am MT). For on-site engagements at Jasper Avenue, the ICE District, the U of A campus, AMII at Athabasca Hall, AHS sites, or the Industrial Heartland (kickoff, milestone reviews, security walk-throughs), we travel to Edmonton on a scheduled cadence rather than maintaining a sub-scale local presence.

No, and we are direct about that on the first call. The Alberta Machine Intelligence Institute (AMII) at the University of Alberta is one of three Canadian Pan-Canadian AI Strategy institutes alongside Mila and the Vector Institute, and AMII members include researchers like Richard Sutton in reinforcement learning. Aiinfox is not a member, we do not publish at NeurIPS, we do not have AMII faculty on payroll, and we will not pretend otherwise. What we bring to an AMII-adjacent scaleup is the production engineering layer between a research artefact and a real product — typed-tool-call agents, structured-extraction pipelines, eval harnesses, observability, guardrails, and the hand-off documentation that gets the system to a real user while AMII-trained researchers get back to research. If your engagement genuinely needs a research-lab partner with publication output, we will recommend a direct AMII industry-partnership engagement instead.

Yes. Alberta HIA (the Health Information Act, administered by the Office of the Information and Privacy Commissioner of Alberta) imposes obligations on custodians of health information that go beyond PIPEDA's federal commercial baseline — duties of custodians, consent rules, the right to access and correct, breach reporting to the OIPC of Alberta, and specific provisions for foreign-based service providers handling Alberta health information. For AHS-adjacent, U of A Hospital-adjacent, Stollery Children's-adjacent, and Cross Cancer Institute-adjacent healthtech, BAAs or equivalent DPAs are signed before any health information is shared; deployments default to AWS ca-central-1 (Montreal) inside customer-controlled Canadian clouds so health information never leaves Canada (with ca-west-1 Calgary supported where in-Alberta residency is preferred); every model and tool call is audit-logged with input, output, prompt version, and operator identity.

Yes. Alberta PIPA (the Personal Information Protection Act) governs private-sector personal information generally and is the Alberta-specific analogue to PIPEDA — overlap is substantial but Alberta PIPA has its own notification and consent specifics. Alberta FOIP (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 Alberta ministry engagements and Alberta Crown-corporation engagements, 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 ca-west-1 or self-hosted Llama 3 on vLLM inside the customer's Canadian VPC.

Carefully and explicitly. For Suncor Edmonton, Imperial Strathcona, ATCO, EPCOR, and broader Industrial Heartland engagements where the data is largely commercial-confidential — proprietary process models, internal logistics, contract terms with suppliers, emissions and environmental telemetry — 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. For permits and regulatory filings under AER (Alberta Energy Regulator) and CER (Canada Energy Regulator) where the documents are public-facing, document intelligence on managed inference endpoints is supported. Audit logs capture every prompt and tool call against the trade-secret boundary.

Your call. We default to AWS ca-central-1 (Montreal) because it has full AWS service coverage including Bedrock for Claude inference. For Alberta data-residency engagements that need to land in Alberta physically — typically Government of Alberta FOIP-scoped engagements and energy-services engagements with internal data-residency policies — we use AWS ca-west-1 (Calgary), which has progressively expanded service coverage and is the closest in-Canada region to Edmonton. Azure Canada Central (Toronto) is supported. For high trade-secret or FOIP-scoped engagements, we self-host Llama 3 on vLLM inside the customer's Canadian VPC for zero third-party inference.

Yes, at the document-intelligence layer. AER (Alberta Energy Regulator) permits, abandonment and reclamation filings, OneStop submissions, and CER (Canada Energy Regulator) pipeline filings are the classes of document we have shipped structured-extraction pipelines for. Layout-aware models, JSON-schema output, confidence scoring, and a review queue that flags low-confidence fields for human sign-off before submission. We do not write the regulatory submissions themselves — that is your regulatory team's job — but we ship the engineering glue that gets your operational data into a submission-ready state faster.

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, energy-services predictive-maintenance ML, Alberta HIA-aligned healthcare work, or FOIP-scoped public-body work typically reach CAD 220,000 to CAD 420,000. Pilots are usually CAD 12,000 to CAD 28,000. Edmonton clients invoice in CAD via bank transfer or USD by preference. Cost difference versus a Calgary or Toronto consultancy is roughly 40 to 60 percent on senior rates.