NINOVA LABS_
// 00 — MANIFESTO
const manifesto = {

Software should begin where the problem does.

Ninova Labs builds its own products — no client work — from frictions that already exist in the real world.

};
SEE THE RECORDS
ninova — build.log
$ ninova build --calm
resolving problem… found in real life
compiling sakin@0.9.4 … ok
compiling virdly@0.6.1 … ok
researching project-x … phase 01
ai.core … in the loop
# hype_modules: 0 · buzzwords: 0
ships when ready, not before
03
PRODUCTS IN BUILD
60+
UNITS ON LIVE OPS
0
CLIENT PROJECTS, EVER
// 01 — PRINCIPLES

The Ninova Compass

Four bearings we check before anything ships.

N

Problem first

A product starts as a friction in the real world, not as an idea for an app. If the problem can't be named in one sentence, it isn't ready.

E

Live with it daily

We run our products inside real operations — our own — long before anyone else is asked to trust them.

S

Layer by layer

Good software accumulates like an archive: release by release, kept in order, meant to last. No hype cycles, no artificial urgency.

W

Promise less

Calm software, calm words. Every claim on this page is one we can keep.

// TRUE NORTH — AI-NATIVE

Machine intelligence, human judgment

AI runs through the whole studio — it writes code alongside us, flags reconciliation anomalies in Sakin, and shapes gentle, personal rhythms in Virdly.

But it stays in the engine room. Models draft, humans decide; the product surface remains calm. Intelligence is leverage here, never spectacle.

// 02 — THE RECORDS

Three records, all in the making

archive.filter(record => record.problem.isReal())
RECORD 02.A — FILED UNDER: OPERATIONS COMING SOON

Sakin

Building management for commercial business centers

Dues and collections, account reconciliation, security patrol logs, tenant operations — the daily paperwork of a business center, kept in one calm system.

In Turkish, sakin means both resident and calm. That double meaning is the whole product.

DUES & COLLECTIONS RECONCILIATION PATROL LOGS TENANT OPS
FIELD NOTE

Used live, every day, in a ~60-unit business center the founder manages himself. The product and its first customer share an office.

RECORD 02.B — FILED UNDER: PRACTICE COMING SOON

Virdly

A spiritual habit companion for Muslims

At its heart is the Vird Planner: a gentle way to portion a daily practice — dhikr, reading, reflection — and keep it, quietly, over years.

Its thesis is old and simple: consistency over intensity. Small portions, kept gently, outlast grand resolutions.

VIRD PLANNER DAILY PORTIONS GENTLE STREAKS PRIVATE BY DEFAULT
FIELD NOTE

The most beloved of deeds are those done consistently, even if small. Virdly is software shaped around that sentence.

RECORD 02.C — FILED UNDER: INTELLIGENCE PHASE 01 — RESEARCH

Project X

An AI engine for serious book summaries — working title

A tool that reads whole books and produces summaries worth a scholar's trust — for academics, writers, and people who never stop learning.

Most of it is still undecided, and we like it that way. The potential is large; the claims will wait until the work has earned them.

AI-CENTERED BOOK INTELLIGENCE SCHOLAR-GRADE NAME PENDING
FIELD NOTE

A library that reads with you. The oldest ambition in the archive, and the newest record in it.

// 03 — ENGINEERING

How the records are kept

+ 3.1 merged

Boring, proven technology

Stacks chosen to still make sense in ten years. Novelty is a cost we pay only when the problem demands it.

+ 3.2 merged

Small releases, real changelogs

Every version ships with a legible record of what changed and why. The archive stays honest.

+ 3.3 merged

Operated, not just written

Monitoring, backups and reconciliation are product features, not afterthoughts. Software that runs a building has to run itself first.

+ 3.4 merged

Data stays yours

Clean exports, no lock-in tricks, privacy by default. A good archive can always be carried out of the building.

// 04 — THE STUDIO

A note from the founder

$ cat founder-note.md

Ninova Labs is an independent product studio in Istanbul. The name looks back to ancient Nineveh and the library of Ashurbanipal — knowledge gathered layer by layer, kept carefully, meant to outlast its keepers. That is how we build software: patiently, in layers, with records that stay legible years from now.

Both products in this archive began as problems we could not ignore in our own daily life — a business center managed every morning, and a spiritual practice kept every evening. We build them slowly, use them daily, and ship them when they are calm enough to trust.