Nomvel

Software company/Delaware, USA

We build software we keep.

Nomvel is an independent software company. We build internet products we own, run them on our own infrastructure, and answer to the people who use them. We are not an agency and we do not take outside work.

1.0001.105N—01DRAWINGGEOMETRYREVISIONNOMVEL / MARK45.00°2026.06SCALE 1:1ZYLOO, LLC — DE, USA
Established
2026
Model
Independent, self-funded
Entity
Zyloo, LLC
Products live
First in build
Owned end to end. No outside work. No trackers. No data resold. Self-funded. Small on purpose. Built to be kept. Operated in-house. Privacy by default. Boring technology.
01Products

Software we own.

Everything here is ours end to end — the idea, the code, the infrastructure, and the relationship with the people who use it. Nothing is built to be handed over or flipped.

01

Vypulse

Soon

Privacy-first website analytics.

vypulse.io

Measurement that tells you what you need to know about your website without following your visitors around the internet. No cross-site profiles, no advertising identifiers, no data sold on.

Category
Web analytics
Model
Subscription
Stage
In development
02

Unannounced

In planning

We start the next one when the last one can stand on its own.

02Practice

Four things, done properly.

A deliberately narrow practice. When you own the product, there is nobody to hand the hard parts to.

01

Product architecture

Tenancy model, data boundaries, permissions, billing. The decisions that are cheap in week one and structural by month six — and that we are the ones living with.

  • Domain modelling
  • Multi-tenancy
  • Permission design
  • Billing
02

Interface engineering

Design systems written as code. Typed components, real empty states, keyboard paths, and accessibility treated as part of the build rather than an audit at the end.

  • Design systems
  • Component libraries
  • Accessibility
  • Motion
03

Platform & delivery

Infrastructure a small team can reason about at 3am. Pipelines, environments, migrations, and enough observability to trust a deploy on a Friday.

  • CI/CD
  • Environments
  • Observability
  • Cost control
04

Operating

The part that never ends. Uptime, performance, security patching, support, and the roadmap that only becomes obvious once real people are using the thing.

  • On-call
  • Performance
  • Support
  • Roadmap
03Method

Build the risky part first.

Most software fails late because the hard decisions were deferred. We invert the order: infrastructure and edge cases at the start, polish at the end. It feels slower for a fortnight and then it never does again.

  1. 01Weeks 1–2

    Frame

    We pull the problem apart before writing anything. Who it is for, what it refuses to do, and the one number that tells us whether it is working.

  2. 02Weeks 3–6

    Spine

    The riskiest path gets built first — accounts, data model, billing, permissions. If something is going to break the product, it breaks now, while it is cheap.

  3. 03Weeks 7–12

    Surface

    Interface, states, edge cases, empty screens. The version we would be willing to put our own name on, because we are about to.

  4. 04Indefinitely

    Operate

    Production, monitoring, support, and the pager. This phase has no end date, which is exactly why the first three are done the way they are.

04Principles
  1. I

    Boring technology, aggressively applied.

    We pick tools with a decade of answered questions behind them. Novelty is a cost, and we are the ones who pay it at 3am.

  2. II

    The customer is the business model.

    Our products are paid for by the people who use them. No advertising, no data brokerage, no third party whose interests quietly outrank yours.

  3. III

    Scope bends. Quality does not.

    We would rather cut a feature than ship a compromised version of everything. Nothing goes out under our name that we would not want to maintain.

  4. IV

    Built to be kept.

    We are not building to be acquired or to hand anything over. Every decision assumes we will still be running this in ten years, because that is the plan.

05Contact

Say hello.

We do not take client work, so there is no sales pipeline to get through. If you have a question about what we are building, or you need help with something we run, write to us and an engineer will reply — usually within one working day.