catalog growing Need a module that doesn't exist yet? Missing a module? ask for it
About us

We reached transversal modular architecture the long way.

Zennith Techlabs delivers management software in blocks. The method behind it was not born on a drawing board: it came from years delivering payment systems in Latin America, migrating legacy code and pushing every architecture style to the point where it starts to hurt.

See the catalog →

How we got here.

Each step solved a problem and created the next one. Today's architecture is what was left after all of them.

2022 — 2024 · Payments, LATAM
Hexagonal, monoliths and legacy migration
Large projects in the payments industry, at mid-sized and large companies across Latin America. Hexagonal architecture, monolithic systems and the routine of migrating legacy code to modern technology — which is where you learn, in practice, which boundaries survive a change.
Then
Products as modulith
Modular monoliths: a single artifact to run and deploy, but with real internal boundaries between domains. The end of the tangled monolith without the operational cost of a fleet of services.
Then
Microservices with a gateway — and modules inside
Microservice architectures with a gateway unifying what comes in and out. The detail that turned the key: inside, each service was still organised in modules. The unit holding everything up was not the service — it was the module.
Late 2025 · The synthesis
Transversal modular architecture
A module with an explicit contract, cutting across the whole system instead of living on one floor of a layer. We did not invent the method — several players in the market work this way. What was ours is the road to it.
February 2026
ZennGov in production
The first implementation of transversal modular architecture, designed for the public sector: city halls, agencies and the routines the law requires.
August 2026
The elasticity showed up
It became clear that what had been built was generic enough to leave the public sector and serve companies — no fork, no rewrite. What started as ZennGov became Zennblocks.

What transversal architecture changes in practice.

Four direct consequences — and they are what you feel while using the product, not the diagram.

The contract comes before the code
Each module declares what it does, who may use it and which routines it triggers. The menu, the permissions and what stays enabled for each client all derive from that contract — not from a hand-written list.
Transversal, not layered
A routine cuts across modules and people: it starts in one department, passes an approval in another, ends in a third. From the inside it is one flow, not three integrations.
Switch on and off per client
The same code serves whoever uses two blocks and whoever uses ten. Nobody becomes a parallel version to get one more module — and so nobody is left behind on an update.
What is common stays common
Login, permissions, audit trail and billing belong to the system, not to each block. Configuring once holds for every module that comes later.

Three products, one architecture.

Zennith Techlabs Ltda keeps three products today. The first two are where the method came from; the third is the method applied from scratch.

OttoWallets
Digital wallets. It moved from modulith to microservices with a gateway — it was while building this product that the central piece of the method appeared.
ZennPay
Payments.
Zennblocks
Management software in blocks, for companies and public agencies. It was born as ZennGov, in production since February 2026. It is this site.

Who came up with it.

Alan Delon
Founder · Software Engineer

Author of the transversal modular architecture and directly involved in the architecture decisions of all three products. Before that, years in large payment projects across Latin America: hexagonal, monoliths, legacy migration, moduliths and microservices with a gateway — in that order, and it is from that sequence that the method came.

LinkedIn profile →

Where the ideas come from.

None of the pieces was invented here. These are the texts that hold up the decisions — worth reading for anyone who wants to check the reasoning.

Hexagonal Architecture — Alistair Cockburn cockburn.us Monolith First — Martin Fowler martinfowler.com Strangler Fig Application — Martin Fowler martinfowler.com API Gateway — microservices.io microservices.io

Want to know whether a block solves your case?

Describe the routine in one sentence. We send back the module scope within 48 hours.

Talk to us →