Your team serves the community.
We run the technology.
Jumex is a small, accountable team in Calgary. We design, build and operate the websites, portals and private AI that community organizations rely on — and the hardware and data centre behind them. We answer for all of it.
Run by Mark Iwankow, partner-founder and CIO/CTO — he answers ops@jumex.org.
Privacy-forward by design · accessible to WCAG 2.2 AA · no third-party analytics
What we run for you.
One accountable team, built around community organizations. Take the whole stack or the piece you're missing — the scope is written down before anything starts.
Fractional CIO/CTO (vCIO / vCTO)
Fractional CIO and CTO leadership for organizations without an IT executive: a technology roadmap tied to your mission and budget, vendor and contract oversight, and board-level reporting on risk, spend and readiness.
AdvisoryManaged technology
Day-to-day operations for the systems your organization depends on: monitoring, patching, backups, access control, and a named person who answers when something breaks.
Managed serviceHardware, on site
Advanced hardware setup and maintenance — servers, workstations, networking and GPU machines: specification, installation, commissioning, repair and replacement, for organizations that would rather not buy blind or maintain it alone.
Project + managedData centre planning and management
Room, rack and power planning, build-out, and ongoing management. We coordinate the electrical, networking and colocation contractors for the room with our Alberta partners, so you deal with one team.
Project + managedWebsites and portals
Public sites, owner and board portals, resident services and document libraries — designed for the people who actually use them, including seniors and first-time visitors.
Project + managedPrivate AI, deployed
Assistants, document workflows and AI concierges running on hardware we operate in Calgary. AI takes the routine questions; a person takes anything that matters. Your records are not sent to a third-party cloud to make the model work.
Project + managedSecurity and privacy operations
Access reviews, backup verification, incident response and data-residency decisions — written down so your board can see them, not buried in a vendor portal.
Managed serviceSupport and hand-over
Plain-language support for staff and residents, onboarding, and documentation that lets you take the service in-house when your team is ready. Leaving is the goal, not the upsell.
SupportA live deployment, and the work behind it.
We don't ask you to trust a demo. One community is running on this service today — and we take on a small number at a time, so each one gets the same team. The checks we run on our own stack are published.
A community's own digital front door.
Mountain View Terraces is a Springbank Hill community of owners and board members. Jumex built and operates its public website, owner and board portals, and an AI concierge that answers residents in plain language — including seniors who would rather talk to a person. Resident records stay on the same private fleet in Calgary.
We test our own AI before it answers a resident.
In the Absinthe Probe, we handed a local model its own architecture card with one number quietly wrong, then asked whether it was correct.
- Question
- Will a model rubber-stamp a description of itself, or check the evidence?
- Method
- One corrupted model card, one question, run on our own hardware. Every row checked against GGUF metadata and raw tensor shapes, with the full session published.
- Finding
- It caught the error, verified its architecture line by line, and volunteered two limits: multi-token prediction was absent from the weights file it was serving, and the 1M-token context was a claim, not an enabled setting.
- Limits
- One model family, one weights file, one session. This is not a general claim about model honesty or security.
Stewardship.
You hold other people's information and your donors' trust. Stewardship is the operating standard: it decides how we build, what we log, and who we let near the data.
What stays yours
In writing, before the first invoice.
- Your records and content. You own them; we operate them.
- Your decision on where data lives, documented.
- Your access list — who can see what, reviewed with you.
- Your exit: a documented hand-over, not hostage data.
What we run
The part you shouldn't have to think about.
- Hardware, backups and monitoring in Calgary.
- The data centre and its partners: power, cooling, cabling, physical access.
- The private model stack and the AI concierge.
- Patching, access control and incident response.
- A named person who answers, within one business day.
Privacy
No third-party analytics or tracking pixels. Client records are not used to train models.
Accessibility
Built to WCAG 2.2 AA and reviewed with the people who use the service, including seniors.
Continuity
Backups nightly and documented; restore runbooks kept with the service, not with one person.
Social sensitivity
Plain language, no dark patterns, and no automated decision that takes a human out of the conversation.
Who you'll work with
Mark Iwankow
Partner-founder and CIO/CTO
He brings 30+ years in IT infrastructure and cybersecurity and a CISSP (ISC2) to every engagement, has run Jumex since 2012, and answers ops@jumex.org himself. He also signs the monthly report. Profile
Work is delivered by the same small team, with Alberta partners brought in for electrical, networking and colocation — so the room and the systems in it stay one relationship.
What your board sees, every month.
Transparency is a deliverable, not a value statement. One written report, in plain language, covering:
- Uptime, and every backup verified — with the restore test that proves it.
- Access changes: who was added, removed, or given more.
- Incidents, what happened, and what we changed afterwards.
- Spend against the scope you approved, line by line.
Tell us what you're responsible for.
A community, a board, a research program, a system that has outgrown its owner. We'll tell you honestly whether we're the right partner — and what a first project would take.
- Send a note through the form, or email ops@jumex.org.
- A person replies within one business day — usually faster.
- If it fits, we scope the first project in writing before any invoice.
ops@jumex.orgYou reach the person who builds it, not a queue.
Springbank Hill, Calgary, Alberta