$ Infrastructure & Deployment Engineering
I help small teams deploy, document, and maintain the systems they depend on. Cloud, self-hosted, or a sensible mix of both.
Deployments, CI/CD, monitoring, backups, and docs.
Based in Montréal, Québec
Managed cloud or self-hosted, depending on what your setup needs.
The useful stuff behind a deployment that stays up.
Get your app live without crossing your fingers. I package it, configure its environment, and add monitoring and backups from day one.
Start with infrastructure your team can actually understand. I set up servers, networking, storage, and automation so the whole thing is reproducible and documented.
Move without the usual moving-day chaos. I plan the cutover, migrate your data, and test the new setup before traffic follows.
Keep things healthy after launch. I handle updates, watch for trouble, check backups, and fix issues before they become everyone else's problem.
Also handy
Hear about problems from your monitoring, not your users. Get useful alerts, dashboards, and logs without drowning in noise.
Choose open-source tools that fit your needs and your appetite for maintenance. I help you compare, configure, and own the right stack.
Everything comes with docs, so future-you and your team are not left guessing.
Small teams that need solid infrastructure they own.
Get dependable infrastructure without building a full IT department. I handle the technical plumbing so your team can get back to the actual business.
Ship client projects without becoming their forever-DevOps team. I handle hosting, deployments, and handoff docs so everyone knows what they own.
Keep building your product while I make deployment smooth and repeatable. You get a setup you can own, hand off, and grow with.
A few systems I have built, shipped, and kept running.
An asset-tracking platform built with a team for Dawson College, replacing spreadsheets across four departments.
A real-time multiplayer card game built with a team and hosted end to end on managed cloud infrastructure.
More than 17 services running on my own hardware, where I test the tools and patterns I recommend to clients.
You will know what is happening, why, and what comes next.
First, I learn what you have and where it hurts. You get a clear map of what is fragile, undocumented, or worth changing.
Then I build, migrate, or tidy up. Security, backups, and monitoring are part of the setup, not chores saved for later.
Nothing ships without docs. Your team gets plain-language instructions and enough context to run the system without depending on me.
Need help after handoff? I can answer questions, handle updates, or step in when something goes sideways. Ongoing support is optional, not a lock-in.
The person behind the terminal.
I'm Talon (like a claw), an infrastructure and deployment engineer in Montréal. I help small teams keep their software dependable, understandable, and firmly under their control. I hold a DEC in Computer Science Technology from Dawson College. I work in English and French.
I test promising open-source tools in my own homelab before I recommend them. You get the option that fits, not whatever happens to be trending.
See what I've starred on GitHubThe sensible questions to ask before I setup your infrastructure.
It depends. Cloud is quick to start and easy to scale. Self-hosting gives you more control, but someone still has to care for the hardware. I will recommend what fits, including a mix of both when that is the sensible answer.
Most projects use a fixed quote agreed before work starts. Ongoing support uses a monthly retainer. The price depends on scope, complexity, and how much responsibility you want me to take on.
No. You get clear documentation and ownership of the setup. I can stay involved if you want support, but leaving should never require an escape plan.
Yes. A monthly retainer can cover updates, monitoring, backup checks, and incident response. You can also bring me back for one-off work when needed.
Absolutely. I can work with your developers, designers, tools, and existing workflow. I document what changes so your team can take over with confidence.
Both. I work remotely with clients across Québec and beyond. For local Montréal projects, I can visit on-site when it is genuinely useful.
Send me an email with the problem, the setup, or even the messy version of both. I will ask a few questions, then suggest the most useful next step. That is often an audit, but not always.
Tell me about your setup and what you need help with.