Skip to content
In Void

Freelance software collective

In Void

From the void, we build.

Every project begins as nothing: no schema, no screens, no name for the thing yet. We are comfortable there. Tell us what should exist, and we build it until it runs.

Capabilities

Three kinds of work, done properly.

interfaces

Web applications

Product interfaces, dashboards, and customer-facing sites built as one maintainable codebase. Typed end to end, fast on a phone, readable by the next developer who opens it.

services

APIs and backends

Data models, endpoints, and background jobs that behave the same on a quiet Tuesday and under real load. We design the schema before we write the first route.

rework

Inherited code

A project someone else started and left. We read it, map what it actually does, and get it back to a state where you can ship changes without holding your breath.

Process

Four steps, in this order, every time.

  1. Scope

    One call to understand the problem, then a written scope with what gets built, what does not, and a fixed price. You approve it before anything starts.

  2. Build

    Short cycles with something you can click at the end of each one. You see the work in progress on a private URL, not in a status report.

  3. Ship

    We deploy it, watch it under real traffic, and fix what the first week of real users exposes. Launch is a step in the plan, not the end of it.

  4. Hand over

    You receive the repository, the deploy pipeline, and documentation written for a developer who has never seen the project. No lock-in, no dependency on us.

The hardest part of software is the blank page. That is the part we like.

In Void
Selected work

What we are building.

A small studio ships a small number of things carefully. Here is the current one.

Aquabook

Booking and scheduling platform

In progress

Aquabook is in active development. The short version: scheduling and booking, built so the people running the operation spend less time in a spreadsheet.

A full write-up follows once it is live — the problem, the decisions we made, and what the numbers looked like afterwards.

Year
2026
Role
Design and development
Stack
TypeScriptNext.jsPostgreSQL
The next project goes here.
Contact

Tell us what should exist.

A rough idea is enough to start. Describe what you want built and we reply within two working days — with questions, a rough shape, and whether we are the right people for it.

Your message goes to our inbox and nowhere else. No tracking, no analytics, no mailing list.