← All projects
Individual developmentVisit project (new tab)

De Fato

Facts, context and evidence with independent review.

Identified technologies
.NET / C#Next.jsPostgreSQL

My contribution

Design, architecture and 100% of development to this stage, within a project with partners and repository collaborators.

People and partnership

Development and partnership.

A project in partnership with Fábio Henrique, Wellington M. F. Zambelli and Diogo Nunes. At this stage, Breno Mayder has done 100% of development. The partners are repository collaborators. GitHub access is not presented as a code contribution.

Diogo Nunes

Partner · repository collaborator

Development partner on CondoVia, owner of the CondoFlow repository and partner on De Fato.

GitHub Diogo Nunes (new tab)

Credits provided by Breno Mayder · 2026-11-01

Architecture overview

A modular .NET monolith, Next.js UI and PostgreSQL. Contributions and review use separate roles and permissions.

Technical structure

Technology by module.

The modular backend and web are separate processes, with domain rules in the API. A mobile app remains planned.

What each part does and which technologies support it. A module in the code does not mean all its features are complete or published.

01 / Existing code

API

C#ASP.NET CoreEF CoreNpgsql

API, authorization and domain rules.

A modular backend organizes use cases and storage. SQL controls the schema without automatic ORM DDL.

02 / Existing code

System

Next.jsReactTypeScript

Browser access and interaction.

The web presents states and sends operations to the API. It does not duplicate domain rules in UI components or routes.

03 / Existing code

Data and contracts

PostgreSQLSQLContracts

Data and shared contracts.

SQL scripts and explicit contracts support API, web and operation integration.

04 / Planned

Mobile app

FlutterDart

Planned mobile surface.

Technology selected for future work. Not presented as a delivered or published app.

How the parts connect

The browser uses an authorized web/API boundary. Domain rules stay in the backend. The UI does not access PostgreSQL or private files directly.

Data and integrations

PostgreSQL with EF Core/Npgsql mapping. SQL scripts control the schema, with access isolation and authorization for each operation.

Quality and operations

Access and contract tests, per-surface checks and deployment procedures. Planned features and existing modules remain clearly separate.

Skills in this project

Languages and backend ↗Web, mobile and experience ↗Databases and integration ↗DevOps and delivery ↗Architecture, quality and AI ↗
Let’s build something

Do you have a similar challenge?

Tell me what you need. The WhatsApp draft includes this project as a reference. You can edit it before sending.

Talk on WhatsApp ↗
/→

Keep exploring

Contact

Good work starts with a conversation.

Let’s talk