Product studio
Ourfirstclientwas us.
Six products designed, built, shipped and kept alive — the same hands take on a few client builds a year. One at a time, never two.
- 06
- Products owned
- 02
- Shipped & live
- 04
- Rolling out
001 — Why we exist
Aportfolioshowswhathappened.Aproductisstillhappening.Weownsix—ourmoney,ourname,ourtwointhemorning.
Yoursgetsthesametreatment.
002 — What we own
Sixproducts.Allours.
Not case studies — a case study can be abandoned the day the invoice clears. These cannot be, because we still run them: scoped, funded, designed and built by the hands you would be hiring.
- 02
A tarot reading written for the question you actually asked
Ask something, then draw a Past / Present / Future spread from an on-screen Rider–Waite–Smith deck. The cards are dealt server-side before any money changes hands; the first two turn over free, and the full reading pairs a curated 78-card library with an AI-written narrative.
- Web app
- Workers AI
- Credits
In development - 03
An infinite board where space is bought once and kept
Pan and zoom across an endless canvas and claim the block you want by dragging it out at your image's own aspect ratio. Bigger blocks cost proportionally more, so it becomes a game of who commits the most space — the Million Dollar Homepage, without the edges.
- Infinite canvas
- One-time claim
- Stripe
In development - 04
A book of nothing, sold as a state of art
A deliberately empty book, given the storefront it deserves: a Stripe-Press-styled page built around a 3D book you can pick up and rotate under moving light. The object is the argument, so the site exists to let you turn it over before you buy it.
- WebGL
- Commerce
- Physical + digital
In development - 05
A glimpse of who they will become
A parent enters a newborn's birth details and receives a written blueprint — playful, personal suggestions for sports, languages and hobbies, each traced back to a real natal chart. Built to be printed and kept rather than scrolled past.
- Keepsake
- Natal chart
- Generated prose
In development
003 — What we do
Onestack,deeplyunderstood.
We would rather know one toolchain to the bottom than twenty to the brochure. Everything below is in production across the products above — nothing on this list is aspirational.
- 01
Product design & build
From a sentence on a napkin to a thing people pay for. Interface design, front to back engineering, and the unglamorous middle — auth, billing, email, admin. The parts nobody screenshots are the parts that decide whether it survives contact with real users.
- Interface design
- Design systems
- Nuxt & Vue
- TypeScript end to end
- 02
Edge-native architecture
Every product we own runs on Cloudflare Workers and ships through CI/CD. Serverless SQL, object storage and queues at the edge: low latency everywhere your users are, and an infrastructure bill that stays boring while you grow.
- Cloudflare Workers
- D1 & Drizzle
- R2 & Queues
- CI/CD
- 03
AI where it earns its place
We ship generative features when they make the product better and leave them out when they do not. Model routing through an AI gateway, prompts held under version control, graceful fallbacks — and costs you can actually forecast.
- Workers AI
- AI Gateway
- Prompt engineering
- Cost modelling
- 04
Payments & growth
Checkout, subscriptions, credits and one-time purchases with server-computed pricing, so the number a customer sees is the number you meant. Analytics wired in from day one, because shipping without measurement is just guessing.
- Stripe
- Server-side pricing
- Product analytics
- SEO foundations
004 — How we work
Reduce.Prototype.Build.Run.
- 01
Reduce
Most briefs contain three products wearing a trench coat. We spend the first week finding the one that matters and arguing the rest out of scope — the cheapest work is the work you never build.
- 02
Prototype
A clickable, deployed thing before a line of production code. Real URLs on real devices, because opinions about a mockup are worth very little and opinions about a working screen are worth a great deal.
- 03
Build
One stack, deeply understood: Nuxt on Cloudflare Workers, typed end to end, tested where tests pay for themselves. You get access to the repo and the deploy previews from the first week, not the last.
- 04
Run
Shipping is the midpoint. We stay for the part where real traffic finds the sharp edges — monitoring, iteration, and the small relentless improvements that separate a launch from a product.
005 — Work with us
Ournextprojectcouldbeyours.
Before you ask
We spent years on the other side — logos, websites, a thousand small briefs delivered and handed over. None of it is on this page, because none of it had to survive: a deliverable ends at handover, a product has to keep earning. Devilos exists to do only the second kind of work.
Fixed-price phases rather than open-ended hourly billing. We scope a phase, quote it, and deliver it. If it turns out we scoped it wrong, that is our risk to carry, not a change request for you to absorb.
A small number a year, one at a time. The rest of our capacity goes into our own products — which is what keeps the practice sharp and means we are never taking work purely to make payroll.
Everything — and from the first week, not the end. The repo, the infrastructure and the deploy pipeline are yours, on managed primitives any Nuxt developer can pick up. We stay because we are useful, not because you are locked in.