Your engineers should be shipping features, not babysitting AWS. We run your infrastructure so they can get back to the product.
Most SaaS teams of ten to fifty people do not have a DevOps hire yet. The developers run the infrastructure in the gaps between features. It works, until the AWS bill creeps past what the workload needs, deploys get slow and scary, and one quiet weekend something breaks that nobody was watching for.
We take that off your plate. We review what you have, fix what matters, and then keep it fast, cheap, and reliable month to month, so your engineers can go back to building the product.
Who this is for
Small SaaS teams on AWS
Roughly ten to fifty people, running on AWS, with developers doing their own DevOps and no full-time DevOps hire yet. The founder or CTO is who we talk to.
Teams in regulated spaces
Health, finance, and anywhere a mistake is expensive and security is not optional. We have worked in those environments, and that experience is part of what you are hiring. We are honest about what is a sensible baseline and what would need a real compliance program.
How it works
Three steps, and you can stop after any of them. Most teams start with the audit because it is low risk and it tells everyone exactly what they are dealing with.
Step 1
AWS Cost and Reliability Audit
$1,499 CAD, fixed
About a week. A full read of your AWS: cost, compute and EKS, deploys, backups, alerting, and security posture. You get a written report with prioritised findings, a 30-day fix list, and a readout call. Credited toward a fix sprint if you go ahead. Low risk, and it is yours to act on with or without us.
Step 2
Fix Sprint
$4,500 to $7,500 CAD
Two to three weeks. We implement the top fixes from the audit: rightsizing and cost cuts, a proper deploy pipeline, alerting and monitoring, backups and recovery. Fixed scope and a fixed price, agreed before we start.
Step 3
Managed DevOps Retainer
$2,999 to $4,999 CAD / month
Ongoing. Releases and EKS upgrades, cost watch, alerting and incident help, and a short monthly report so you always know the state of things. Starter and growth tiers, scoped to your hours and response needs.
The world your product runs on never sleeps, and the quiet, steady work of keeping it healthy is exactly what gets skipped when a small team is heads-down shipping.
What the retainer actually covers
No jargon. Here is the ongoing work, in plain terms.
Keep the bill in check
We watch the AWS spend every month and trim it before it drifts, so you are not overpaying for capacity you do not use.
Ship releases cleanly
Deploys that are boring on purpose, with a pipeline your own team can read and run.
Keep EKS healthy
Cluster and Helm upgrades handled on a schedule, before a version goes end of life and forces a scramble.
Catch problems early
Alerting and monitoring set up so you hear about trouble before your customers do, with playbooks for the common ones.
Protect the data
Backups you have actually tested, and a recovery plan that is written down, not improvised.
A hand on the pager
Business hours plus best-effort on-call for incidents, so a 2am problem is not faced alone.
See trouble before your users do
Most outages are not sudden. A disk fills, a certificate ages out, connections creep toward a limit. We watch the signals that lead to failure and alert on them while there is still time to act, so a would-be outage becomes a short acknowledgement instead of a post-mortem.
Failure imminent ยท Tier 1Example
Disk space on db-primary
Rule
over 90% for 15 min
Now
92%, rising
Held
17 min
Runs out in
about 40 min
Sent to your PagerDuty and on-call channel, with the runbook link attached.
Without it
A customer notices first. Then a scramble to find what broke, at the worst possible time.
With it
Minutes of warning, a named resource, and the runbook. A short ack instead of a post-mortem.
Cost creep and spend spikes
Disk and inode exhaustion
Certificate expiry
Error rate and latency jumps
Memory and connection limits
EKS node and cluster health
Your telemetryPrometheus, Datadog, CloudWatch
Monitoring we runthresholds on cost, capacity and health
Tiered alertseverity, value and runbook
Your on-callPagerDuty, Slack
What we bring
We have run production infrastructure for years, not as a service we added last week. The experience behind this includes cutting cloud bills by around a third, taking deploy times from over forty minutes down to roughly fifteen, operating and upgrading Kubernetes across several clusters in production, and leading credential rotation during a live security incident. We bring that to your account, we do not inflate it, and we are happy to walk through the specifics on a call.
How we work, and what we will not pretend
No lock-in
You keep the AWS account and the pager. When an engagement ends, there is nothing of ours to unpick, and you can stop with notice any time.
No 24/7 heroics we cannot keep
We are a small shop, so we promise business hours plus best-effort on-call, in writing, not an uptime guarantee we would have to fake.
A sensible security baseline
Least-privilege access, secrets handled properly, and the fundamentals right. Not a compliance certification we do not run.
Straight talk
If something is outside what we do well, we say so and scope it out, rather than learn on your budget.
Questions teams ask before they start
We have never worked with you. How do we know this is safe?
Start with the audit. It is read-only: we look, we do not touch. You get a written report with prioritised findings that is yours to act on, with or without us. You see exactly how we work and what we find before you give us anything that can change your infrastructure.
What will it cost?
The audit is $1,499 CAD, fixed, and is credited toward a fix sprint if you go ahead. A fix sprint runs $4,500 to $7,500, and the ongoing retainer is $2,999 to $4,999 per month. Everything is scoped and quoted before we start, so there is no surprise on the invoice.
What access do you need, and can we revoke it?
The audit needs read-only access. For hands-on work we use least-privilege access scoped to the task. You keep the AWS account and can revoke our access at any time. There is nothing of ours you cannot take back.
Do you offer 24/7 on-call?
No, and we will not pretend to. We promise business hours plus best-effort on-call, in writing, not an uptime guarantee we would have to fake. We set up the alerting and the playbooks; your team holds the pager.
What if we want to stop?
No lock-in. You keep the AWS account, the code, and the pager. You can cancel the retainer with notice at any time, and when an engagement ends there is nothing of ours to unpick.
How soon can you start, and how long does the audit take?
The audit takes about a week once we have read-only access. The quickest way to begin is a free 30-minute discovery call, or you can book the audit directly from the contact form.
Start with the audit
One week, a fixed fee, and a written report you can act on no matter what you decide next. It is the easiest way to find out what your infrastructure is really costing you and where it is most likely to break.