Nocturn designs, builds and runs web platforms, back-office systems and data products. Most of what we ship, we also operate — so it is built to survive Monday morning.
Selected work
Vertical SaaSLive
Leasing, maintenance, accounting and bank reconciliation for owners whose properties sit in separate LLCs — with the rules that protect financial history enforced by the database, not by application code.
02Developer APIBeta
Four checks that usually live in four tools, each running as its own service behind a single gateway: one base URL, one key, one contract, and one answer to “is this release safe to ship?”
03Data productLive
A property-intelligence platform covering all 81 provinces of Turkey: price per m², rent yield, demand and volatility by district, official central-bank housing indicators, an interactive map and a moderated community forum.
What we do
01 — Product engineering
Design, data model, build, deployment and the first months of operation — for founders and teams launching something new.
02 — Operations software
Back-office tools that replace the spreadsheet: ledgers, bookings, stock, point of sale — built around the rules your business actually has.
03 — Search & data
Programmatic SEO, ingestion pipelines and automated publishing — the plumbing behind sites that grow without a content team.
The products here are live, in beta, or in pilot — and marked accordingly. Open them, click around, try to break them.
Code, repository, domains and cloud accounts are in your name from the first day.
Progress is shown on a live URL you can click, not in a status report.
Anything that depends on a third party is labelled as such until it actually works.
Health checks, backups, error tracking and a rollback path ship with the first release.
Index
Notes
Manufacturers publish drills and grinders in PDFs, marketplace listings and prose. A comparison only becomes possible when every product maps to the same fields.
A news site does not fail because it lacks a CMS. It fails when the publishing stops. Notes from a finance site run by a scheduled Python pipeline.
Process
Step 01
Thirty minutes on what it has to do, who will use it and what already exists.
Step 02
A few pages: milestones, price, and — just as important — what is out of scope.
Step 03
Weekly demos on a staging URL. You can use the product from the first milestone.
Step 04
Go-live checklist and monitoring. Ongoing maintenance is optional and has no lock-in.
Nocturn