Work most engineers walk away from.
Real work. Real outcomes. Real engineering decisions.
The case studies on this page document the kind of infrastructure work most IT providers won't take on — and the kind we built Edos Solutions to handle.
Each one tells the same basic story: a Sydney business hits a problem that goes deeper than their current IT provider can solve. Sometimes it's a critical system Microsoft's own tooling can't fix. Sometimes it's a mail server that's been quietly degrading for years. Sometimes it's a security gap nobody's noticed because nobody's been looking. We get the call, we diagnose what's actually going on, and we fix it properly — not with a workaround that buys six months, but with a real engineering solution that holds.
These aren't marketing-led case studies. We don't write up jobs that went smoothly because clients asked for new servers. We write up the jobs where something was genuinely broken, where standard tooling had failed, and where specialist engineering decisions made the difference between recovery and rebuild.
What you'll find here
Each case study covers three things in plain English:
- The problem. What the client was facing, what had been tried before, and why the standard fix didn't work.
- What we did. The actual technical work — including the unglamorous parts most providers leave out of their write-ups.
- The result. What's running now, what's been hardened, and what we put in place to stop the same problem coming back.
What you won't find here
We don't publish client names or branded testimonials unless our clients explicitly want to be named. Most don't — the kind of businesses that hire us to fix infrastructure failures generally don't want those failures publicised. Every case study on this page is anonymised by default, with enough technical detail that other engineers can verify the work was real.
- Mail infrastructure August 2025
Production Mail Recovery
Edos's own production mail environment hit a critical upgrade failure where vendor tooling couldn't complete a required security update. Manual root-cause diagnosis, hardening and ongoing monitoring — recovered without rebuild, zero downtime to mail flow.
Read the full case - Email deliverability October 2025
SPF Record Over Lookup Limit Causing Intermittent Delivery Failures
Outbound email failing intermittently to specific recipients with no obvious pattern. Audit revealed the SPF record had accumulated 14 DNS lookups through nested includes — well over the RFC limit. Restructured the record; delivery failures resolved within 24 hours of propagation.
Read the full case - Email deliverability November 2025
Exchange Online DKIM Signing Stopped After Microsoft Licence Migration
DMARC aggregate reports showed DKIM alignment dropping to zero three weeks after a Microsoft 365 licence migration. Mail was delivering but completely unprotected. DKIM keys regenerated, monitoring added.
Read the full case
Want to talk about your environment?
If you've got a problem that sounds like the kind we'd be the right team for — or one your current provider has stopped returning calls about — we'd rather have a real conversation than guess.