← The six schools

Artifice · applications and tools

DevisNet

The tool my employer uses to answer calls for tender: from the catalogue of cleaning operations to the contract the client signs.

What it is for

Account managers build answers to calls for tender for workplace cleaning. They need a catalogue of operations and frequencies, contracts split into sites and rooms, a technical specification for each site, and clean documents to send. DevisNet holds all of it, from the first draft to the signed contract.

What I built

  • A library of operations and grouped operations, generic or specific to one client, with Excel import and export.
  • Versioned contracts with history, states, annexes, and a lot › site › room tree built from room templates.
  • A rich editor for the technical specification of each site, with photos and drag and drop, exported to PDF.
  • A separate client portal where clients read their contracts, sign them and discuss them in a chat.
  • Document storage in Nextcloud, isolated per client, with a personal account for each user.

How it is built

Blazor Server on .NET 9, Entity Framework Core over MariaDB, ASP.NET Identity. The internal tool and the client portal are two applications sharing one library, each with its own database. PDF reports come from JasperReports and SQL views. Tests are written with xUnit and NSubstitute.

Security and production

  • Two-factor authentication is mandatory, sessions expire every 30 days, permissions are fine-grained, and every change is written to an audit log.
  • Authorization tests run before each deployment. The deploy script runs the tests and can roll back.
  • It runs on a Linux server under systemd, with a runbook and a written production protocol.

What was hard

The hardest part was not a feature: it was serving two kinds of users at once. Account managers work inside the tool; clients and candidates come from outside. Each new request had to be placed on the right side, and every door to the outside had to be thought through before it was opened.

So I split it into two applications with separate databases, sharing only one library, and put security first: two-factor authentication, permissions per action, an audit log, authorization tests before each release. Security is not my first field; that is exactly why I treated it as a design question, not a finishing touch.

On the technical side, Blazor Server taught me one lesson the hard way: a database context shared by a whole connection fails as soon as two operations overlap. I moved to one context per operation.