Web applications, from schema to deploy

Portals and platforms used every day. I design the database, build the API and the screens, and put it into production myself.

What it is

To me a web application is a complete system: data model, backend, interface, tests and the rollout. Not a few screens on someone else's API, but the whole of it, with one person who knows how it fits together.

I build in TypeScript, with Next.js and React at the front and PostgreSQL or MySQL underneath. A new version starts next to the old one and only takes over once the health check reports exactly that version.

What I build

  1. 01

    One system instead of separate tools

    The business portal brings quotes, work orders, invoices, planning, a shared inbox and the accounts together.

  2. 02

    Working together without overwritten work

    In Fyldd a change reaches everyone within a second, and whoever saves an outdated version gets a warning instead of silently lost work.

  3. 03

    Data that stays separated

    Row-Level Security in PostgreSQL as a second lock: 49 tables in Fyldd fall under it, so customers never see each other's data.

  4. 04

    Rules in code, not in a manual

    The Riha webshop refuses checkout in the 10 VAT territories it does not ship to, and the welcome discount only works while the real promotion exists.

  5. 05

    Background jobs that never run twice

    In the business portal 21 jobs hold a database lock, even during a rollout in which two versions run side by side.

A web application that needs building, or a team that is building one?

info@bitvire.com