Skip to content
Asmar.

§ 01 — Asmar Momand · Toronto / Remote



I architect distributed systems, design the cloud underneath, and write the code that ships them. Solo when the team is small. With a team when it's not. The diagram above is the posture I keep returning to — distributed, event-driven, multi-tenant, pure-domain.

For founders and engineering leaders who need an architect who can also build: I take an idea through architecture, solution design, cloud infrastructure, implementation, and delivery — end-to-end, without handing off at the blueprint and walking away.

Senior software solution architect. Twelve years across public financial management, private FinTech & wealth management, and product. Currently at iA Financial Group, founding Ghasi Technologies in parallel.

§ 01·5 — What I do

I take ideas
from whiteboard
to production.

Most architecture practices end at the blueprint. Mine starts there. I move with a project across the whole lifecycle — framing the idea, mapping the bounded contexts, designing the solution, standing up the cloud, and writing the code that actually ships. When the team is small, I do all of it. When it's not, I lead it.

  1. 01

    Idea framing

    What's the real problem, and what changes if we solve it?

  2. 02

    Architecture

    Bounded contexts, ADRs, integration patterns, risk register.

  3. 03

    Solution design

    Service blueprints, API contracts, event schemas, data model.

  4. 04

    Cloud infrastructure

    GCP / AWS / Azure. Networking, security, observability.

  5. 05

    Implementation

    Production-grade code, with the team or alone.

  6. 06

    Delivery & deployment

    CI/CD, drift gates, on-call, the boring parts that matter.

00

years

of practice across public financial management, private FinTech & wealth management, and product.

0

platforms

in the Ghasi suite — health, education, hospitality, intake, comms.

00

services

across the portfolio. Domain-driven, event-backed.

0

clouds

hands-on across GCP, AWS, and Azure — architecture and infrastructure.

§ 02 — Recent work
§ 03 — Method

Three convictions I keep returning to.

1

The domain layer is sacred.

Pure TypeScript, no framework imports, no leakage. Everything else is replaceable.

2

Multi-tenancy is not a feature flag.

It's a non-negotiable enforced at the domain, the database (RLS), and the API — or it's not multi-tenancy.

3

Architects who don't ship lose calibration.

Blueprint-only architecture decays. The discipline of running production keeps the design honest.

§ 04 — Work with me

01

Advisory

2–8 hours / week

Architecture review, ADRs, second-opinion on a roadmap. Interview support for senior hires.

Best whenyou have an instinct that something is off and need a fast calibration check.

02

Solution Design

4–8 weeks · fixed scope

Bounded-context maps, service blueprints, event schemas, ADRs, POVs and POCs, vendor evaluations.

Best whenyou know what to build and need someone to hand the team a real blueprint plus the decisions behind it.

03

Embedded Lead

1–2 quarters

Tech lead / architect role on a delivery. I own the design and supervise — or write — the build.

Best whenyou have a funded program but no senior architect on the team yet, and you want one for a fixed stretch.

Designing something hard?

I take a small number of architecture-and-build engagements per quarter, and I'm currently open to senior, staff, and principal-level architecture roles.