Fractional CTO & Managed Cloud

Own your infrastructure. I'll run it.

Technical leadership and hands-on server management for small businesses that run their own website, app, or software, without hiring a full-time CTO.

Monthly retainer. Accounts in your name. No lock-in.

You have technology. Nobody owns it.

"An agency set it up and moved on."

Your servers run, but nobody on your side knows how, what they cost, or what happens if something breaks.

"My developer ships, but nobody checks."

Changes go live without review. You can't tell whether the work is right until a customer finds the bug.

"The cloud bill is a mystery."

Every month it's a number you can't explain, for services you didn't know you had.

"I can't afford a full-time CTO."

You need senior technical judgment a few hours a week, not a $200K hire.

Your technical lead and security team, for a set number of hours a month.

Security, kept current

Firewall rules that stop bots and password-guessing, patched servers, locked-down access with MFA, rotated credentials, and alerts when something looks wrong.

Servers, run properly

Updates, monitoring, and fixing what breaks. The server-level work your web developer can't or shouldn't touch.

Backups you've tested

Automatic backups, checked every week, and restores we've actually practiced, so a bad day stays a bad hour.

A faster site

I find what's slowing pages down, from caching to oversized servers, and fix it with numbers before and after.

A gate before anything ships

I review your developers' changes before they go live and set the technical priorities, so the work matches what the business needs.

Costs you understand

I find idle servers, forgotten storage, and oversized plans, cut what you don't need, and explain the bill in plain words.

Your accounts. Your data. Written down.

Everything runs on accounts in your name. Your setup is documented and written as code, so it can be rebuilt, audited, or handed to someone else. If we ever part ways, you keep everything and lose nothing.

You own

  • AWS account
  • Domain and DNS
  • Code on GitHub
  • All your data

I run

  • Servers and deploys
  • Backups and security
  • Code review
  • Monitoring and fixes

You always get

  • Documentation
  • Setup written as code
  • A clean handoff, anytime

You always know what you're paying for.

Every week you get a scorecard of how your systems ran, plus a short, plain-English note: what got done, hours used so far, and what's next. If a month looks like it will run over, you hear about it before it happens.

Running real businesses' infrastructure today.

ONGOING RETAINER

Little Sponges

An education company serving school districts, on its own AWS setup built by an agency that had moved on.

  • Took over the servers from the agency, with a clean handover of every account and key
  • Tuned the firewall to block bots and password-guessing without blocking whole classrooms
  • Server caching fix: page times from about 0.8 s to 0.2 s
  • Backups with tested restores, alarms, and a weekly ops scorecard
  • Prepared the platform for a large school district's security review
  • Rewrote the agency's outdated Terraform: the entire setup is now in code, reviewable and repeatable
  • Wrote automated browser tests (Playwright) that check the site's key flows

MY OWN STUDIO

Mindful Owl Yoga

My yoga studio in Atlanta. I moved its website onto the studio's own AWS setup.

  • Security set up from day one, on accounts the studio owns
  • Same security baseline on my Forma Consulting site
  • Same playbook I use for clients

SOFTWARE I BUILT

Forma Studio

My open-source studio management software. The live demo runs entirely on AWS.

  • Load balancer, app servers, and a managed AWS database
  • Setup written as code, so a new studio can be stood up quickly
  • See Forma Studio →

What I run day to day.

Hosting and data

  • AWS EC2 and ECS containers
  • Application Load Balancer
  • Aurora and RDS databases
  • ElastiCache (Redis)
  • S3 and EFS storage
  • Route 53 DNS and certificates

Security and reliability

  • AWS WAF: rate limits, managed rule sets, IP blocking
  • IAM least-privilege access and MFA
  • Credential rotation
  • GuardDuty and Inspector
  • AWS Backup with tested restores
  • CloudWatch metrics and alarms

How changes ship

  • Terraform (infrastructure as code)
  • CI/CD pipelines with a manual production gate
  • Code review on GitHub and Bitbucket
  • Automated browser testing (Playwright)
  • WordPress and custom apps

Start with what you have.

01

Intro call

We talk through what you run, who touches it, and what keeps you up at night. Free, 30 minutes.

02

First month: take stock

I map every account, server, and bill, fix access and backups, and write it all down. You see exactly what you have.

03

Ongoing: run and improve

A monthly block of hours for upkeep, reviews, and improvements, with a Monday update every week.

Monthly retainer

A set number of hours each month, sized to what you run. Hours beyond the plan are billed at the same rate, and you're told before a month runs over.

Do I need a CTO if I have a developer?

Usually yes. Developers build. Someone still has to review the work, run the servers, and make the calls.

Do you only work with AWS?

AWS is home base. If you're elsewhere, we'll talk about whether to stay or move.

Am I locked in?

No. Your accounts, your code, your documentation. Cancel with notice and you keep everything.

Tell me what you're running.

A website on its own server, an app, a setup an agency left behind? Give me the short version and I'll reply within one business day to set up a call.

No long-term contracts. You keep your accounts.