We do two things. We help companies outside Canada incorporate, get licensed and start operating here. And we build AION Nexus, a CRM for firms that answer to a regulator. Both come from the same place: knowing what a regulator will ask, and building for it early.
Two business lines.
We take companies from outside Canada through incorporation, licensing, tax registration and the operational setup that follows. You get one team from the first filing to your first Canadian customer, and a plan with dates on it.
Learn MoreRun your pipeline, your accounts and your onboarding on a CRM that was built for firms under supervision. Scores that explain themselves, an audit trail that detects tampering, and tenant isolation enforced twice. Pre-GA, with the full roadmap on the product pages.
Learn MoreFour things you can verify without a call.
The whole surface is published as an OpenAPI 3.0 specification: over 350 REST endpoints across over 140 data models. Your engineers can judge it for themselves.
Of over 16,000 automated tests, one runs against real PostgreSQL on every build and tries to read across tenants. Another fails the build outright if a money-movement route skips its authorization guard.
Our control matrix maps what is implemented, what is designed, and what is neither. We send it under NDA with the gap analysis attached.
AION Global Inc. is a federal corporation under the Canada Business Corporations Act, incorporated in October 2023. Search corporation number 1546101-4 at Corporations Canada.
AION Nexus
Pipeline, accounts and client onboarding in one place, built for firms that answer to a regulator. Add a financial-operations layer when you need it, on the same data model and audit trail.
Pre-GA: first production deployment with a design partner
Product shape
One data model, one permission model and one audit trail, so turning on the financial layer later is a configuration change.
Accounts, contacts, leads, deals, documents, proposals, forecasting, territories, teams and ownership, and scoring that explains itself. Gmail and Microsoft 365 mailbox sync, an in-app calendar and reminders.
Explore CRM coreCurrency dealing, payment instructions, settlement, ISO 20022 reconciliation, SWIFT messaging and rule-driven compliance. It instructs your providers and never holds your funds.
Explore Financial OperationsFit
Built for these teams. Privacy and anti-money-laundering rules follow each tenant's jurisdiction: UK GDPR, MLR 2017 and POCA with AWS London, or PIPEDA and FINTRAC with AWS Canada Central.
Registered with a regulator, screening counterparties, with a CRM that holds up when an examiner samples it.
Onboarding, verification and a decision trail on the same record as the commercial relationship.
Suitability, reviews and disclosures kept where the relationship is managed.
Prove who changed a record and why, without answering from memory.
Artificial intelligence
A supervisor can ask you to explain any decision. Here is where each kind of automation sits.
Lead scoring and next-best-action are weighted rule engines. Each gives a score, a band and a written explanation.
The assistant uses a large language model with API keys you supply, rate-limited and audit-logged.
Assistants may prepare a payment and can never authorize one. The money-movement guard enforces that on every request.
Narratives are drafted with Anthropic and always signed off by a compliance officer. In the UK, reports are filed manually to the NCA, with DAML tracking. For FINTRAC, the product prepares suspicious-transaction and large-cash reports and keeps a reportable-transaction register.
No score comes from a model whose weights were learned from data.
Forward-looking indicators are the same rule engines on current data, labelled as such.
An accuracy figure needs a model and a validation set; there is no model here. What you get is reproducibility.
Every score can be explained and reproduced.
Platform
Frameworks the product is built against
Alignment describes how the product is built; badges mark where no attestation exists yet. Read our compliance and security posture
Bring your own keys: every integration stays off until you supply credentials.
Roadmap
Each item names the work in flight and the point at which it closes.
Runs today in development, continuous integration and staging. AWS infrastructure-as-code for London and Canada Central is written and not yet applied. The first production environment goes up with our design partner.
Control matrix, evidence and gap analysis are complete, under NDA. The audit is next. No report has been issued, so we call this readiness.
Scope and runbook are written. It runs, with findings fixed, before the first production deployment.
Working together
A design partnership with direct influence over the roadmap, staged in small steps.
A technical review against your requirements: the evaluation brief, compliance evidence under NDA and a product walkthrough.
A bounded deployment with a limited dataset and a named team.
Isolation enforcement and multi-factor authentication are built and get switched on in your environment, and an external penetration test runs with its findings fixed.
Turn on the financial module against live vendor rails once the CRM has settled.
Architecture, data model, permissions, integrations and maturity, written for engineers.
Request this documentWhat AION Nexus is, where it stands, and what a design-partner engagement involves.
Request this documentControl by control: implemented, designed, and open. Sent under NDA.
Request this documentOver 350 endpoints across over 140 data models, as a machine-readable OpenAPI 3.0 document.
Request this documentEntity structure, registration, tax accounts, banking, employment and privacy for operating in Canada. Released after review.
In preparation
AION Nexus CRM
The always-on core of AION Nexus. Pipeline, accounts, activities, documents and proposals, on a security model designed for a platform that settles payments.
A general-purpose CRM can be configured to do much of this. Four things came first here: tenant isolation you can demonstrate to an auditor, a tamper-evident audit trail, permission domains that match how a regulated firm separates duties, and a deal model that understands currency.
Pipeline
Stages, win probabilities and entry and exit criteria are configured per tenant, so the system enforces your process.
Relationships
Health scores draw on contact recency, ninety-day volume, stalled deals, open complaints and outstanding balances.
Collaboration
Every one of these is written to the audit trail like any other action.
Scoring and data
Lead scoring is a weighted rule engine. Nothing in it learns its own weights from your data, so identical inputs always give an identical, explained score.
Roadmap
The next items, in the order a design partner sets.
A design partner sets the order, starting with calendar sync and telephony.
AION Nexus Financial Operations
Dealing, payments, settlement, reconciliation and compliance on the CRM's data model, permissions and audit trail. Optional.
Implemented against real vendor contracts; has not yet run against live rails.
Control model
Five invariants that fail closed. Every money route passes one guard, and the build fails if one does not.
The platform never holds client funds. It instructs your providers.
Every execution needs a bound authorization record, protected by a SHA-256 integrity check. An altered one is refused.
The default provider is hard-coded as unavailable, and revoking a credential severs execution against that provider.
Self-approval is rejected at any amount. A second authorizer is required above a threshold that defaults to CAD/GBP 10,000.
Automated and assistant-driven actors may prepare a payment but can never authorize one.
Dealing and payments
Maker-checker throughout.
Reconciliation and messaging
Native message handling.
Compliance engine
Rule-driven and explainable.
Until vendor credentials are configured, identity verification uses a demonstration scorer that returns a randomized risk value.
Treasury
Forecasting, liquidity and risk.
Maturity
Live code is separated from built code, capability by capability.
| Capability | Status | Detail |
|---|---|---|
| Money-movement control model | Live | Enforced and tested. |
| Per-tenant module gating | Live | HTTP 403 when the module is disabled. |
| Compliance rule engine | Live | Deterministic. Vendor screening awaits credentials. |
| Dealing, payments and settlement | Built, awaiting live rails | Built on real provider contracts; never run against live rails. |
| Mark-to-market and margin calls | Built, awaiting live rails | Shipped with margin facilities; awaiting live rails. |
| Position and risk book | Built, awaiting live rails | Shipped with end-of-day snapshots. |
| ISO 20022 and SWIFT messaging | Built, awaiting live rails | Tested against sample messages. |
| Vendor rails | Built, awaiting live rails | Every integration stays off until you supply keys. |
| Settlement calendar | Partial | Working; complete once compliance signs off the holiday table. |
| General ledger | Partial | Purpose-built ledger; third-party ledger behind a disabled flag. |
| Settlement netting | Planned | Instructions settle individually; netting starts with the first design partner that needs it. |
Send us your questionnaire and we will answer it in writing, early and in full. Below: current controls, what we send under NDA, and where assurance stands.
AION Nexus is pre-GA. The framework work described here is readiness, not attestation. No audit report has been issued.
Each one is implemented in code and covered by tests.
A row-level security policy on every tenant-scoped table, plus scoping in the application. A real-PostgreSQL test attempts a cross-tenant read on every build.
Personal and identity-verification data is encrypted with AES-256-GCM, and a key rotation re-encrypts existing data. The default mode keeps plaintext; encryption is enabled per deployment.
Audit records are hash-chained per tenant, and a verification sweep checks each chain, so an edit or deletion is detectable.
Twenty permission domains with seeded roles including Compliance Officer and Auditor. Role changes and data exports are approval-gated, so no administrator can quietly grant or take.
Vendor credentials sit in a bring-your-own-key vault; revoking one severs execution against that provider. Sign-in uses time-based one-time-password multi-factor authentication.
UK GDPR and PIPEDA are both supported, with hosting on AWS London or AWS Canada Central. Privacy and AML rules follow each tenant jurisdiction.
These exist today, and we send them before any commercial conversation.
Control by control: what is implemented, designed, or neither.
What an assessment would find missing today, and what closing each item takes.
Architecture, data model, permissions and integrations, written for your engineers.
The full API surface, over 350 endpoints across over 140 data models.
Where each piece of external assurance stands, and what closes it.
We take companies from outside Canada through incorporation, licensing, tax registration and operational setup.
Take one piece or the whole programme.
We run the whole incorporation, federal or provincial, and tell you which one suits you.
We work out which federal and provincial rules apply, then set you up to meet them early.
We build the entry plan from your numbers: who already sells to your buyers, and which channel merits your first hire.
Three stages, each with a visible result.
A free session on your structure, regulation and competitors.
A written entry plan with timelines, milestones and cost estimates you can budget from.
We do the work alongside you, from filing to bank accounts, through your first operating milestones.
Companies entering Canada, and those already here.
Answered before you book a call.
Federal CBCA incorporation gives you name protection across Canada, but you still register extra-provincially in each province where you operate. Provincial is simpler if you will only operate in one. Most companies entering from abroad are better off federal.
It depends on where you incorporate. Federal CBCA corporations generally require at least 25 per cent of directors to be Canadian residents, with an exception where there are fewer than four directors. Some provinces, including British Columbia and Ontario, have no residency requirement.
Incorporation takes days; the timeline is set by the business number, CRA accounts, bank account and any sector licence. For an unregulated software company, four to eight weeks is realistic. A financial services licence puts you in quarters.
Government filing fees are modest and published. We give you a fixed figure with the plan, and you can buy a single service.
Two lines of work, one skill underneath both: knowing what a Canadian regulator will ask, and building for it early.
AION Global Inc. was founded in 2023 by Sonya and Christopher Cleroux, who saw the same problem from two directions. Sonya advised foreign companies through Canadian market entry and watched capable businesses stall on regulatory process. Christopher built systems for firms that answer to a regulator and watched teams bend general-purpose software to fit.
The consultancy takes companies through incorporation, licensing and operational controls. AION Nexus is the software version: a CRM for regulated financial businesses, with an optional financial-operations layer, approaching its first production deployment with a design partner.
A federal Canadian corporation, checkable against the Corporations Canada register.
Search the federal register for corporation number 1546101-4.
Chief Executive Officer
Sonya leads the consulting practice, guiding foreign companies through Canadian incorporation, licensing and the regulatory obligations that follow.
LinkedInChief Technology Officer
Christopher leads the engineering behind AION Nexus. He is responsible for the platform's isolation model, its audit design, and the decision to keep scoring deterministic and explainable.
LinkedInPlanning a move into Canada or evaluating AION Nexus, send us the details. We reply within one business day, and answer security questionnaires in writing.