The studio makes digital things. In practice that means marketing sites, custom dashboards, interactive pieces, and the brand-data layers that sit between them — the parts of a company a person actually touches.

The work spans three.js and custom shaders where they earn their place, plain HTML where plain HTML is the right register, and bespoke data interfaces for companies whose work is partly in how they look at their own numbers. Charts and tables are treated as composed objects, not data dumps. Loading states are designed. Empty states are designed. Most of what distinguishes a studio site from a templated one lives in places a client doesn't think to ask about.

We don't work from templates, ever. Each engagement begins from the brand and the question, and ends with something specific to both. If a project could have been ordered from a marketplace, we are the wrong studio.

The companies we work well with already think of themselves as objects in the world. They have a sense of their typography, their color register, the music that would play in a room they had built. They are usually small, or recently small. They have a visual ambition that exceeds their budget, and they are willing to spend the difference on craft.

Most have tried the templated route and found it disappointing. Their site loads, the buttons work, and yet the product they sell — which has a soul — is represented by something that does not. They come to us because they want the digital surface to read at the same register as everything else they make.

Founders, in particular: people who care about the difference between a thing made by hand and a thing assembled. Labels with a clear point of view. Companies whose customer is also someone who notices.

A website is a place a person stands in for thirty seconds, an hour, a day. The question is what is in that place when they arrive — and what stays with them when they leave.

Most digital surfaces leave nothing. They were built efficiently. They funnel the visitor toward a click, a signup, a purchase, and they have learned, over twenty years of optimization, to do so with great precision. A page that does this well is, by industry definition, working. But the visitor walks away with no memory of where they were, because they were nowhere.

Funnels are not places.

A world, by contrast, is built to be inhabited. It has its own weather. It implies things outside the frame — the room next door, the season, a history. A visitor who spends a few seconds inside it carries some of it with them afterward, the way one carries a film, not the way one carries a transaction.

To build digital things this way is mostly slow, untidy work. An afternoon on a color transition no one will inspect. A sentence on the contact page rewritten until it stops sounding like a sentence on a contact page. A shader written so that the hero of the site reads as paint and not as code. None of it is efficient. All of it is the difference between a place and a delivery vehicle.

Most engagements start with a long conversation. Not a sales call — a conversation about what the company is, who its customer is, and what the work has to do. We come out of it with a brief the founder recognizes as theirs.

What follows is the stage we treat as the studio's distinguishing move: the visual world. Before any code, before any layout, we build the moodboard, the color register, the typographic temperament, and a handful of reference compositions that establish what the site is going to feel like to be inside. This is the part most studios treat as a luxury. We treat it as the brief.

Build and polish go quickly after that. We code carefully and finish slowly. The last fifteen percent of a project — the cursor, the loading state, the seventh frame of an animation — is where the work earns its register. We do not ship until that work is done.

Veladura is small on purpose. The studio is run by a founder — a working data scientist, philosopher, and software designer based in Santiago — with a small network of collaborators when a project calls for one. There are no team photos on this page because the work is what we would like to be looked at.

Smallness is a constraint we have chosen. It means we take on a few engagements a year, that the founder is the person who answers email, and that the person who writes the shader also writes the case study about it. We expect this to remain true for some time.