DEMONIC BINARY / ENGINEERING STORIES
Engineering work. Production incidents, mobile/backend systems and engineering labs. Explore the architecture, debugging and implementation behind each project.
PUBLISHED WORK / SCROLLING GALLERY
01 Production engineering Repairing a Cloudflare Worker canonical-URL redirect loop 02 Observability SiteGuard Monitor: service-health and alerting demonstrator 03 Mobile & APIs Mobile and backend workflows across multiple operational sites ENGINEERING AT A GLANCE
Published engineering stories Readable technical accounts
Production incident Routing and release repair
Controlled demonstrator Local monitoring implementation
Anonymized architecture story Mobile and backend architecture
FROM THE ENGINEERING RECORD
Read the notes behind each investigation, implementation and engineering decision.
These stories show engineering work from our systems and technical projects. For client references, our team can discuss what's available to share.
First-party operational work / 01 of 03
“ The edge Worker requested /index.html and /services.html while the asset layer redirected these requests to / and /services.
— Excerpt from the published engineering case study
A production site stopped serving pages because asset requests for .html files bounced back to their clean canonical paths.
EDGE ROUTING / PRODUCTION Before /services → /services.html → /servicesRedirect cycle
After /services → ASSETS.fetch(request)HTTP 200 · unknown routes 404
Featured engineering story 1 of 3 01 02 03
RESOURCES / ENGINEERING STORIES
Our website entered a redirect cycle when the Cloudflare Worker requested exported HTML filenames while the asset layer redirected back to canonical paths. We traced the response headers, changed the asset-fetch boundary, and verified successful pages, canonical redirects and missing routes.
EDGE ROUTING / REQUEST PATH
Before /services → /services.html → /services
After ASSETS.fetch(request) → HTTP 200
Read the full incident timeline At a glance
System Demonic Binary’s own website
Technology Next.js / Cloudflare Workers
Work performed Incident investigation, asset routing correction, regression verification
Evidence HTTP 200, 301 and 404 behavior YOUR SYSTEM COULD BE NEXT
Have a failure worth investigating? Describe the symptom and the system involved. We'll discuss where to start.
Find the relevant problem
Explore our engineering work. Find production debugging, backend authorization, mobile architecture and working engineering labs. Filter by the system or problem you're interested in.
Showing 3 of 3 published engineering examples.
Production engineering 01
First-party operational work
A production site stopped serving pages because asset requests for .html files bounced back to their clean canonical paths.
Release reliability · Next.js / Cloudflare Workers
Read the engineering story Observability 02
Internal demonstrator
We implemented Python/SQLite probes, durable health observations and a status view, then exercised the alert states with synthetic failure sequences.
Incident detection · Python / SQLite
Read the engineering story Mobile & APIs 03
Experience-based architecture overview
A founder-led engineering account of authenticated mobile/API workflows and offline recovery across multiple operating sites.
Authentication & recovery · iOS / Android / REST APIs
Read the engineering story CLIENT REFERENCES
Need to speak with someone we've worked with? Tell us what kind of project you're evaluating. We can discuss relevant work and check whether a client introduction is available.
Request a reference Have a difficult issue across your stack? Start with the symptoms and what your team needs to change. We'll discuss a focused investigation.
Discuss your problem 