MapleJockey: Canadian tools, evidence and migration
17 November 2026 | Founder-led private increment | maplejockey.com
Product direction
Help Canadian organisations choose useful tools, understand the control they actually gain and move with a tested way back. The catalogue is the discovery layer. Migration guides turn an interesting alternative into a bounded experiment. The assessment workspace records the evidence, requirements and remaining dependencies behind a decision.
This extends the 12 November charter in response to Max's direction. That charter deliberately deferred a broad supplier directory. The current increment authorises a local, source-linked catalogue and migration guides alongside the assessment, using existing tools and no new external spend. It does not approve the charter's contracted budgets or pricing hypotheses.
The five starting sectors are security, defence, sales, research and marketing. Sales and marketing are business functions rather than industries, so entries can appear under several sectors. Shared infrastructure supports all five. Coverage is expandable; this release is an initial reviewed catalogue, not a complete census of Canadian technology.
Three connected jobs
- Find a Canadian option. Search by workflow, incumbent tool or sector. Read why an entry is included and what is still unknown.
- Plan a safe move. Choose an object-level migration guide, inspect what will be lost, define acceptance checks and retain rollback.
- Substantiate the result. Record the selected product, contract, tenant region, support access, key control and recovery evidence in the assessment workspace.
An entry is a candidate for evaluation. A shared category does not establish feature equivalence, a supported import path, a recommendation or suitability for regulated information. For some enterprise workflows, a complete Canadian replacement may not exist; partial substitution or a better-controlled incumbent deployment can be the honest outcome.
Canadian identity and language
- Brand: MapleJockey. Descriptor: Canadian tools. Informed choices. Practical migration.
- Visual identity: a distinct stylised maple leaf, maple red, warm white and charcoal. No government wordmark, coat of arms, certification seal or implied endorsement.
- Language: Canadian English,
en-CA, Canadian spelling in authored copy, CAD for future estimates, metric units where relevant and unambiguous dates. Preserve official product names, source titles, filenames, API fields and quoted technical identifiers. - The 18 November 2026 local preview offers Canadian English and French across the catalogue, migration guides, workbooks, assessment, pilot and news. New editorial records require both languages.
- Lead with the work a person needs to do. Show ownership, residency and control evidence separately rather than a single patriotic badge.
Catalogue evidence policy
Every material claim has an ID, dimension, status, scope, reason, date and source references. Unknowns have a dated gap statement and the evidence required to resolve them. Reviewing a supplier page establishes what the supplier declares, not what a tenant actually does. An official government or institutional record can establish its documented scope without proving every downstream service arrangement.
Six dimensions remain separate: Canadian connection; ownership and jurisdiction; data residency; support and administrator access; key control; and portability. Canadian headquarters, incorporation, founding, ownership, operation and hosting are different facts. Public resources and foreign-owned providers with a Canadian region can be listed transparently as enabling assets, with that connection stated explicitly.
The assessment prototype retains Observed, Supplier-declared, Document-reviewed, Inferred and Unknown provenance, with Conflicting and Stale states recorded separately. The initial public-source catalogue mostly contains supplier declarations, reviewed documents and unknowns; it does not invent tenant observations. Source review dates are point-in-time checks, not ongoing monitoring.
Conflicting evidence must retain both sources and their scopes. Do not silently choose an older marketing page over current terms. A corporate acquisition, new subprocessor, changed region, changed export format or changed documentation should trigger a re-review. Before an actual purchase or move, recheck all decision-critical claims regardless of the catalogue date.
Coverage and prioritisation
The phrase “top used” is a research objective. The initial incumbent names are familiar candidate workflows, not a measured Canadian market-share ranking. Rank future work using the tools actually named by qualified pilot organisations, the urgency of their buying trigger, feasible migration paths and the consequences of failure. Keep separate counts for organisations interviewed, distinct workloads and tools named.
| Sector | Initial workflow coverage | Incumbent candidates to investigate, unranked | Important expansion gaps |
|---|---|---|---|
| Security | Passwords, MDR, orchestration, forensics, awareness, data security and cryptography | Microsoft Sentinel, CrowdStrike, Splunk, LastPass, Okta, KnowBe4 | Tested SIEM rule and detection migration; identity; endpoint replacement; evidence-chain preservation |
| Defence | Supplier cyber services, secure communications, keys and a gated document-workspace discovery guide | Microsoft 365/SharePoint, Box, Jira/Confluence, engineering repositories | Contract-specific information handling; CAD/PLM; classified systems; export controls; approved supplier evidence |
| Sales | CRM, service operations, customer intelligence and sales video | Salesforce, HubSpot, Pipedrive, Dynamics 365 | Full relational CRM migration; email history; custom objects; territory models; forecasting and commissions |
| Research | Review software, qualitative analysis, data repositories, compute/network resources and public datasets | Dropbox, Google Drive, Qualtrics, NVivo, REDCap, AWS research workflows | Survey platforms; laboratory systems; institutional identity; restricted research data; reproducible compute environments |
| Marketing | Email, social scheduling, landing pages, reporting and agency operations | Mailchimp, HubSpot Marketing Hub, Sprout Social, Buffer, Google Analytics, Looker Studio | Attribution continuity; historical analytics; consent evidence; automations; ad-platform dependencies |
| Shared infrastructure | Canadian hosting options, file collaboration, DNS and enabling resources | AWS, Azure, Google Cloud, Cloudflare, Dropbox | Email/collaboration; backup; domain lifecycle; e-signature; accessibility; regional procurement and Indigenous-led resources |
These are coverage gaps, not claims that suitable Canadian alternatives do not exist. Research-specific, Indigenous data sovereignty and community-governed resources need their own expertise and participation, not automatic inclusion under the federal institutional framework.
Migration publication standard
Each guide must identify the source and target product and plan, the objects included, export/import formats, permissions, field mapping, expected losses, elapsed-time target, completeness checks, functional checks, stop conditions and rollback. Record the version/date of the documentation and whether the guide is desk-reviewed, rehearsed using synthetic data, tenant-tested or production-observed. Never promote one maturity level to another without evidence.
Counts and file checksums are necessary where applicable but insufficient by themselves. Test the user jobs: sign in with the right role, find a record, use an attachment, preserve an exclusion/suppression list, open a research file or deny an unauthorised share. Retain the original until a workload owner accepts the scoped result and a rollback window has passed.
A password CSV export is plaintext. Handle it on an approved local device, keep it out of cloud sync and tickets, minimise copies, and follow the organisation's approved deletion process. Moving marketing contacts must preserve consent evidence and exclusions; importing a contact is not permission to send a message.
Defence content is a separate gate. Contract-specific classification, handling rules and approvals determine the destination and method. A Canadian provider entry, a security badge or a generic migration tutorial never authorises moving controlled information.
Policy boundaries
The Government of Canada's Digital Sovereignty Framework describes federal internal operations and does not introduce new requirements. It does not automatically bind every Canadian private organisation. [P1]
Customer-managed encryption keys are not necessarily customer-controlled keys. The Cyber Centre distinguishes provider control from customer lifecycle management; establish who can actually use the key and decrypt the data. [P2]
The current federal Level 1 CPCSC guidance describes requirements for select defence contracts. Applicability and the assessment scope come from the actual contract; the catalogue does not confer certification. [P3]
Commercial role and independence
The free catalogue and bounded guides are an acquisition hypothesis. The proposed paid work remains assessment, migration readiness, a supervised rehearsal and recurring evidence maintenance, with scope and prices to be validated. No projected revenue is treated as committed.
Publish the same evidence standards for every supplier. Keep sponsorship, referral fees, hosting sales and Sopka relationships separate from findings and inclusion decisions. Disclose any commercial relationship next to the entry if one is later created. There are no paid placements or newly arranged referral relationships in this increment.
Next pilot gate
Use one accessible, non-sensitive workload and one migration route. Agree the actual source/target accounts, ownership, business acceptance checks, allowable outage, recovery objective and rollback owner. Obtain the product/tenant evidence needed to resolve decision-critical unknowns. Then perform a small authorised export/import/re-export rehearsal and report losses as well as successes.
Before an external engagement: settle contracting/IP entity, terms, customer evidence handling and permission for any customer access. Those decisions do not block this local catalogue, guides or assessment prototype. External outreach remains draft-only; publication and spending require separate scope and approval.
Primary references
- P1: Treasury Board of Canada Secretariat, Digital Sovereignty Framework, reviewed 17 November 2026.
- P2: Canadian Centre for Cyber Security, Guidance on cloud service cryptography, section 3.3, reviewed 17 November 2026.
- P3: Public Services and Procurement Canada, Level 1 cyber security certification requirements, reviewed 17 November 2026.