From Prinymity
to Forge Vertical:
building without permission.

// Chapter 01 — The Name Nobody Could Pronounce

The name was supposed to be clever. Pri for privacy. Nymity for anonymity. Put them together and you get Prinymity — a word that communicated exactly what I cared about and absolutely nothing else to anyone who saw it for the first time.

"Is it Prince-ymity?" "Prin-ee-mity?" "Prin... what?" I heard every variation. The fumbling became a running joke. But the idea behind the name was serious — I had been obsessed with privacy, anonymity, and how digital systems worked since before I had the vocabulary to describe why. The name was a signal to the three people who would get it immediately, and an interesting puzzle for everyone else.

Prinymity launched around 2018 to 2020. I was building custom PCs, fixing computers, and designing small-business websites using Mobirise — a drag-and-drop builder that was genuinely good for what it was at the time. Cape Town. Self-taught. No formal qualification beyond primary school, and a determination that the absence of a certificate was not the same as the absence of ability.

One of my first real gigs was setting up an i5 Lenovo for an actuary. Full setup — printer, Office installation, the works. But the part I remember most was the optimisation pass at the end: stripping visual effects, setting the CPU performance profile to maximum throughput, minimum at 5% to avoid unnecessary throttling. Not because it was on a checklist. Because it bothered me to hand someone a machine that was not running at what it was capable of. That instinct — extract the actual performance from whatever you are working with — has not changed.

The trades, TEFL, and China

// Chapter 02 — Learning with your hands

Before the websites and the code, there was panel beating. I trained in the collision repair trade at Lance's Panel & Spray — the same family business that would later become one of Forge Vertical's first clients, and the environment that gave birth to the Sure Drive loyalty system and Aurora Repair.

Panel beating is a precision craft that most people do not think of as technical work. It is. Reading a panel for stress lines, understanding how metal moves under heat, knowing the difference between a repair that will hold and one that looks right today and fails in six months — that is diagnostic thinking applied to physical materials. The same way a developer reads a stack trace or a security researcher traces a request through an application. The medium is different. The discipline is the same.

Then there was China. I am TEFL-certified — TQUK Level 5 through The TEFL Academy, 2017 and 2018 — and I went to teach English. It was one of the better decisions I have made. Living and working in an environment where you do not speak the language, where every system works differently, where you have to solve daily problems without the scaffolding you normally rely on — it builds a particular kind of adaptability. You learn to read signals rather than words. You learn that most problems have a workaround if you are willing to look for one rather than wait for permission to find it.

I also spent time as a safety-testing crew member for stunts on Fear Factor India, filmed in Cape Town. The job is exactly what it sounds like: you run the stunt before the talent does, identifying what can go wrong before anyone is in danger. Applied risk assessment. Physical consequence. Not entirely unlike security research, as it turns out.

Lockdown and the pivot that wasn't

// Chapter 03 — When the world stopped, I started

COVID-19 lockdown in South Africa was one of the strictest in the world. For many businesses, it was the end. For Prinymity, it was unexpectedly clarifying. When you cannot go anywhere and most physical commerce stops, the internet becomes the only channel for everything. Businesses that had been ignoring their web presence for years suddenly understood why it mattered. Small operators who had been running on word-of-mouth suddenly needed a searchable, credible digital presence.

I was ready for that moment, in a limited but real way. The work was Mobirise websites, basic SEO, some local directory listings. Nothing architecturally complex. But it was real work solving real problems for real clients, and it taught me the gap between what most small businesses had online and what they actually needed.

Prinymity was hard. Genuinely hard. Clients were difficult to find, the work was inconsistent, and the tools had a ceiling I kept bumping into. I am not going to reframe that as a quiet success — it was a grind that did not produce the results I was hoping for. What it produced instead was something less tangible and more durable: the understanding that I could show up, do the work, and keep going without anyone validating that I should. That is worth something. Not everything, but something.

The limitation that mattered most was technical. Mobirise was the right tool for where I was. It stopped being the right tool before I was ready to admit it. The gap between what clients needed and what I could actually build was widening, and the only way to close it was to learn to build properly — which meant starting over at a lower level and working back up.

Learning to code — properly

// Chapter 04 — HTML to Firebase, one rabbit hole at a time

The self-directed education path is not glamorous to describe. Udemy courses in HTML, CSS, JavaScript, Python, C++ fundamentals. Hours on YouTube. Documentation. Stack Overflow. Building things that broke, understanding why they broke, building them again. No bootcamp, no cohort, no one to ask when something did not make sense except forums and documentation and the willingness to sit with a problem until it gave up its answer.

