Skip to content
PL

Undernapse / Work

Work you can check.

Two projects, two different scales: an operating system for salons and a website for an ayurveda practice. For each one we show the scope, the stack and what you can look at yourself.

13

weeks

since Vezori’s first commit

633

commits

in the Vezori repository

122

test files

Vezori: 111 unit and integration, 11 acceptance

12

pages

the SomaVeda site, no app dependencies

As of 5 November 2026

An operating system for beauty and hair salons: appointments, client records, inventory, checkout and the real margin behind every service.

The challenge

A salon often keeps its calendar in a paper book, its till in a spreadsheet and its client records in a separate program. The owner does not know which services actually earn money, because material costs are estimated rather than counted. We set out to put the day, the client record, stock and finance into one system where margin comes from actual consumption, not from a percentage typed into a price list.

What we built

  1. Owner and manager panel

    Today’s queue of things that need action, a calendar, client records, checkout, finance with margin, inventory and settings. One system instead of several browser tabs.

  2. Public booking pages

    A client books from a phone without creating an account, then moves or cancels the visit themselves. Nothing to install.

  3. Margin from recipes, not price lists

    Material cost is calculated from actual consumption and stock movements. The specialist approves exceptions but never types usage by hand.

  4. Money recorded as it actually is

    PayNow deposits with an upper cap, prepaid passes recorded as a liability to the client, and an append-only ledger. A closed sale changes only through a correction document with a required reason and author.

  5. Health data with separate access

    A treatment record is special-category data: separate permissions, consents appended with a withdrawal history, and a full audit trail.

  6. Imports that do not block the panel

    Encrypted background jobs read CSV and XLSX files up to 100 MB and 500,000 rows. The file is removed after parsing, and the preview shows the plan before anything reaches the database.

How we worked

Thirteen weeks from the first commit. We work with AI agents inside the repository: code generation, migrations and tests move faster, while architecture decisions, code review and accountability for every change stay with the engineer. That is why the repository contains an AST gate that blocks database access outside a single layer, and tests for data isolation between salons.

What you can check

  • We show the panel, the booking pages, a spreadsheet import and a margin calculation live.
  • Tests, migrations and product documents are opened in the meeting — we do not just talk about them.
  • Technical decisions carry written rationale in ADR documents. We show them together with the trade-offs.

Straight answer

Vezori is built toward a pilot, not a public launch — that is why there is no user count and no revenue impact here. Fiscal receipts and KSeF are designed but not implemented yet, so they are not in this list either. What there is: scope, architecture and 122 test files you can open.

A website for an ayurveda practice in Łódź: twelve pages, an editor the owner runs herself, and a contact form that does not pretend to send a message.

SomaVeda Ajurweda home page: dark green typography and a photo of the practice
The delivered site — home page

The challenge

The brief: a site the owner can run herself, with no developer for every change. Bio, offer, FAQ, company details, hours, photos and cancellation rules all have to be editable in one place, without anyone hand-holding the layout. The content concerns health, so nothing unverified can appear: no therapy names, prices or durations until the owner confirms them.

What we built

  1. A static site with no application dependencies

    HTML, CSS and JavaScript without a framework, database or API keys. Deployed to Cloudflare with no application server to maintain.

  2. An editor for the owner

    Fields for the bio, offer, FAQ, company details, hours, photos and cancellation rules. Saving rebuilds the preview, previous versions are backed up, and the editor never ships to production.

  3. Only confirmed content goes live

    Every therapy has a “confirmed — publish” switch. Without it, the therapy appears neither on the page nor in structured data. Names, prices and durations the owner has not confirmed do not exist in the code.

  4. A form that says what it does

    It composes an email and opens the visitor’s mail app. There is no fake success state, no stored submission and no sending server. Phone and email work without JavaScript.

  5. Brand, SEO and maps without surprises

    Canonicals, sitemap, unique titles and descriptions, Open Graph, LocalBusiness with the tax ID, and Service and FAQPage data matching the visible content. Own logo system, favicon, Apple icon, 1200×630 social image and self-hosted WOFF2 fonts.

  6. Tests for structure, SEO, content and the form

    Tests run against the built pages: links, metadata, content presence, the form and the legal pages. The 404 page always stays out of the index.

How we worked

A project with no application dependencies: static HTML, CSS and JavaScript, no database and no API keys. The things that usually drift in sites like this — metadata, the map, the privacy policy — are held by the build scripts and the tests. The owner gets an editor that runs locally, with backups of previous versions. Publishing stays a deliberate decision, not a side effect of a click.

What you can check

  • Content, phone and email work without JavaScript, from the first visit.
  • Structured data matches the visible content — check it with a validator, not with our word.
  • The editor and the tests are part of the project; we show both in the meeting.

Straight answer

Vezori booking is wired but disabled until launch. The main buttons lead to contact instead of promising slots that do not exist. The form does not fake a send. That is deliberate: the page tells the visitor exactly what will happen after the click.

What it proves

What this means for your project

01

Scope that holds up

In Vezori, appointments, checkout and margin are one system; inventory and imports are connected to them, because otherwise margin would be a guess. We add the features that close the loop, not the ones that look good in a demo.

02

Rules that survive daily use

A closed sale changes only through a correction document, and every database access goes through a single layer. Rules like these cost something at the start and save months on the first serious mistake.

03

We say where the limits are

SomaVeda publishes no unconfirmed therapies or prices, and its form does not pretend to send a message. A site that says what it does not do earns trust faster than one that promises everything.

Next step

The next project could be yours.

Tell us what you want to build and where you are now. In the first conversation we work out whether you need a product, an AI implementation or a website — and what makes sense as a first step.

Let’s talk about your project
Book a callAI readiness