full-stack, one developer

Every role a dev team splits up. Handled by one person.

I design, build, and deploy production web applications end to end — frontend, backend, and the cloud infrastructure underneath. No handoffs, no account managers. You talk to the person writing the code.

Book a consultation See my services
A typical teamonemanstack
Frontend DevAngular / React
Backend Dev.NET / APIs
DevOpsAzure / Docker
QATesting
Project ManagerDelivery
Msizi Shangase
All of the above

Normally five roles across five people — frontend, backend, DevOps, QA, and project management. On this project, it's one person: me.

services

Four things clients usually need. I cover all four.

01 Custom web applications

Full applications built from scratch — from database design to the interface users actually touch. ASP.NET, Angular, and TypeScript form the core.

02 Cloud & deployment

Getting an application onto real infrastructure and keeping it running — Azure hosting, Docker containers, CI basics, and sane environment setup.

03 APIs & integrations

RESTful APIs that connect your systems to the tools you already use — payment providers, third-party services, or internal data sources.

04 Modernizing legacy systems

Old system slowing the business down? I assess what's there, and rebuild or refactor it into something maintainable — without a full stop on operations.

stack

The tools behind the work.

Frontend

Angular
TypeScript
JavaScript

Backend

C#
.NET
ASP.NET MVC
REST APIs

Cloud & Infra

Azure
Docker

Tooling

Git
SQL Server

AI Tools

Claude
ChatGPT
Gemini
how i work

A one-person shop still needs a process.

~/onemanstack/process.log
01Discovery

// We talk through what the application needs to do, who it's for, and what "done" looks like — before any code gets written.

02Build

// Development happens in visible stages, not one long silence. You see progress as it's made, not just at the end.

03Deploy

// The application goes live on proper cloud infrastructure, configured to actually stay up.

04Support

// Launch isn't the finish line. I stay reachable for fixes, changes, and the next phase of the build.

about
~/onemanstack/about.md

#How onemanstack came to be

onemanstack didn't start with a business plan. It started with a layoff.

I'd always wanted to build something of my own, but went the conventional route first — a software engineering job straight out of varsity. It didn't stay conventional for long: barely out of school, I was carrying responsibilities closer to a senior engineer's than a junior's. It was a steep, fast education.

"I had four-plus years of real, hands-on engineering behind me and, honestly, nothing left to lose."

When that job ended, so did my reason for waiting. So I stopped putting off the idea and started onemanstack instead.

Right now, "one man" is literal — I handle every layer of the stack myself. That's not a permanent philosophy, just where things are today; the plan is to grow into a team as the work grows. Until then, every client gets my direct attention on every part of the build.

---
details.yaml
location: Pretoria, South Africa
experience: 4+ years in software engineering
education: Diploma in ICT — Applications Development, DUT
focus: Full-stack web applications & cloud deployment
contact

Book a consultation.

Tell me a bit about what you're building. I typically reply within a day.

hello@onemanstack.co.za