KILN.
← Home
The studioOne pair of hands

One maker at the kiln.

KILN is one person in Singapore. I do the design and write the code myself, which mostly means nothing gets simplified on the way from one to the other.

Who's at the kiln

Hello. I'm Lin.

I design and build websites on my own, and I've never been able to keep the two apart for long.

I studied banking and finance at polytechnic, then switched to computer science. Finance was never going to stick. I'd been drawing and messing about with graphics the whole way through anyway, and what I actually wanted was to build things — web design is where those two ended up overlapping.

How the work goes: one project at a time, so yours isn't sitting behind three others. I write every line of it, with no page builder underneath and no theme bought and re-skinned. Because I know how long that takes by now, I can give you a fixed price instead of running a meter.

The concept builds in the work section are self-initiated. Nobody paid for those and no client brief shaped them — I'd rather say that outright than dress personal projects up as case studies. They're there so you can see the standard before you spend anything. Executed is the different one: a subscription platform that's live in production, with most of it behind a login.

What each tier includes, and how a project runs →

How I work
Made to order

No templates, ever

Each project is shaped for what it actually is — down to the motion and the last line of markup. No page-builder underneath, no reused theme.

Real technique

Build the thing, not a picture of it

When a project calls for 3D, shaders, or generative motion, I build the technique itself — not a static image pretending to be it.

Honest craft

Fast, accessible, sturdy

Under the atmosphere, the basics are handled: performance, accessibility, responsive behaviour, and graceful fallbacks. Craft you feel, even when you can't name it.

What I build with

No framework is a house style here; I pick the lightest thing that does the job. Most of these sites ship as static files with no build step, which is why they load fast and keep working. When a build genuinely needs a library — three.js for real geometry, GSAP for orchestrated motion — I bring in one, tell you what it adds to the page, and you agree to it before it goes in.

Languages
  • HTML · semantic, hand-written
  • CSS · Grid, custom properties
  • JavaScript · vanilla, no jQuery
  • GLSL · fragment and vertex shaders
Graphics & 3D
  • WebGL · written raw, not wrapped
  • Three.js · when real geometry earns it
  • Canvas 2D · particles, fields, diagrams
  • SVG · drawn and animated
Motion
  • GSAP + ScrollTrigger
  • Lenis · smooth scrolling
  • IntersectionObserver
  • Raw requestAnimationFrame
Craft & care
  • Responsive down to 360px
  • Keyboard and screen-reader paths
  • prefers-reduced-motion honoured
  • Works with JavaScript off
Delivery
  • Static hosting · Netlify, Vercel, Pages
  • Git · every change tracked
  • Domain and DNS setup
  • Analytics, if you want it
Design
  • Figma · files you can open
  • Type scales and colour systems
  • Favicons and share previews
Light the kiln

Got something worth firing?

Tell me what you're making. An email is enough — it comes straight to me, because there is nobody else here for it to go to first.

hello@studiokiln.space
  • Tell meWhat you're building, roughly when you need it, and a link or two you like.
  • You'll hear backWithin 48 hours, usually sooner. I'm in Singapore, so mind the time difference if you're not.
  • You'll getA tier, a timeline and a fixed price. I don't bill by the hour.