TMP is where I share the software and websites I make. Have a look around, or drop me a message if you’re curious about something.
A look at the projects I build, run and keep tinkering with.
I build TMPx Triumphant OS for desktops. TMP EdgeDev is my newer browser workspace for writing, running and testing code.
Central Server is the backbone I wrote for everything else — logins, routing, real-time sync and DDoS protection across 6 nodes.
TMP Collectables is my authentication and market-intelligence service for rare trading cards and vintage camera gear.
The SMP Server is my multiplayer world — social clusters, leaderboards and live events, run by me.
TMP Merch is the shop: physical and digital goods with live inventory, set up and managed by me.
CyberNexus API is the one data interface that lets my platforms (and other people's) talk to each other.
I didn't set out to build 49 platforms. I built one thing I needed, then another, and because I kept everything on one shared foundation, each new project got faster to make than the last.
Design, front end, back end, servers, payments, support — it's all me. That means I know exactly how every piece works, and when something breaks I know where to look.
Every platform shares the same account system, the same Central Server and the same status layer. Build the hard parts once, reuse them everywhere. That's how one developer keeps 49 things alive.
I can try a small idea quickly, then improve it as I use it and hear what people think.
I'd rather get something real in front of people and fix it from feedback than polish it in private for months.
I host, monitor and maintain every platform myself, so nothing gets built and then forgotten.
The status page is public and current. If something's down or delayed, you'll see it.
One login, one API, one status layer. Use one platform and the rest are already set up for you.
I use automation heavily — it's a big part of how one person can build and maintain this much.
Message me through the forum or contact page and you're talking to the person who actually wrote the code.
Most of this is stuff I like making. The paid projects help pay for hosting and the time I spend maintaining them.
When I charge for a project, you can find its price and what’s included on its own page.
I bought out Triumphant LTD, so Triumphant OS and everything under that name is fully owned and run by me.
Not sure where to begin? These are the four I'd point a friend to first.
My biggest project: a desktop OS that quietly tunes itself to run smoothly on minimal RAM. Available now.
Authentication for trading cards and vintage optics, used across the big marketplaces.
Check what's up, what's under maintenance and how everything's been performing.
Ask a question, report a bug or just say hi — I read everything.
Wondering if something is down?
I started TMP to share the things I build. I still write the software, keep it running and answer messages myself.
I build the thing I wish already existed, then I keep it running.How TMP works
I started TMP in 2023. One of my early projects was TMP Collectables, which grew out of my interest in rare trading cards and vintage cameras. TMP EdgeDev came later. It’s a browser-based coding workspace for writing, running and testing code.
Every project after that got easier, because I stopped starting from zero. I built one account system, one server backbone and one status page, and plugged each new idea into them. That's how a single person ends up with 49 platforms without losing track of any of them.
Along the way I also bought out Triumphant LTD, so the OS that carries its name is now fully mine too.
I design it, write it, host it, fix it at odd hours and answer the messages. It's a lot, but it also means every decision on this site was made by someone who actually uses it.
It's the project I'm proudest of, and it's no longer a plan or a countdown. People have been using it for months. It's a desktop operating system that quietly optimises itself in the background so it runs smoothly on minimal RAM, and I've been shipping updates, fixing what people report and making it better the whole time.
Smart automation runs quietly in the background, tuning the OS and your system. There's nothing to open, talk to or manage.
It's designed to run smoothly on modest hardware. I recommend 4GB RAM, and 128GB of storage is the very minimum.
I keep improving it based on what people tell me, and the status page shows how it's doing.
It runs on the same identity as the rest of TMP, so you don't start over for each thing.
That's the goal I set at the start, and I'm still working toward it with every release.
Some projects are free. Where I charge, it helps cover hosting and the time I spend keeping things running.
I list the price on each paid project so you can decide if it suits you.
Triumphant is now fully mine. It's the name behind Triumphant OS, and owning it outright means the OS and everything around it answers to me, not to anyone else's plans.
It's the same approach as everything else here: I'd rather own the thing, run it myself and keep it fair.
If something's down, the status page says so. If something's late, I tell you.
I'd rather something work every day than look impressive once.
Your account, your data and your computer should answer to you.
I keep prices low where I can and use what I earn to keep the projects running.
One login, one API and one status layer, so nothing I make is an island.
Good automation works silently in the background. That's how the OS runs, and it's a big reason one person can maintain this much.
I started TMP and launched TMP Collectables, my authentication service for rare trading cards and vintage optics.
Triumphant OS launched, and I set up Central Server across 6 nodes so everything could share one backbone. TMP Merch and the CyberNexus API went into beta, and Collectables reached 5 marketplaces.
The SMP Server opened to the public. I moved to real-time Supabase infrastructure for instant sync across devices, and launched the unified account system.
I’m still improving TMPx Triumphant OS. My newer project, TMP EdgeDev, gives me a place to write and run code in the browser.
Got a question, found a bug, or just curious how I'm running all this on my own? Message me. It comes straight to me, not to a support queue.
These are the sites, tools and servers I’ve built. Several share the same TMP account.
My newer browser-based coding workspace. I built it for editing projects, running code and trying snippets in a sandbox.
The global authority in rare item authentication. Forensic-grade verification for trading cards and vintage optics across eBay, Vinted, Depop, and Big Cartel.
Official physical and digital merchandise platform with real-time inventory sync, global fulfillment, and seamless checkout powered by TMP Central Server.
High-fidelity multiplayer gaming environment with social clusters, leaderboards, and real-time event infrastructure.
Centralised data interface and API gateway for third-party integrations across the TMP ecosystem. WebSocket streaming, REST endpoints, and SDK support.
Our most ambitious project is fully here and ready: a desktop operating system built to become the better, newer Windows. It optimises itself silently in the background so it runs smoothly on minimal RAM. Recommended: 4GB RAM, with 128GB of storage as the very minimum.
Try my browser-based coding workspace and run snippets in the sandbox.
The backbone of the entire TMP ecosystem. Handles all authentication, traffic routing, real-time sync, and data replication across 6 nodes in North America, Europe, and Asia-Pacific. Every request on every platform routes through Central Server.
I built TMPx Triumphant OS to run quietly in the background. This page has the download, requirements and live service status.
TMP x Triumphant OS quietly optimises itself and your system in the background so it runs smoothly on minimal RAM. It isn't an assistant you open or talk to. The standard license costs £35 and includes lifetime updates and access. Terms and conditions apply.
OS availability, user access, authentication, and core services are operational.
Automation runs quietly in the background to keep the OS and your system smooth. It isn't an assistant you open or talk to.
Access and authentication are monitored as first-class service components through the live TMP status backend.
Memory, background tasks and system resources are tuned automatically so it stays responsive without needing much hardware.
It runs smoothly on minimal RAM, but 4GB is what I recommend for the best experience.
You need at least 128GB of storage. That's the very minimum I'd recommend.
Availability, dependencies, incidents, maintenance, and service state remain visible through the public status console.
This page reads the same Supabase-backed status state used by the public Status page and administrator console. Changes made by an authorized administrator propagate through the existing realtime channel.
Public OS access layer and availability state.
Account, entitlement, and access flow.
Identity and session services through Central Server.
Platform services and supporting infrastructure.
The £35 license provides lifetime updates and access for the licensed user. Use of TMPx Triumphant OS is subject to these terms and any additional license conditions presented at checkout.
I reuse the same account system and infrastructure across several projects. Here’s what happens behind the scenes.
Global CDN delivery, TLS 1.3 termination, and always-on DDoS shielding. Every connection to a TMP platform is encrypted before it touches the network.
The backbone. Load balancing, traffic routing, the Auth Hub for identity and sessions, and the Sync Relay that propagates state changes across every platform in real time.
Supabase-powered Postgres with realtime channels and row-level security. Status changes, incidents, and account data replicate instantly to every connected device — no refresh needed.
TMP EdgeDev, Triumphant OS, Collectables, Merch, SMP, LogoForge, ReviewBoost, and Dispatch — all consuming one unified identity and one live data fabric.
Central Server replicates across six nodes for sub-10ms regional latency. EU-WEST is the primary; every other node can take over routing within seconds.
I use access controls, shared sign-in and monitoring to protect the projects I run.
End-to-end encrypted user sessions across every platform, with automatic token rotation and short-lived credentials.
Edge-level traffic filtering absorbs volumetric attacks before they reach Central Server. Routing degrades gracefully, never catastrophically.
Database policies enforce access at the row level — your data is isolated by design, not by convention.
I built a few small games you can play here. Scores save on your device, and top runs can sync to the leaderboard.
Tap / click / press Space to jump the outage node.
Questions people ask me about the projects and TMP accounts. If I missed yours, send me a message.
TMP is where I share the projects I build, including my EdgeDev coding workspace, TMPx Triumphant OS and TMP Collectables. Several use the same TMP account.
Use the Login button in the navigation bar to sign up. Your account works across every TMP platform and comes with a unique 16-digit Collector ID.
It's built to run smoothly on minimal RAM. I recommend 4GB of RAM, and 128GB of storage is the very minimum you'll need.
No. There's nothing to open or talk to. Automation runs silently in the background, optimising the OS and your system so it stays smooth.
Visit the Status page for real-time service health, incident history, and scheduled maintenance windows across every node.
Yes. Authentication and data are handled through encrypted infrastructure, and we never sell user data. See our Contact page to reach the infrastructure team directly with any concerns.
Send me a note through the Contact page with what you have in mind.
Check the Status page first — most incidents are posted there in real time. If it isn't listed, contact us and we'll investigate.
Updates on what I’ve shipped, what I’m fixing and what I’m working on next.
Our AI-driven automation stack is now in internal developer testing, with a phased rollout planned across Collectables, TMP Inc, and certain platforms. There are currently no plans for a public CyberNexus API programme — CyberNexus continues as internal infrastructure.
PlatformTMPxTriumphant OS is fully here and ready: a desktop operating system that runs silently in the background to optimise itself and your system, so it runs smoothly on minimal RAM. Recommended: 4GB RAM, with 128GB of storage as the very minimum.
AnnouncementThe public status page now propagates every state change instantly over Supabase Realtime — service toggles, incidents, and maintenance windows appear on every connected device with zero refresh.
InfrastructureOur logistics platform now auto-detects ten carriers — Royal Mail, Evri, InPost, DPD, Parcelforce, Yodel, UPS, FedEx, DHL, and Amazon — with proof-of-posting records and a customer-facing tracking page.
LogisticsCentral Server now surfaces predictive load analytics across all six nodes, flagging anomalies before they become incidents. Rolling out to the status console through 2026.
PlatformA members-only marketplace for authenticated collectables, built on the Collectables verification registry and the unified TMP account. First invitations later this year.
AnnouncementTwo new platforms come under monitoring and unified identity: AI-powered logo generation and multi-platform review aggregation, both live on the status console.
LaunchThe unified TMP account ships with a 16-digit Collector ID, cross-platform sign-on, and email-verified password recovery — the same identity from Collectables to the status console.
IdentitySend me a message if you’ve found a bug, have a question or want to talk about a project.
I use this forum for questions, bug reports and feedback. Posts, comments and reactions are public.
Use one account for the TMP projects that share sign-in.
Check what’s running across the sites and servers I look after.
This page shows live status for the services I run.
Open Multi-site Maintenance to load saved settings.
For page-only maintenance, leave the website switch off, select the pages and save.
Loading saved page switches…
| Service | Region | Role | Protocol | Priority | Status | Actions |
|---|
Name|Descriptiontmp_status_cards — id (uuid pk), name, domain, url, description, status, latency, uptime, load_label, sort_order (int4), sub_components (jsonb), created_attmp_platform_cards — id (uuid pk), name, domain, url, description, status, featured (bool), sort_order (int4), created_atOpen the editor to load saved settings.
Blank settings inherit the site defaults. Changes stay in the draft until you save Appearance.
Page text and card styling.
We're performing scheduled maintenance. We'll be back shortly.