About
Issaber is an AWS practice for engineering teams running real production workloads. We design, build and tune cloud infrastructure, without making anyone's life harder in the process.
Background
Our work is led by an AWS Certified Solutions Architect with more than five years of hands-on experience building and operating production workloads for a B2B SaaS company. Not advisory experience. The kind where you own the infrastructure that breaks when nobody is watching it, and where the AWS bill is high enough that a percentage point matters.
We still build. Alongside client work we design and run a multi-tenant SaaS platform on AWS end to end: containers, managed databases, queues, email, the deployment pipeline, all of it defined in code. That matters here for one reason. When we recommend something to you, we have usually had to live with the consequences of the same decision ourselves.
A lot of the work is unglamorous. Turning off what does not need to be on. Moving workloads onto services that do the job for less. Writing down an environment so it can be rebuilt rather than remembered. Adding the guardrail that stops a bad deploy at 2am. We publish nothing on conference stages. We make systems cheaper, steadier and easier to reason about.
How we work
- Read-only first. On an audit we work from a read-only IAM role until trust is built. Your production stays untouched.
- Engineer-first, not a marketing shop. No synergy decks. Specific findings, dollar figures, and the order to do them in.
- Risk before reward. Every recommendation carries a risk rating. We will never push you into something that could break a customer experience.
- Written down, not in anyone's head. Infrastructure we build is defined in code and documented, so the day we stop working together costs you nothing.
- Plain English. Reports are written for engineering managers and CTOs, not for consultants.
Where we are
Canada. We work remotely with clients across North America and Europe. Most calls happen in the client's morning, which is our evening, and that overlap usually works out fine. For Canadian clients with data residency requirements, we build in Canadian regions by default. More on AWS security and Canadian data residency.