Full-stack engineer. AI builder. Tinkerer by nature.
I design, build and run the software behind the businesses I'm part of — and put AI to work inside it. From sign-in and point-of-sale to the factory floor and the back office.
8systems in production
6businesses running on them
1sign-in for all of it
~/william — zsh
$ whoami
william-d · full-stack engineer · ai builder
$ cat role.txt
design → build → deploy → keep it running
$ ls ~/systems
clauth cebos cebpos commy alab-erp
alab-studio alabapparel.com xpenses
$ systemctl status --all
● 8 units · active (running)$ uptime
since the first firmware build — still shipping
01 · systems in production
Things I've built that people use every day.
Every system below is designed, coded, deployed and maintained by me — the servers, releases and backups included.
01 / identity
Clauth
architect · sole engineer
live
An OpenID Connect identity server built from scratch. One sign-in for every app — users, organizations and per-app roles live here, and each app enforces its own permissions.
Single sign-on across all the systems on this page
A business operating system for Philippine SMEs. Legal entities, compliance requirements, people and money in one place — fed by the other apps instead of re-typed.
Hub that the POS, expense and ERP systems report into
The ERP in charge of Alab Apparel's full-sublimation shirt production — enquiry, artwork, quote, job order, printing, sewing, QC, shipping and invoicing.
One quote approval creates the job, reserves materials and raises the deposit invoice — in a single transaction
Artwork gate: nothing gets printed without a signed-off design
Expense tracking for the companies I work with. Snap a receipt, AI reads it, and it moves through an approval chain before it reaches the books.
Vision-model receipt extraction — vendor, amount, VAT, date
Mobile app for capture, web console for review and approvals
Feeds approved expenses into CebOS
internal tool · no public link
Laravel 12Expo / React NativeClaude · MiMo
08 / operations
Commy
architect · sole engineer
in use · internal
The ERP that runs the Cakes by Grace food commissary — every order from booking to pickup or delivery, the production calendar the kitchen works from, and the money that comes back in.
Orders, production calendar, deliveries, pickups and trip tickets
Invoices, payments and balances, with daily reports
REST API that CebOS and finance reports read from
internal tool · no public link
PHPWooCommerceREST APIPlaywright
02 · ai in production
AI where it earns its place.
Not demos. Models doing real work inside the systems above — reading receipts, designing kits, answering to agents — behind the same permissions, logs and approvals as everything else.
vision · extraction
Receipts that read themselves
Xpenses sends a photo of a receipt to a vision model and gets back vendor, amount, VAT and date. Providers are pluggable — Claude, MiMo or any OpenAI-compatible model, routed per task.
llm · image generation
Design by conversation
In Alab Studio a team describes its kit in a chat; a language model turns it into a brief, image models draw the designs and repaint them onto the real pattern pieces for print.
mcp · agents
Agents as first-class users
CebPOS ships an MCP server, so AI assistants can look up sales and act through scoped, audited API keys — the same guard rails a human user gets.
workflow
Engineering with agents
I build alongside AI coding agents every day — specs, code, tests, reviews, server work — while I own the architecture and every release. That's how one engineer ships eight systems.
03 · expertise
What I build, with proof.
Every area below is backed by a system that is running today — tap a name to see its screens.
erp
ERP for food & commissary
Orders, production calendars, deliveries, pickups and costing for kitchens and cafés.
built:
erp
ERP for clothing manufacturing
Enquiry to invoice for made-to-order production — artwork, job orders, scheduling, QC, shipping.
built:
commerce
E-commerce
Shopify and WooCommerce stores, custom storefronts, carts and checkouts wired into operations.
built:
cms
CMS & WordPress
Custom WordPress themes and plugins — from agency client sites to a full ERP running as a plugin.
built:
web
Marketing landing pages
Fast, hand-built pages that explain a product and convert — no page builder.
built:
web
Websites & custom applications
Full-stack web, mobile and PWA apps, designed, built, deployed and run end to end.
built:
ops
Invoicing & payments
Invoices, deposits, balances, receipts and payment allocation — tax-aware, audit-logged.
built:
ops
Inventory management
Stock levels, material reservations and items that stay in sync with sales and production.
built:
ops
HR tools
People records, labour-law checks, health certificates, probation and minimum-wage alerts.
built:
ai
AI integration
Vision extraction, LLM chat, image generation and MCP servers — in production, with cost tracking and guard rails.
built:
auto
Automations & integrations
APIs, webhooks, scheduled jobs and syncs so data moves between systems instead of being re-typed.
built:
auto
Identity & security
Single sign-on, roles and permissions, 2-step verification and hardened servers.
built:
…and the glue in between: reporting, exports, PDFs, compliance tracking, backups and the servers it all runs on.
04 · how it connects
Not eight projects. One ecosystem.
Shared foundations mean every new system starts with the hard parts done: one identity layer for sign-in, one hub for the numbers, the same storage and release process everywhere. Two production lines run on it: Commy runs the food commissary, Alab ERP runs full-sublimation shirt production.
sign-in (OpenID Connect)data: sales, expenses, orders, production
serversLinux servers I patch, harden and monitor myself
storageCloudflare R2 for media and off-site backups
releasesVersioned, tagged releases — not hand-edited files
backupsScheduled, and restores actually tested
05 · path
From hardware to whole systems.
Started close to the metal, moved up the stack, then into leading teams. Now building the foundations for the businesses I'm part of.
HEAD · now
Builder & technology partner
TheCakeLabs — independent
Setting up the software and infrastructure for the businesses I co-own and work with — identity, POS, ERP, expenses, and the servers they run on.
v6
Lead Developer → Head of Technology
Dilate Digital
Came back to Dilate as lead developer, then took on the whole technology side — how the team builds, plus the hosting and domains behind the clients.
v5
Head of Software Engineering
Definics
Led the software engineering team and how it built and shipped.
v4
Web Developer
Dilate Digital
Custom WordPress themes and plugins for a digital agency's clients.
v3
Software Engineer
TrustArc
Continued on the privacy and compliance platform after TRUSTe became TrustArc.
v2
Software Engineer
TRUSTe
Privacy and trust technology for businesses online.
v1
Firmware Engineer
ASPROTRA Inc.
Embedded software — where every byte and every cycle counts.
v0
Service Engineer
first role
Where it started: fixing the things people depend on.
06 · what it runs
Real businesses, not demos.
The software is built for companies I co-own, run or work alongside — so it gets tested at the counter, on the factory floor and at month-end.
Cakes by Gracecakes · Technology Innovation Consultant
The Cake Cafecafé
Java Icefood & drinks
Alab Apparelsportswear manufacturing
Alab Studiosublimation design
Alab Sportstournament live streaming
Built under TheCakeLabs— formerly Glabs Tech
07 · how I build
Boring where it matters. Curious everywhere else.
A few rules I keep coming back to.
01
Build for the business you actually run
I'm on the operations side too. If it doesn't survive a busy Saturday at the counter, it isn't done.
02
Own it end to end
Design, code, servers, backups, releases. When something breaks at 2 a.m., I already know where to look.
03
Shared foundations
One identity layer, one hub, one way to store and release. Each new system starts with the hard parts done.
04
Reliability is a feature
Tagged releases, tested restores, least-privilege keys. Nobody notices good infrastructure — that's the point.
05
Tinker, then harden
Prototype fast to learn what's real. Then slow down and make it solid before people depend on it.
06
Plain over clever
Code and screens that the next person — or me in a year — can understand at a glance.
A God-fearing man first, and a member of the BCBP community — the Brotherhood of Christ Business and Professionals.
I'm also the Technology Innovation Consultant for Cakes by Grace, which is why most of what I build starts as a real problem at the counter, on the floor or in the back office.
And a creator and tinkerer by nature — if something can be taken apart, understood and made better, I'm probably already halfway through it.
“And whatsoever ye do, do it heartily, as to the Lord, and not unto men.”
— Colossians 3:23
09 · let's talk
Got a challenging problem technology could solve?
Let's talk over coffee. Tell me what's slowing your business down — orders, stock, paperwork, a process that lives in someone's head — and we'll see what can be built.