Senior full-stack engineer in Japan, 12 years in. I scope the problem, design the system, write the code and look after it in production. Most of my work belongs to clients, but the tools I built for myself don't, and you can try all three on this page.
{
"title": "I'm Muazzam. I build software, then I keep it running.",
"sub": "Senior full-stack engineer in Japan, 12 years in. I scope the problem, design the system, write the code and look after it in production. Most of my work belongs to clients, but the tools I built for myself don't, and you can try all three on this page.",
"photo": "/assets/images/home/muazzam.jpg"
}src/data/pages/home.json → products
[
{
"id": "repocms",
"name": "RepoCMS",
"tagline": "Edit a static site's content without touching code.",
"status": "In daily use",
"desc": "Static sites are fast, but every text change still needed a developer. RepoCMS connects to a GitHub repository, turns each JSON content file into a form, manages the media folder, and commits changes that trigger a Cloudflare build. An agency now edits all of its client sites with it.",
"stack": [
"FastAPI",
"MongoDB",
"React 19",
"Vite",
"shadcn/ui",
"Docker"
],
"links": [],
"demo": "repocms"
},
{
"id": "linerichmenu",
"name": "LineRichMenu",
"tagline": "Design and switch LINE rich menus across organisations.",
"status": "In use",
"desc": "Managing LINE rich menus means hand-writing pixel coordinates and juggling channel tokens. LineRichMenu handles token-based onboarding for each organisation, gives you a visual editor for tap areas, and switches menus across organisations with real-time data.",
"stack": [
"Next.js",
"TypeScript",
"Supabase",
"shadcn/ui"
],
"links": [],
"demo": "richmenu"
},
{
"id": "qafied",
"name": "Qafied",
"tagline": "Visual feedback, pinned to the actual page.",
"status": "Live",
"desc": "Client feedback by email means screenshots with arrows and \"the button on the left\". Qafied is one script tag on any site: people click where the problem is and leave a pinned comment. Each comment captures a screenshot, browser, OS, viewport and exact coordinates, then lands in a dashboard inbox with a status workflow.",
"stack": [
"FastAPI",
"MongoDB",
"React",
"Tailwind",
"shadcn/ui",
"Vanilla JS widget",
"Docker"
],
"links": [
{
"label": "qafied.link",
"href": "https://qafied.link/",
"external": true
}
],
"demo": "qafied"
}
]My own products, as opposed to client work. Each one has a working demo on this page.
Edit a static site's content without touching code.
Static sites are fast, but every text change still needed a developer. RepoCMS connects to a GitHub repository, turns each JSON content file into a form, manages the media folder, and commits changes that trigger a Cloudflare build. An agency now edits all of its client sites with it.
FastAPI, MongoDB, React 19, Vite, shadcn/ui, Docker
Try the demo at the top of the pageDesign and switch LINE rich menus across organisations.
Managing LINE rich menus means hand-writing pixel coordinates and juggling channel tokens. LineRichMenu handles token-based onboarding for each organisation, gives you a visual editor for tap areas, and switches menus across organisations with real-time data.
Next.js, TypeScript, Supabase, shadcn/ui
Visual feedback, pinned to the actual page.
Client feedback by email means screenshots with arrows and "the button on the left". Qafied is one script tag on any site: people click where the problem is and leave a pinned comment. Each comment captures a screenshot, browser, OS, viewport and exact coordinates, then lands in a dashboard inbox with a status workflow.
FastAPI, MongoDB, React, Tailwind, shadcn/ui, Vanilla JS widget, Docker
This is a local copy of the Qafied widget. Turn on feedback mode, click anywhere on the page, and pin a comment. On a real site the comment lands in a dashboard inbox with a screenshot. Here you only see what would be sent.
comment payload
No pins yet. Turn on feedback mode and click somewhere.Turn on JavaScript to pin comments.
src/data/pages/home.json → workflow
[
{
"title": "Conventions as skills",
"desc": "House rules live in Claude Code skills: how our Astro sites are structured, a WordPress launch checklist, a site audit, a Figma-to-Bricks playbook, a SaaS starter. Agents follow the same standard on every project, and each project's lessons go back into the skill."
},
{
"title": "Real systems over MCP",
"desc": "WordPress installs and business tools are connected over MCP, so an agent can inspect a live site, plan a change or draft a handover against real data, behind permission prompts rather than copy-pasted context."
},
{
"title": "Parallel work, one decision",
"desc": "Research and audits fan out to sub-agents, one per site, server or source, and only their conclusions come back. I make the call and write down the trade-offs."
},
{
"title": "Review stays human",
"desc": "Agents scaffold, refactor and explore alternatives. I read every diff, and anything that touches production, payments or client data goes through me."
}
]Most of my code is now written with agents. The part that matters is the system around them: the conventions they follow, the systems they can reach, and the review they go through.
src/data/pages/home.json → clientWork
[
{
"title": "Leasing operations platform",
"kind": "Application",
"desc": "A furniture and appliance leasing business was running all its orders on spreadsheets and email. I designed and built the system to replace it. Staff get quotes from suppliers, send estimates and follow each order until delivery. Customers browse the catalogue, build their order and approve the estimate. WordPress is only used for login, the REST API and the back office. All the business rules are on the server, and staff and customers have separate React apps, so cost and margin data never goes to a customer's browser. It has 28 domain modules, an order status flow, PDF estimates, and 43 test suites that run on every deploy.",
"stack": [
"PHP",
"REST API",
"React",
"WordPress (auth + API only)",
"JetEngine"
]
},
{
"title": "Multi-tenant B2B commerce platform",
"kind": "SaaS",
"desc": "Wholesale buyers need more than a normal web shop. I built a multi-tenant platform where one deployment serves many stores, each on its own subdomain. It has quotes and request for quote, price lists per customer group, credit terms and invoicing, roles and permissions, and an audit log of every change. It is API first with a typed SDK, so a store can build its own storefront. Every store also has an MCP endpoint with scoped keys, so AI agents can work with the store's data safely.",
"stack": [
"FastAPI",
"PostgreSQL",
"Redis",
"React",
"Docker",
"MCP"
]
},
{
"title": "Performance and traffic firefighting",
"kind": "Performance",
"desc": "A bilingual WooCommerce store with 42 plugins took 4.6–6.6s to render uncached. Profiling put the cost in PHP rendering, not the database (0.07s). Removing session locking made pages cacheable by the CDN again: cached shop pages now return in ~30ms, a blocking admin check went from 2.57s to 0.003s, and home page HTML shrank 28%. On the same estate, one crawler was generating 84% of traffic (up to 155k requests a day) through faceted filter URLs, each an ~11s cache miss. Contained it in layers: robots.txt, a Cloudflare WAF rule, and a server-level block.",
"stack": [
"WooCommerce",
"PHP profiling",
"Cloudflare WAF",
"LiteSpeed",
"Redis"
]
},
{
"title": "Lead ingestion and spam filtering platform",
"kind": "SaaS",
"desc": "An agency was losing hours to spam and to a different SMTP setup on every client site. I designed and built a multi-tenant platform: per-client endpoints and email settings, submissions scored and filtered, suspect leads held for review, clean leads forwarded automatically.",
"stack": [
"FastAPI",
"MongoDB",
"React",
"Tailwind",
"Docker"
]
},
{
"title": "Static site framework for an agency",
"kind": "Architecture",
"desc": "The agency's WordPress sites were slow and costly to maintain. I proposed and built the replacement: Astro sites with all content in JSON, pages composed from reusable components, deployed on Cloudflare. This site is built the same way.",
"stack": [
"Astro",
"JSON content",
"Cloudflare Pages"
]
},
{
"title": "Operations system inside WordPress",
"kind": "Internal tool",
"desc": "A client wanted an internal system but needed staff to keep the WordPress admin they knew. I kept orders, line items, logs and notifications in dedicated tables instead of posts, and built React dashboards for staff and customers on top of the REST API.",
"stack": [
"WordPress",
"Custom tables",
"REST API",
"React",
"PHP"
]
},
{
"title": "Hosting estate consolidation",
"kind": "Infrastructure",
"desc": "Audited a multi-provider estate of 16 servers and 100+ DNS zones. Designed an ARM-based consolidation, set up automated backups to object storage and storage boxes, and cleared out stale DNS records and 150+ GB of duplicate data.",
"stack": [
"Linux",
"Docker",
"Cloudflare",
"S3 storage"
]
},
{
"title": "Production security remediation",
"kind": "Incident response",
"desc": "Patched a CVSS 10.0 Next.js remote code execution flaw (GHSA-9qr9-h5gf-34mp) across three production containers, and stabilised a compromised WooCommerce store: bot traffic, contaminated serialised data and caching faults.",
"stack": [
"Security",
"Docker",
"Oracle Cloud",
"WooCommerce"
]
},
{
"title": "Shopify builds and integrations",
"kind": "E-commerce",
"desc": "Store builds and rebuilds with custom Liquid themes, third-party systems connected through the Shopify REST and GraphQL APIs, custom pixel events, and UX changes aimed at conversion. Led a major theme upgrade (Broadcast v4 to v8) with custom code kept in isolated snippets so future updates stay safe, and fixed a live search page freeze caused by legacy theme JavaScript.",
"stack": [
"Shopify",
"Liquid",
"GraphQL",
"GA4"
]
},
{
"title": "Healthcare web platforms",
"kind": "Healthcare",
"desc": "A multi-step application portal for a medical facility with conditional form logic, custom roles and admin workflows, and a headless Next.js site for a health brand with WordPress as the editorial backend.",
"stack": [
"WordPress",
"Next.js",
"Headless CMS"
]
}
]This work belongs to clients and agencies, so there are no names. What's left is the problem, what I decided, and the stack.
A furniture and appliance leasing business was running all its orders on spreadsheets and email. I designed and built the system to replace it. Staff get quotes from suppliers, send estimates and follow each order until delivery. Customers browse the catalogue, build their order and approve the estimate. WordPress is only used for login, the REST API and the back office. All the business rules are on the server, and staff and customers have separate React apps, so cost and margin data never goes to a customer's browser. It has 28 domain modules, an order status flow, PDF estimates, and 43 test suites that run on every deploy.
PHP, REST API, React, WordPress (auth + API only), JetEngine
Wholesale buyers need more than a normal web shop. I built a multi-tenant platform where one deployment serves many stores, each on its own subdomain. It has quotes and request for quote, price lists per customer group, credit terms and invoicing, roles and permissions, and an audit log of every change. It is API first with a typed SDK, so a store can build its own storefront. Every store also has an MCP endpoint with scoped keys, so AI agents can work with the store's data safely.
FastAPI, PostgreSQL, Redis, React, Docker, MCP
A bilingual WooCommerce store with 42 plugins took 4.6–6.6s to render uncached. Profiling put the cost in PHP rendering, not the database (0.07s). Removing session locking made pages cacheable by the CDN again: cached shop pages now return in ~30ms, a blocking admin check went from 2.57s to 0.003s, and home page HTML shrank 28%. On the same estate, one crawler was generating 84% of traffic (up to 155k requests a day) through faceted filter URLs, each an ~11s cache miss. Contained it in layers: robots.txt, a Cloudflare WAF rule, and a server-level block.
WooCommerce, PHP profiling, Cloudflare WAF, LiteSpeed, Redis
An agency was losing hours to spam and to a different SMTP setup on every client site. I designed and built a multi-tenant platform: per-client endpoints and email settings, submissions scored and filtered, suspect leads held for review, clean leads forwarded automatically.
FastAPI, MongoDB, React, Tailwind, Docker
The agency's WordPress sites were slow and costly to maintain. I proposed and built the replacement: Astro sites with all content in JSON, pages composed from reusable components, deployed on Cloudflare. This site is built the same way.
Astro, JSON content, Cloudflare Pages
A client wanted an internal system but needed staff to keep the WordPress admin they knew. I kept orders, line items, logs and notifications in dedicated tables instead of posts, and built React dashboards for staff and customers on top of the REST API.
WordPress, Custom tables, REST API, React, PHP
Audited a multi-provider estate of 16 servers and 100+ DNS zones. Designed an ARM-based consolidation, set up automated backups to object storage and storage boxes, and cleared out stale DNS records and 150+ GB of duplicate data.
Linux, Docker, Cloudflare, S3 storage
Patched a CVSS 10.0 Next.js remote code execution flaw (GHSA-9qr9-h5gf-34mp) across three production containers, and stabilised a compromised WooCommerce store: bot traffic, contaminated serialised data and caching faults.
Security, Docker, Oracle Cloud, WooCommerce
Store builds and rebuilds with custom Liquid themes, third-party systems connected through the Shopify REST and GraphQL APIs, custom pixel events, and UX changes aimed at conversion. Led a major theme upgrade (Broadcast v4 to v8) with custom code kept in isolated snippets so future updates stay safe, and fixed a live search page freeze caused by legacy theme JavaScript.
Shopify, Liquid, GraphQL, GA4
A multi-step application portal for a medical facility with conditional form logic, custom roles and admin workflows, and a headless Next.js site for a health brand with WordPress as the editorial backend.
WordPress, Next.js, Headless CMS
src/data/pages/home.json → background
{
"id": "background",
"title": "Background",
"paragraphs": [
"8+ years at a Tokyo digital agency, from developer to lead developer to Solutions Architect, running several accounts at once across e-commerce, healthcare and media. Since 2014, an independent practice alongside it, building SaaS products, internal tools and the servers they run on.",
"I work best when there's a real problem nobody has shaped yet. I'll ask the awkward questions early, write down the trade-offs before any code, and stay with the system after launch."
],
"stackLabel": "What I reach for",
"stack": [
{
"area": "Backend",
"tools": "Python, FastAPI, PHP, Laravel, Node.js"
},
{
"area": "Frontend",
"tools": "TypeScript, React, Next.js, Astro, Tailwind"
},
{
"area": "Data",
"tools": "PostgreSQL, MongoDB, Redis, Supabase"
},
{
"area": "Commerce & CMS",
"tools": "Shopify, WordPress, WooCommerce"
},
{
"area": "Infrastructure",
"tools": "Docker, Linux, Cloudflare, AWS, Hetzner"
}
]
}8+ years at a Tokyo digital agency, from developer to lead developer to Solutions Architect, running several accounts at once across e-commerce, healthcare and media. Since 2014, an independent practice alongside it, building SaaS products, internal tools and the servers they run on.
I work best when there's a real problem nobody has shaped yet. I'll ask the awkward questions early, write down the trade-offs before any code, and stay with the system after launch.
src/data/pages/home.json → reviews
[
{
"text": "Yet again, Muazzam was simply excellent to deal with. His knowledge and experience is simply invaluable. I cannot recommend him highly enough.",
"author": "Kiaran B., Erskine, on PeoplePerHour"
},
{
"text": "Muazzam is proactive and organised. He can handle many balls in the air. He made me believe that we can reorganise our work, and finally we are on track.",
"author": "LinkedIn recommendation, agricultural portal"
},
{
"text": "Knowledgeable, helpful, fair, honest individual. Will continue to work with you when it comes to web development.",
"author": "Andrew G., Potters Bar, on PeoplePerHour"
}
]Yet again, Muazzam was simply excellent to deal with. His knowledge and experience is simply invaluable. I cannot recommend him highly enough.
Muazzam is proactive and organised. He can handle many balls in the air. He made me believe that we can reorganise our work, and finally we are on track.
Knowledgeable, helpful, fair, honest individual. Will continue to work with you when it comes to web development.
222 reviews averaging 4.9 out of 5 on PeoplePerHour.
src/data/pages/home.json → now
{
"id": "now",
"title": "Now",
"timeLabel": "My time",
"timeFallback": "Japan, UTC+9",
"items": [
{
"label": "Open to",
"value": "Senior full-stack and architect roles, and select projects"
},
{
"label": "Overlap",
"value": "EU mornings, US East evenings"
}
],
"builtLabel": "This build"
}Hiring a senior full-stack engineer, or have a system that needs building or fixing? Email me what you're working on, or book a call. No forms.