We Started Because Banks Kept Failing People

Back in 2019, Cleo Hartwell was locked out of her own account for three days. No warning. Just a system glitch that froze her rent payment mid-transfer. That frustration sparked something. What if banking security could actually work for people instead of creating new problems?

Born From Real Banking Frustration

Cleo wasn't a cybersecurity expert when she started ivakearexmorivo. She was a frustrated customer who'd watched her mother lose access to her savings account twice in one year because of authentication issues.

The breaking point came when a friend's business nearly collapsed after their banking portal was compromised. The bank's solution? Change your password and wait. That's when Cleo realized something had to change.

She spent six months talking to small business owners across Tasmania. Same story everywhere. Banking security felt like it was designed to punish customers for trying to protect themselves. Too many steps. Too many lockouts. And when something went wrong, you were on your own.

Early days of ivakearexmorivo development workspace in Hobart

The Team That Gets It

We're not lecturing from some ivory tower. Everyone here has dealt with banking headaches personally. That's what makes our teaching different.

Cleo Hartwell teaching digital banking security concepts

Cleo Hartwell

Founder & Lead Instructor

Started ivakearexmorivo after watching her own family struggle with banking security issues. Cleo's approach is simple: if your grandmother can't use it safely, the system is broken. She teaches from real scenarios, not textbook theory.

Vera Quinby mentoring students in secure banking practices

Vera Quinby

Security Architecture Mentor

Vera spent twelve years building security systems for regional banks before joining ivakearexmorivo. She knows where systems actually fail because she's fixed them at 3am. Her mentoring style focuses on asking the right questions before implementing solutions.

How We Actually Teach This Stuff

Our method isn't revolutionary. It's just honest. We start with the problems people actually face, then build understanding from there.

1

Real Scenarios First

Every session starts with an actual security incident. We dissect what went wrong and why. No theory until you understand the problem.

2

Build Your Solution

You design the fix. We guide, question, and push back when needed. The best learning happens when you're defending your own decisions.

3

Test Under Pressure

Your solution faces simulated attacks and user testing. If it breaks, we figure out why together. That's where the real growth happens.

People Who Turned Things Around

These aren't success stories. They're just honest accounts of what happened when people committed to understanding banking security properly.

Modern banking interface development workspace

Marcus Riley

Before ivakearexmorivo

Marcus was managing IT for a small accounting firm. They'd been breached twice in eighteen months. Clients were leaving. He was drowning in compliance requirements he didn't fully understand.

After Nine Months

He rebuilt their entire authentication system from scratch. Not perfect, but functional and actually secure. More importantly, he can now explain to non-technical staff why each security measure exists. The firm hasn't had an incident since mid-2024.

Secure payment processing system implementation

Thea Pemberton

The Starting Point

Thea ran a retail business that relied on digital payments. She knew nothing about security architecture and felt completely lost whenever her payment processor had issues. It was costing her sleep and money.

Current Situation

She's not a security expert now. But she understands her systems well enough to spot problems early and communicate effectively with technical support. She's also consulting for two other local businesses on their payment security setup.

Trying to Figure Out If This Fits?

People ask us the same questions. Here's what usually helps them decide.

Do I need technical experience to start?

No. But you need to be comfortable with technology in general. If setting up a new phone or troubleshooting your router feels completely overwhelming, you might want to build those foundational skills first. Our autumn 2025 intake includes people from retail, healthcare, and hospitality backgrounds.

What if I'm already working in banking or finance?

Even better. You'll recognize the problems immediately. Most of our experienced students say the program helped them understand why certain security measures exist, which makes their current work easier. Our next cohort starts September 2025.

How much time does this actually take?

Plan for twelve to fifteen hours weekly. Some weeks are lighter, some heavier. The real time commitment comes from working through your project. You'll need blocks of uninterrupted time to think through problems properly.

Will this guarantee me a job in banking security?

We can't promise that. What we can do is help you build genuine skills and understanding. Some students use this to transition careers. Others apply it to their current roles. A few have started consulting. The outcomes vary because people's situations vary.

Talk About Your Situation