Where structure
enables freedom.

Software shaped by systems, not trends.

A small line of
quiet products.

Each one starts as a recurring problem in our own work — then becomes useful enough to share.

Zen Forms

AI form and test builder.

LiveWeb

Zen Bot

A conversational layer over your docs and tasks.

ActiveWeb

Heart Stabilizer

Heart-rate stabilization for iOS + watchOS.

EarlyiOS + watchOS

Zen Cap

Calls captured, transcribed, and turned into usable memory.

BetamacOS

TRUTH OR DARE

iOS social game for honest conversations.

LiveiOS

Zen Transcriber

Lightweight transcription microservice.

ActiveAPI
LabsExperiments that may become products — or stay quiet.

AI Content Factory

Structured brief → structured output.

AI Music Platform

Compositional scaffolds for generative scores.

More in progress. We'll show them when they hold up on their own.

We design systems,
not features.

Clarity before interfaces.

Structure before surface.

Products small enough to maintain, deep enough to matter.

01

Substrate, not sheen.

Every product begins with a data model we'd be proud to publish. Surfaces come last, once the underlying grammar is correct.

02

Friction as signal.

Where a tool feels awkward, something upstream is wrong. We treat UX debt as a bug report for the system itself.

03

Small, forever.

Ten years matters more than ten thousand users.

Pick a system.
See the inside.

Four of our products, viewed from the same angle: the interface you use, and the structure that makes it work.

A reading layer that knows the shape of your docs.
Zen Bot sits on top of your existing documentation and treats it as a graph, not a blob. It answers from the grammar of your content — source-linked, context-aware, quiet by default.
How does the session-cache invalidate on a re-auth?
It rotates via rev 4.2 / session.ts:88 — a new auth event clears the cache key and re-keys downstream workers.

Built slowly.
Kept intentionally small.

Some products start as internal tools. Some become public. Some stay private. We care less about launching everything and more about keeping the systems clear.

01

Internal tools

Built first to solve our own recurring problems.

02

Public products

Released only when the system is useful beyond us.

03

Labs

Experiments that may become products — or disappear quietly.

Where limitations
quietly disappear.

You don't need to have it figured out. Say what the problem feels like — we'll help shape it into something clear.

E-mail directhello@zen.software
StudioR. da Boavista 117, Lisbon
AvailabilityQ3 · 2 slots open
Typical engagement6–12 weeks
Start with a voice note.
Speak freely. We'll turn it into a clear brief.