Thornbury DigitalMenu

04 — Studio

Studio

A studio in Singapore that builds the whole site, not a deck about it.

IThe charter

Fig. — The charter Five articles

Article 01

Nothing here is inherited.

Every standard in this studio had to be written, argued over and agreed on. None of it arrived with the furniture. That is slower than adopting a house style, and it is the reason we can tell you why any decision was made rather than that it is simply how things are done.

Practice

The internal charter runs to fourteen articles. This page is the part that concerns you.

Article 02

We would rather be understood than admired.

A website can be impressive for five seconds. After that it has to be read, used on a phone with one thumb, and understood by someone who is not thinking about design at all. When those two ambitions disagree, the second one wins — every time, and in writing.

Practice

Priority when something has to give: usability, then information, then visual effect. Effects are cut first, never the other two.

Article 03

The second look is the one that counts.

Anything survives a glance. We build for the moment after it — when the site is opened on an old phone, when another developer reads the code, when nobody has touched it for two years and it still has to work. That moment is unglamorous and it is the one we design for.

Practice

Every effect on this site can be switched off. Turn JavaScript off and the pages still work.

Article 04

We say no in writing.

We publish a service only once we are confident in it — two of ours are still unlisted for exactly that reason, marked so everywhere they appear. That costs us enquiries. Pretending otherwise would cost more.

Practice

AEO / GEO and SEO are marked in development on every page they appear on, including the one selling them.

Article 05

Failure is budgeted, not hidden.

We expect some things not to work; that is written into how this studio operates, not buried halfway through. What we owe a client is not the pretence of never being wrong — it is that being wrong stays our problem, never theirs.

Practice

On delivery you receive the repository, the hosting, the domain and the mailbox. If you walk away, nothing stays with us.

Article 03, in practice

Throw it and the field stops, the film unloads and every animation on the site goes with them. The page carries on.

Article 05, in practice

On 26 August 2026 a content security policy change took our own site down for about seven hours. The build passed, the review passed and every page rendered — and nothing on them could be clicked. A person opening it in a browser found it; the tooling never did. Since then no change ships until someone has clicked through the live deploy, which is why every page here was checked in a real browser, and on a real phone, before this one.

A black hole seen edge-on: a thin, bright accretion disc bends up over and under a dark sphere, with one red filament running the length of the disc.

Fig. — The second look. Article 03, made literal: move across it and the surface gives way to the structure underneath.

IIWhat we are not the studio for

  • A logo on its own.

    We draw one when it is going on a site we are building.

  • A rebuild that has to be live in ten days.

    We will tell you what is actually possible in the time before you pay for any of it.

  • A site with nobody in the room who can decide.

    We will ask, and the answer has to come from someone.

IIIWho we are

Thornbury is new. We would rather you heard it from us.

A studio with thirty years behind it can point at the thirty years.

A studio with thirty years behind it can point at the thirty years. We do not have that, and pretending otherwise would fail the first standard on this page.

So we did the other thing. We decided what this studio believes, what it refuses to do, and who is accountable when it goes wrong — and we wrote it down. The charter above is that document.

How the work goes

Four things happen in the same order every time.

  1. The first deliverable is an audit, not a design. Sometimes it says you do not need us yet.

  2. Decisions are written where you can read them, with the reasoning attached.

  3. Documented guardrails, a review pass, and nothing that relies on one person’s memory.

  4. Repository, hosting, domain, mailbox — ownership transfers completely on delivery.

Fig. — 0 points, one scene at a time. Shape and surface direction from licensed photographs; none of their colour is used, no face is drawn, and nobody in them works here.

Two principals

  • Zhang Zhijie

    Founder / CEO

  • Isaac

    Co-Founder / COO

And behind the two of us

A founding team of around twenty — design, engineering, writing and research. Most are building their first company. None of them are a stock photograph of an office, which is why you will not find one on this page.

Founding team, not headcount

We will name people here when they are ready to be named, and not before.

Where this goes

We are not trying to become a large agency. We are trying to become a studio whose work rewards being looked at closely, for the kind of client who can tell the difference. That is a slower business and a smaller one, and we would rather have it.

Where we are

Singapore. Anything you send us is governed by the Personal Data Protection Act, the law our privacy policy is written against.

What we actually do

The whole site: design, writing, build, launch and handover, in one studio on one timeline. Nothing subcontracted.

How we are structured

Two principals and a small team, most on their first company — which is why the charter above exists in writing.

What we will not do

Publish a service before we are confident in it. Two are marked in development wherever they appear, including the page that sells them.

Freelancer, agency, or us — the six things that decide a project.

See the comparison

IVTwo promises, in plain words

  • Speed

    The words arrive first. The film, the motion and the big picture load after them, and a phone is never sent the desktop’s version.

    CheckOpen this site on a bad connection. The words are there first.

  • Ownership

    Domain, hosting, payment provider, business profile, analytics, mailbox: you create every one of them and own it, and we work inside them on access you can revoke. We never open a business-critical account in our own name to make setup easier, so nothing of yours can be held hostage and nothing depends on one of us being reachable. Two things stay ours — error monitoring and rate limiting — because they are shared plumbing nobody outside the studio logs into.

    1. 01The repository — every file the site is made of
    2. 02The hosting account, in your name
    3. 03The domain, in your name
    4. 04The mailbox on it

    CheckAsk any studio to put that list in writing before you sign. The answer tells you most of what you need to know.

For your developer — two things this page proves about itself

OneBelow is not a copy of this page’s content security policy — it is the policy, split into its directives out of the page’s own head as it loaded. View source and compare it line for line.

TwoThese are the opening lines of css/layout.css, fetched from the file itself while you were reading. Not a build artefact, not minified, not generated by anything.

VWhat sits behind the site

We do the work. These are the platforms it runs on — chosen, configured, and handed over with the site.

Platforms we build on — not partners, sponsors or endorsements.

Vercel
Where your site is published and served from. Every visitor touches this
Cloudflare
The domain, the DNS, and the shield in front of it. Before the first byte
Supabase
Where the site remembers things between visits. Only if your site stores things
Upstash
Stops one form being submitted ten thousand times. When a form gets hammered
Resend
Makes sure an enquiry actually reaches the inbox. When someone gets in touch
Sentry
Tells us a page broke before you have to. The moment something breaks
OWASP ZAP
Attacks the finished site before anyone else can. Before launch, and after changes
SonarCloud
Reads the code and flags what will hurt later. Deepest — you never see it

Neither ZAP nor SonarCloud makes a site unbreakable. Nothing does, and nobody can honestly promise it.

What they mean is that the known problems have been looked for, with public tools you are free to point at the site yourself.

If that sounds like the way you want it built, say hello.

Start a project