What changed the rate of progress was the arrival of capable AI tools as genuine development partners. Not as autocomplete. Not as a search engine replacement. As actual collaborators that could reason about architecture, suggest approaches I had not considered, catch errors in logic before they reached production, and help me move at a speed that would otherwise require a team.

I am explicit about this because I think the dishonesty around AI-assisted development is counterproductive. A significant portion of the industry pretends that AI tools are just faster autocomplete, used only for boilerplate, while quietly depending on them for everything. That pretence serves nobody. What I have learned is that directing AI development tools effectively is itself a skill — a real one, with a high ceiling — and that the person who knows what to build, why to build it, and whether the output is correct or not is the person doing the actual work. The AI is a tool. An exceptional one. But a tool.

Aurora, Sure Drive, and the family business problem

// Chapter 05 — Building for a problem you already understand

The best projects I have built came from problems I lived with before I knew how to solve them technically.

Aurora Repair exists because I watched the collision repair industry — the one I trained in — operate on paper, phone calls, and manual quotes for years. Getting from a damaged car to an accurate, trustworthy repair quote takes real time and real back-and-forth between insurers and repairers. I built an AI-driven assessment engine that does OCR licence-plate scanning, pulls real-time parts pricing, and generates tiered repair quotes automatically. Economy parts pathway or OEM — the insurer or repairer sees real options, not one number someone calculated manually.

Sure Drive started as an even simpler idea — a car-repair savings fund for customers of the family business. The complication was regulatory: a straightforward savings product collides with South African insurance law and hire-purchase credit regulation. The solution was to design around the regulation rather than ignore it. A digital token loyalty currency — "Sure Bucks," one rand equals one SB — is structurally a gift and rewards system, not a savings or credit product. Same real value to the customer. Different legal architecture. No exposure. The ability to see that distinction, and then build the system that exploits it correctly, came directly from understanding the business problem before touching a line of code.

The International Panel Shop check-in and release system is the quietest one and in some ways my favourite. A digital intake form with real terms and conditions, electronic signature capture, automated email delivery to both customer and business, and a structured release checklist that closes the liability loop cleanly. It replaced paper. It created permanent records. It removed friction from a daily workflow. Small, complete, and genuinely useful — the kind of internal tool that most agencies would never build because it does not look impressive in a portfolio, but that real businesses need more than they need another landing page.

Security research — the career inside the career

// Chapter 06 — Finding what is broken before someone else does

The privacy obsession that named Prinymity eventually became something more structured. Web application security research.

I work through TryHackMe for structured learning — covering IDOR, SQL injection, XSS, SSRF, command injection, authentication bypass, file inclusion vulnerabilities, content discovery, and subdomain enumeration. And I submit real findings on real production systems via HackerOne, Bugcrowd, and YesWeHack. The findings are real. Client confidentiality is maintained by personal choice, beyond what standard Safe Harbor terms require, because discretion is part of the work.

Security research changes how you build. When you spend time finding the gaps in other people's systems — the state machine assumptions, the trust boundaries, the edge cases that nobody tested — you cannot go back to building without that perspective. The Firestore security rules in TripSpace Global were independently designed, audited, and hardened because I knew exactly what a poorly written security rule looks like in production. I found one myself: a rule that restricted a sensitive collection to admin-only access looked correct on paper but accidentally blocked the very check needed to grant a Director Candidate their own permissions. The rule never accounted for someone needing to read their own record. I diagnosed it, traced it to the exact line, corrected it. Not luck. Method.

TripSpace Global — the product that is the mission

// Chapter 07 — Building what the market was missing

TripSpace Global did not begin as a grand vision. It began as a question: why does every accommodation booking platform take a percentage of every booking, indefinitely, from people who own the property, do the work, and carry all the operational risk?

The answer — platforms provide distribution, technology, and trust infrastructure — is real and worth paying for. The problem is that no meaningful alternative existed. Commission or nothing. Platform terms or no guests. That is not a partnership. That is a dependency.

So I built the alternative. React, TypeScript, 30+ Firebase Cloud Functions, PayFast and PayPal payment integration, real-time messaging between hosts and travellers, a multi-tier affiliate and partner revenue-share system, Firestore security rules I audited myself, a host verification programme, a QR check-in system, and tools I will get to in a moment. All solo. All production. All live.

