Skip to content
Ejaz Hussain on the hill in the rain, the black goat at his side and the herd behind

Ejaz Hussain.

Ten years in. Still self-taught. Still shipping.

Ejaz Labz. Founder, designer and developer at Launch Nest Studio. The one behind FormaOS. Adelaide, South Australia.

I run Launch Nest Studio and have for about six years. Almost everything I know I learned by shipping it, watching it break, and fixing it before anyone noticed. FormaOS is the clearest example: a compliance platform with multi-tenant data, billing and access control that I designed, built and still operate for paying customers. Around it sit a shelf of sites for real estate, fashion, jewellers, a rug shop and a documentary photographer’s archive, all held to the same bar, which is that I’d be happy to be caught using them.

Software is the part people ask about; it is not most of what leaves here. One week is a database schema, the next is an identity, a set of photographs relit until they read like a film, thirty suburb pages built to rank, or a migration off WordPress that nobody is supposed to notice happening. I do the design and the code, because handing one of them to someone else is where projects usually go wrong.

I did not come up through an engineering team. I spent seven years in customer-facing jobs first, including a stretch at Red Energy, which is where I learned that the thing a client asks for is usually two questions away from the thing they need. Before that: IT support, consulting, a CCNA, and enough hardware to know exactly how systems behave when they fall over. Graphic design, video editing and a bit of teaching did the rest.

What I take on

How one went

One project, by its dates: batoor.com, for the photographer Barat Ali Batoor, in 2026.

  1. 8 September

    I read before I drew anything: twenty years of his press, his old site in the Wayback Machine, the pages for his film. The brief I wrote from it settled most of the site before a page of it existed.

  2. 9 September

    The first build, in a day. His archive restored, every page in English and Hazaragi, and a preview he could open that night.

  3. 10 September

    I threw the first look out. It was tasteful in the way everyone’s default is, so it was redesigned from the type up: one face for the record, another kept for his own words, and lapis blue for the stone of Badakhshan.

  4. 11 September

    The archive recounted pixel by pixel: 236 photographs, not 237, because one had been uploaded twice. The same day the opening lost its shader. It was re-rendering his photographs, and the camera should move, not the pixels.

  5. 15 October

    He signed it off, and it was switched on the same day.

  6. 17 October

    The last of it: his interviews gathered on one page, every page ending on one of his photographs, and an audit of every one of its pages, their links and their images.

The whole case study

What I actually use

EngineeringNext.js, React, TypeScript, Node.js, Supabase / Postgres, Stripe billing, Auth / SSO / SCIM, Background jobs.

Interface & motionTailwind CSS, GSAP / ScrollTrigger, Framer Motion, WebGL / Three.js, Design systems, Accessibility (WCAG).

DesignUI / UX design, Brand identity, Figma, Motion design, Graphic design, Art direction.

GrowthTechnical SEO, Core Web Vitals, Programmatic SEO, Answer-engine optimisation, Analytics, Conversion.

If it’s on this list, I’ve shipped with it.

The rest is in the work.

Open the work