About

Most software is weightless.We build the other kind.

Voidix is a small engineering studio. We take the surface that has to be fast, legible and alive at the same time — the trading floor, the clinical record, the storefront that behaves like film — and we build it properly, with the people who will maintain it in the room.

The premise

Weightless is the default, and mostly that is fine. Software loads, it works, it is forgotten between openings. Nobody was ever meant to feel anything about the expenses tool.

Gravity is the opposite property, and it is not decoration. A product has it when leaving costs something: when the number lands where the eye already was, when the motion is carrying information rather than apologising for a wait, when the thing is quick enough that nobody has to think about the thing. That is an engineering result before it is a design one, which is why the two are not separate jobs here.

A product earns its gravity in the first four hundred milliseconds, and keeps it over the next four hundred days.

What we are made of

  • The hard part first.

    The first fortnight goes on whatever the project is most likely to die of — the render path, the data volume, the thing nobody has built before. An estimate given before that is a guess in a suit.

  • One team, all the way down.

    The people who design the interaction write the shader that draws it. Nothing is thrown over a wall, because there is no wall to throw it over.

  • Performance is a design decision.

    Sixty frames on hardware people actually own is a constraint we design inside, not a pass we run at the end. It has killed features here, and it should have.

  • Handover is a deliverable.

    Documented, commented, and walked through until someone on your side can defend every decision in it. If you never need to call us again, that is the better outcome and we will take it.

How a build runs

  1. Week 1–2

    Prove

    We build the riskiest part first and find out whether it survives contact with real data.

  2. Week 2–3

    Shape

    You get a shape: what we would build, what we would refuse to build, and what it takes.

  3. 6–24 weeks

    Build

    Something working every week, on the real stack. Not a demo that becomes a rewrite.

  4. Then the door stays open

    Hand over

    Keys, docs and a stabilisation window while live traffic finds what staging never did.

The instruments

  • First reply

    Under 5 days

  • First proof

    2 weeks

  • Frame budget

    16.7 ms

  • Handover

    Fully documented

These are commitments, not a scoreboard. They are the four numbers we will be held to before a line of code exists.

What we work in

  • TypeScript
  • React & Next.js
  • WebGL / GLSL
  • Three.js
  • Realtime streams
  • iOS & Android
  • Design systems
  • Performance budgets

The list is short on purpose. We would rather be the studio that knows eight things completely than the one that lists forty.

Tell us what you are building.

A paragraph is enough — what it is, who it is for, and what has to be true on the day it ships.

Or come and build it with us