As of July 2026, TripSpace Global has one host customer. I am saying that plainly because I think humility at the start of something is more credible than inflated claims. One real person chose to list their property on a platform with no existing audience, no brand recognition, and no track record — because the proposition made sense to them. That is the right kind of first customer. The web platform is live. The app is live on the Amazon App Store. Google Play Store testing is planned but has not yet commenced — and anyone who wants early access can opt in directly at tripspaceglobal.com/login to receive the download link. I am building the foundation, not pretending the house is already finished.

What TripSpace does that no other platform does

To my knowledge — and I have looked — TripSpace Global is the first accommodation marketplace that includes meaningful tools built specifically for travellers, not just hosts. I say "to my knowledge" deliberately. If I am wrong, I would like to know. But I have not found another platform that does what the traveller side of TripSpace does.

TripGuard is Aurora Repair adapted for travellers. The same AI-driven vehicle damage assessment engine I built for the collision repair industry — OCR, real-time parts pricing, tiered repair estimates — wrapped as a free tool for anyone who rents a car. Before you return a rental, photograph it. TripGuard analyses the images, identifies every panel, generates a professional damage report with local market repair pricing in 25+ countries, and produces a dispute letter if the rental company tries to overcharge. Free for every registered TripSpace user. No other booking platform offers this.

DeviceGuard is a GPS phone tracker for travellers. If your phone is lost or stolen anywhere in the world, you can ping its location from any internet-connected device. User-activated only. GDPR compliant. It is a paid feature — modest monthly subscription — but it exists within a booking platform, which is where travellers actually are when they need it.

Aria is the one I am most proud of, and the one that was hardest to build correctly. She is not a chatbot. She is a travel companion powered by Google Gemini 2.5 Flash with real-time Google Search and Google Places integration. The distinction matters: a chatbot gives you pre-scripted responses. Aria thinks.

A traveller in Rome who thinks they are having a medical emergency can open Aria and say exactly that. Aria will give them the ambulance number for Italy, find the nearest hospital using their GPS location via Google Places, and display a tap-to-call link. One tap. That is not a feature for a demo. That is a feature for the moment when someone is scared and alone in a country where they do not know the emergency number.

She also handles the mundane. Where should I eat lunch? What time does this museum close? Can you translate this sign? What is the weather this weekend? She uses voice input — you can speak to her when typing is not practical — and she navigates the platform itself if you do not know where to find something.

For hosts, there is Aria Intel. Aria monitors destination demand, competitor pricing in the area, local events, and school holiday calendars. She will flag when a host's price is out of step with market conditions and suggest an adjustment. She does not enforce anything. She advises. The host makes the call. But the insight is there, and it is the kind of market intelligence that boutique hotels used to pay a revenue management consultant to provide.

Forge Vertical — Prinymity with a new face

// Chapter 08 — Where it all connects

Forge Vertical is not a rebrand. It is a recognition that what I was doing had always been the same thing, and it deserved a name that said so clearly.

Prinymity fixed computers and built Mobirise sites. Forge Vertical architects full-stack platforms, builds AI integrations, deploys GEO content stacks, and conducts security research on enterprise infrastructure. The tools are different. The instinct — find what is not working, understand why, build something better — has not changed since the i5 Lenovo setup in someone's home office in Cape Town.

The Prinymity domain still carries real value. Years of clean indexing, genuine history, no spam associations. When search engines and AI models encounter Prinymity in backlinks pointing to Forge Vertical, they read continuity — the same entity, developed over time, not a new brand with no history. That is a real asset and I intend to use it properly.

Today I am also applying to work within established technical teams. Not because Forge Vertical is not working — it is — but because I know the difference between building alone and building alongside experienced engineers who will correct me, challenge my assumptions, and show me things I cannot find in documentation. The self-directed path has limits. I know where some of those limits are. I want to find the rest of them.

The CV and portfolio attached to this article are the honest version of where I stand. No inflation. No projects I cannot demo. No claimed experience I cannot explain in technical detail. What is there is what I built, what I learned, and what I am still figuring out.

That sentence is in my CV because I believe it is the most honest thing a self-taught developer can say when they are ready to stop building alone. Most people in that position either oversell to compensate for the credential gap, or undersell because the credential gap makes them doubt work that is actually good. I am trying to do neither.

The work is real. The learning is ongoing. The name has changed. The obsession has not.