100% Canadian · Source-available · MOTL licensed
The Canadian technology stack you can actually own
Maple Open Tech builds and operates the full stack in Canada — communications, operating systems, hosting, applications, AI and cloud. Standards-based, source-available, and documented well enough that you could run it without us.
Start a conversation See what we build
- Canadian-owned
- Canadian-hosted
- Source-available
- No lock-in
What being fully Canadian actually gives you
Digital sovereignty gets talked about as a matter of principle. In
practice it is a matter of engineering: who maintains the thing, how
quickly they answer, how much of it you can read, and how freely you can
change your mind later.
- Maintainers in your time zone, reachable by name rather than by ticket queue
- Source-available from day one — your team can audit it, extend it or fork it
- Open formats and documented interfaces, so nothing is trapped in our shapes
- A written exit path from the first engagement, because that is what makes it a choice
- Standards-based throughout, so it fits whatever your customers already use
Serving customers anywhere, from infrastructure here
Canadian infrastructure is where the work is done. It is not a limit on
who the work is done for. Our clients sell across Canada, the United
States and further afield, and everything we build is designed to fit
into whatever their customers already run.
- Interoperable by default — open protocols, open formats, no private dialects
- Cross-border ready, with data residency you can actually point to
- Migrations in reversible stages, verified before each next step
- Runbooks written for your on-call, not for us
Six things we build and run
Maple Wireless
Independent, resilient LoRa communication. Long range, low power, and infrastructure you own outright.
- LoRa gateways and nodes
- Mesh and store-and-forward
- Fleet monitoring
Maple Linux
A Canadian-maintained Debian distribution with Canadian-hosted git. Debian’s licensing is untouched; what is Canadian is the maintenance and the people you can call.
- Debian-based, Canadian mirrors
- Canadian-hosted git
- Long-term maintenance
MaplePress
High-performing WordPress infrastructure hosted in Canada, with the heavy work offloaded so sites stay fast as they grow.
- Managed WordPress hosting
- Offloaded search and indexing
- Migration from any host
Maple Apps
Cross-platform applications for everyday productivity, end-to-end encrypted, with the keys held by the people whose data it is.
- Desktop, mobile and web
- End-to-end encrypted
- Keys held by the user
Maple AI
Sovereign AI and Canadian training data. Models that run where you can audit them, trained on material whose provenance is documented.
- Models that run in your perimeter
- Canadian training data
- Documented provenance
Maple Cloud
Storage, email and the rest of the everyday cloud on Canadian infrastructure — with a documented route back out.
- Storage, email and backup
- Canadian data centres
- A written exit path
A licence written to say what we mean
Our software ships under the Maple Open Tech License: source-available
from day one, free for personal, academic and research use immediately,
commercially licensed for four years, and fully open after that. The
ethical limits do not expire with the commercial phase.
- Source visible and auditable from the first release
- Free for personal, academic and research use, immediately
- Fully open after four years, automatically
- Ethical limits that never expire — no automated killing, no mass surveillance
WordPress that stays fast as it grows
WordPress is the right answer more often than its reputation suggests. What goes wrong is rarely the CMS — it is a stack of plugins doing work the web server should never have been asked to do, on hosting chosen by price. We move the heavy lifting off the page, put the data in Canada, and leave your editors the tool they already know.
- Search and indexing offloaded, so a large catalogue stays quick
- Canadian hosting for the database, the media and the backups
- A plugin audit that says what each one actually costs you
Where WordPress Sites fit
Publisher catalogue
Hundreds of titles, faceted search
Membership site
Gated content and renewals
Multi-site network
One codebase, many brands
Static sites that build in seconds and serve in milliseconds
A site that does not need a server to render a page does not need a server to be attacked. For anything published rather than transacted — a brochure, a documentation set, a catalogue — static is faster, cheaper and quieter to own. Your team still edits in a browser; there is simply no database underneath to patch or defend.
- No database and no admin panel, which removes most of the attack surface
- Builds in seconds, so a correction is live before the meeting ends
- Accessibility verified at build time rather than audited after launch
Where Hugo Sites fit
Documentation set
Versioned and searchable
Brochure site
Verified contrast throughout
WordPress migration
Every url preserved
Applications that answer to you
Most internal tools begin as a spreadsheet that outgrew itself and end as a subscription that fits badly. Between those is an application built to the shape of the work — your data model, your hosting, your export path, and no per-seat licence that reprices itself every year.
- A data model built around your process, not a template you bend to fit
- Standards-based APIs, so the next thing you build can talk to this one
- Exports that work, in open formats, tested rather than promised
Where Web Apps fit
Operations dashboard
One view of several systems
Client portal
Documents, approvals, history
Workflow tool
The spreadsheet, made auditable
iOS and Android, from one codebase
A mobile app is a promise to maintain something on two platforms that change every year. We build the ones worth that promise — where being on a phone is the point rather than a box to tick — and we say so plainly when a good mobile website would serve you better.
- Offline-first, because field work happens where signal does not
- End-to-end encryption where the data warrants it, keys held by the user
- Store submission handled, including the review notes nobody warns you about
Where Mobile Apps fit
Field data capture
Works offline, syncs later
Companion app
The parts that belong in a pocket
Secure messaging
Keys never leave the device
Software that runs on the machine in front of you
Some work does not belong in a browser tab: large files, long-running jobs, hardware, or data that should not leave the building. Desktop software is not a step backwards when those are the constraints — it is the only thing that meets them.
- Windows, macOS and Linux from one codebase
- Real performance on large files, with no round trip to a server
- Air-gapped operation where the work requires it
Where Desktop Apps fit
Media processing
Gigabyte files, handled locally
Instrument client
Talks to hardware directly
Offline archive
A whole collection, no network
Straight answers about where AI helps, and where it does not
Most organisations are being sold AI before anyone has asked what it is for. The useful work is narrower and duller than the pitch, and it starts with a question nobody enjoys: what are you actually allowed to put into a model? We will decline most use cases, and show you why.
- A data boundary: what may go to a model, what may not, and how that is enforced
- Local and private model options, costed against the hosted ones
- A written policy your staff can follow, in a page rather than twenty
Where AI Strategy fits
Use-case triage
Ranked, most of them declined
Private model
Runs inside your perimeter
Staff policy
One page people actually read
The few controls that stop most of what happens
Security advice usually arrives as a list of everything, which is indistinguishable from no advice. The useful version is short, ordered, and honest that a small organisation cannot do all of it at once. We start with what would actually hurt, and work down from there.
- Backups that have been restored, not merely scheduled
- Identity hardening: multi-factor, least privilege, joiner-mover-leaver
- An incident plan short enough to follow at 3am
Where Cyber Security Strategy fits
Posture review
Ranked, sized to what you can do
Restore drill
Proof it works, timings recorded
Incident runbook
Who calls whom, in what order
How an engagement runs
01
We start with a clear picture
Together we map what you run today: who looks after each piece, what it costs, and what your options would be if you ever wanted to change direction. It is the most useful part of the whole engagement, and it is the part most teams have never had written down. Some clients stop here, happily — that is a good outcome.02
Then we decide together what is worth moving
Not everything should move, and we will say so. We weigh what a Canadian stack genuinely improves against what the change would cost in money, effort and disruption — and we show you the reasoning, so the decision is yours to make with the full picture in front of you.03
Then we move things, carefully
We work in small stages, each one checked before the next begins and each one reversible. You keep operating throughout. Nothing moves until we have actually tested the way back, not just written one down.04
Then we hand it over properly
You get runbooks written for the people who will be on call, and time with us while your team settles in. The point of owning your stack is not needing a supplier — and we mean that about ourselves too.
Tell us what you are building.
That is the whole first conversation — no discovery workshop, no maturity assessment, no deck. If a Canadian stack would serve it better, we will tell you what that takes. If it would not, we will tell you that just as plainly.