Platforms · AWS Cloud Engineering
We design, build and run Amazon Web Services environments that stay understandable: clear architecture, infrastructure as code, Canadian data residency where it matters, and costs you can explain to a finance team.
You own the code and IP Weekly demos Reply within one business day
$oldevs deploy --env production
✓Build passed · 212 tests · 0 warnings
✓Migrations applied · postgres 16
✓API v2 healthy · 142ms p95
→Rolling out to 3 regions…
OlDevs is a full-stack technology studio in Vancouver, British Columbia that designs, builds and operates workloads on Amazon Web Services.Our engineers work across compute options such as EC2, ECS with Fargate and Lambda, storage and databases including S3, RDS and Aurora, delivery through CloudFront and Route 53, and access control with IAM. Every environment is defined in code with Terraform or the AWS CDK, monitored, backed up and tested for recovery, and it can stay in the Canadian regions in Montreal or Calgary where residency matters. Clients own all code, accounts and IP, and one accountable team stays with the work from architecture through migration and ongoing operation.
Key facts
AWS platform expertise
We map your workload to the right AWS building blocks: EC2 or containers on ECS with Fargate, Lambda for event driven work, S3 for storage, RDS or Aurora for relational data, and SQS or SNS for queues and fan out. Trade offs are written down, not assumed.
Every environment is defined in Terraform or the AWS CDK and changed through pull requests, so development, staging and production stay comparable. Rebuilding an account becomes a pipeline run rather than a memory exercise, and configuration drift is caught early.
When residency matters, we place data and processing in Canada Central in Montreal or Canada West in Calgary, document which services are in scope, and keep backups and logs in region as well. Cross border traffic becomes a decision you make, not a surprise.
We tag resources consistently, set up AWS Budgets and Cost Explorer views by team or product, right size instances and storage classes, and use lifecycle rules and autoscaling so you pay for what you actually use. Reports reach finance in plain language.
CloudWatch metrics, logs and alarms are built around the things that matter to your users, with tracing where it earns its place. Backups are scheduled and, more importantly, restored on a schedule, so recovery times are measured rather than hoped for.
IAM roles follow least privilege, secrets live in Secrets Manager or Parameter Store, and networks are segmented with security groups reviewed as code. For moves from on premises or another cloud, we plan the cut over, the rollback and the quiet weekend.
Process
Assessment
We review your current environment, applications, data and constraints, including residency and compliance questions, and agree what a good outcome looks like.
Architecture and plan
You get a target architecture, the cost drivers explained in structural terms, a build or migration sequence and a risk list, all written in plain language.
Build in code
Networking, identity, compute, data stores and pipelines are provisioned with Terraform or the AWS CDK, with a working demo every week so nothing is a surprise.
Migrate and verify
Workloads move in planned waves with rehearsals and a tested rollback, then performance, backups and monitoring are verified after each cut over.
Operate and improve
Once live, we tune cost and performance, run restore tests, patch and review security posture, and keep runbooks current for your team.
How we work
We look at traffic patterns, data volumes, compliance needs and the team who will run the system before naming a single AWS service.
Managed options such as RDS, Aurora, ECS with Fargate and SQS reduce the operational surface your team carries. We run something ourselves only when there is a reason to.
Changes land through Terraform or the AWS CDK in version control, so every environment has a history, a reviewer and a way to be recreated from scratch.
IAM roles are scoped per service and per environment, human access is time limited and audited, and long lived access keys are removed rather than tolerated.
Cost and performance work starts with real numbers from CloudWatch and Cost Explorer, so effort goes where it actually changes the bill or the experience.
You own the accounts, the code, the pipelines and the runbooks. We document how the environment is operated and train the people who will operate it.
Who it's for
Several applications, existing vendors and an internal platform team. We fit into your change process, security review and account structure rather than asking you to work around ours.
Public accountability, procurement steps and residency questions. We document where data lives, who can reach it and how long it is kept, and build interfaces to WCAG 2.2 AA.
Many locations on shared infrastructure. We build environments with per location data separation, central reporting and a deployment process that behaves the same every time.
Small teams that need to move quickly without painting themselves into a corner. We start with a simple footprint that is easy to run and can grow when demand does.
1 business day
Reply to every enquiry
Weekly
Working demo during builds
2 regions
Canadian AWS regions available
FAQ
Yes. AWS operates two Canadian regions, Canada Central in Montreal and Canada West in Calgary, and we can place compute, storage, databases, backups and logs in them. We document which services sit in region, where any cross border traffic occurs, and what your retention and access rules are, so your privacy officer has a clear answer.
Both, and we choose per client rather than per fashion. Terraform suits mixed estates and teams that already know it. The AWS CDK suits teams that prefer TypeScript or Python and expect to stay on AWS. Whichever we use, the code lives in your repository, runs in your pipeline and is reviewed like application code.
We start with visibility: consistent tagging, Cost Explorer views by team or product, and AWS Budgets with alerts. Then we act on what the data shows, right sizing compute, choosing appropriate S3 storage classes and lifecycle rules, scaling non production down out of hours and removing orphaned resources. Savings plans and reserved capacity are considered once usage is stable.
Yes. We begin with an inventory of applications, data and dependencies, then choose per workload between rehosting, replatforming onto managed services such as RDS or Aurora, and rebuilding. Moves happen in waves with rehearsals, a tested rollback and verification of performance, backups and monitoring after each cut over.
We do not make partner, certification or award claims on this page. What we can say is that our engineers work on AWS every week across compute, storage, data, networking and identity, and that you can talk with the people who would actually do your work before you commit to anything.
That depends on the support arrangement we agree. At a minimum we set up CloudWatch alarms and notification routing so the right person learns about a problem before your customers do, and we write runbooks for the failure modes we can predict. Where you want us on call, we define severity levels, response expectations and escalation in writing.
Yes. The studio is in Vancouver, British Columbia, and we work with clients across Canada remotely, with video calls in your time zone and on-site visits when the work calls for it. Discovery, architecture review and handover all work well over video, and we can support documentation in English and French.
Let’s connect
Tell us what you’re building. We’ll reply within one business day with next steps and a tailored quote — no obligation.