Beex

Business teams spend their time patching together spreadsheets, forms and internal tools that don't talk to each other. Beex starts from a simple idea: give them blocks they assemble themselves to build those tools, without waiting for a developer. It's the product we created HDM-SOFT for, in August 2024.

The challenge isn't only technical. A no-code product has to be flexible enough to cover cases nobody planned, and structured enough that a non-technical user never gets lost.

I'm a co-founder and full-stack developer. On the front-end, I own the module architecture: each feature is an isolated bounded context, with its entities, use cases and components, and strict dependency rules between layers. I also wrote the conventions the team applies in code review.

On the product side, I take part in the trade-offs: what we build, what we refuse, in what order.

The front-end is a React and TypeScript application split into modules, each organized in four layers: domain, application, infrastructure, UI. Network calls go through a shared HTTP client, DTOs and mappers, so the domain never depends on an API format.

The back-end exposes business services and a PostgreSQL database. Everything is containerized and deployed on Kubernetes, with versioned images and a CI/CD pipeline on Azure DevOps.

Structuring a shared codebase from day one is expensive at first and pays off with every new feature. Written conventions beat spoken ones: they can be read, discussed and enforced in review.

I also learned that a no-code product is first an interface design problem. Code is only half the work.