North America's largest home inspection franchise came to Armakuni for a Flexible Engineering POD embedded alongside the client's developers. Initial scope is an emergency infrastructure migration from a reseller-owned AWS tenant into a Pillar To Post-owned AWS account. Ongoing scope covers DevOps, infrastructure-as-code, and a planned EC2 to ECS modernization..
The challenge
Pillar To Post came to Armakuni on a hard migration deadline. The previous AWS partner had stalled because of gaps in DevOps experience. Armakuni's senior Solutions Architects engaged on the first calls, closed the engagement inside two days, and mobilized a Flexible Engineering POD within two weeks. The POD then delivered a working 8 to 10 week migration. The work has since expanded into an ongoing POD running alongside client developers. Terraform adoption and an EC2 to ECS modernization are scoped for the next phase, on the same retainer.
Scale: Approximately 600 GB of production PostgreSQL, plus EC2 compute, RabbitMQ messaging, Redis cache, and S3 storage. The entire stack ran inside a third-party reseller's AWS account before the migration. The platform supports the largest home inspection franchise in North America..
What we built
Armakuni delivered a Flexible Engineering POD embedded alongside the client's developers. Initial scope is an emergency infrastructure migration from a reseller-owned AWS tenant into a Pillar To Post-owned AWS account. Ongoing scope covers DevOps, infrastructure-as-code, and a planned EC2 to ECS modernization. The engagement ran as two fixed-scope SOWs. Flexible Engineering POD Delivery SOW (effective 29 October 2025) covers the end-to-end migration from the reseller's shared AWS account into a Pillar To Post-owned AWS account. Flexible Engineering POD January SOW (dated 24 November 2025) covers 80 hours per month of retained engineering capacity, plus additional on-call support through the January stabilization window.
The outcomes
8 measurable outcomes shipped across the engagement. The ones that moved the business the most:
Engagement closed within two days of first contact.. Pillar To Post was on a hard migration deadline after losing reseller support. Armakuni's senior Solutions Architects engaged immediately, produced a workable plan, and got the SOW over the line inside 48 hours. The migration clock could start while other options were still in…
Flexible Engineering POD operational inside two weeks.. The engagement moved from first call to a mobilized, senior-led POD in under fourteen days. That speed is the difference between hitting the cutover window and missing it.
Production workload migrated out of a shared reseller account into Pillar To Post's own AWS environment.. Approximately 600 GB of PostgreSQL, plus EC2, RabbitMQ, Redis, and S3, now run inside an account Pillar To Post controls. The business is no longer operating on infrastructure it does not own and cannot directly observe.
A stalled migration program restarted and put on a realistic 8 to 10 week path.. Before Armakuni engaged, no executable plan existed. After Armakuni engaged, the CTO had a signed SOW, a dated plan, and a mobilized senior POD inside the first two weeks.
Security posture preserved through cutover.. ALB, WAF, and ACM were rebuilt in the new account before cutover. Pillar To Post never operated below its existing compliance baseline during the move.
DevOps capability now embedded in the client team.. Pillar To Post's developers now work alongside an Armakuni POD covering Application, CloudOps, Data, and Solution Architecture. The DevOps gap that stopped the previous program is closed. The capability is being transferred into the company, not held outside it.
EC2 to ECS migration scoped and staged so compute cost bends down over the next year.. Armakuni has a defined path from the lift-and-shift runtime to containerized workloads on Amazon ECS. The compute cost curve Pillar To Post owns from cutover onward is designed to decrease, not plateau.
Armakuni established as the long-term engineering partner inside the account.. The engagement began as an emergency cutover and became an ongoing Flexible Engineering POD. Pillar To Post's CTO is the primary decision maker. Further modernization work inside the account now pulls against the existing retainer rather than through a new procurement cycle.
Built on AWS
The production environment runs on 13 first-party AWS services. Delivered under our AWS DevOps Consulting Competency. Migration and Modernization Consulting Competency. competency.
What's next
EC2 to ECS migration to lower compute cost and modernize the runtime. Expansion of Terraform coverage across the new account. Continuation of the embedded Flexible Engineering POD alongside Pillar To Post's developers. Further modernization is pulled against the same retainer.