Cloud migrations · Est. 2026 · Canada

Clean cutover.
Legacy to cloud, in
one defined window.

Hardcut runs single-window migrations one workload at a time. Fixed price, fixed cutover date. Larger estates ship as a sequence of clean cuts, never an 18-month parallel run. We spend the weeks so your weekend is boring.

Solo specialist · Toronto, Canada Discovery calls open · scoping the first Hardcut cut
The Hardcut Method

Four phases.
One defined window.

01 Discovery Week 1–2 Infra inventory · risk register
02 Infrastructure as code Week 2–6 Terraform · Ansible · pipelines
03 Dry runs Week 6–8 Rehearsal report · rollback drilled
04 Cutover one night
  1. 01·Week 1–2
    Discovery
    Infra inventory · risk register
  2. 02·Week 2–6
    Infrastructure as code
    Terraform · Ansible · pipelines
  3. 03·Week 6–8
    Dry runs
    Rehearsal report · rollback drilled
  4. 04·one night
    Cutover
    Go-live · receipts

The full method →

Who runs it

One specialist. Run solo from Toronto.

Marthinus Meyer (mar-TEE-nus) Read more →

In production 2012 Config as code 2015 Containers 2018 Infra as code Track record 4,000+ services migrated zero data lost
Ways to work together

Fixed scope.
Named price.

  • Migration 4–8 weeks · fixed cutover

    One workload to cloud, one window.

    From $25K
  • Modernization Sprint 1–2 weeks · one named outcome

    One outcome. One window.

    From $8K
  • Post-cutover hypercare 30–90 days · banded by hours

    Stabilize, then hand off.

    From $3K

The full services →

Security advisories · what I'm watching

Public under fire.

A running chronology of security findings any infrastructure team has to act on. The three most recent below; 20 in order.

  1. 2026-06-01 P2 Meta AI support bot hijacked to reset Instagram passwords
  2. 2026-05-25 P1 Gitea container registries exposing private images without auth
  3. 2026-05-20 P1 GitHub-internal repos exfiltrated via poisoned VS Code extension

If you're staring at a migration you've been putting off, let's talk.

Thirty-minute call by default. No deck, no sales engineer, no follow-up sequence. Either there's a Hardcut-shaped engagement here or there isn't, and you'll know which one by the end of the call.