Skip to content
SPEIA

Software architecture

Architecture first: what makes a tool hold.

A business tool lives for years. What makes it hold is not visible on screen: where the data is, how a version reaches production, how you go back, who decided what. Here are our rules — the ones that are applied.

In short

  • One database per client project
  • Candidate version checked before the switch
  • Backups restored and compared table by table
  • Every decision written and dated

Facts checked on 11 November 2026.

Rules

Eight rules, applied to every tool.

  1. One database per client

    Every tool delivered to a client has its own database; every SPEIA Immo subscriber has their own instance. No large shared database where a forgotten filter would show someone else's data.

  2. When the database is shared, it does the partitioning

    SPEIA Planning serves several companies in one database: partitioning is enforced there by PostgreSQL itself, on 16 tables, not merely by the application's code.

  3. Business logic lives in code

    What decides, validates and bills lives in readable, versioned, tested code — never in a prompt, never in a black box.

  4. No secret in the code

    Passwords and keys live in the server's configuration, never in the repository. A database's address is project data, not a constant.

  5. A version is never modified

    Every go-live creates a timestamped version. The candidate starts alongside the one in service, is checked, then replaces it in a single move; the old one stays there to go back to.

  6. An external action follows the write

    On our control platform, a message to send is recorded in the same transaction as the data that triggers it. If the write fails, nothing goes out.

  7. A backup only exists once restored

    Backups are restored into a throwaway database and compared table by table with the original. Tests on record in September and November 2026.

  8. A decision is written down

    Every architecture choice is recorded and dated, with its reasons and what it replaces. The architecture file is updated in the same piece of work as the change.

Technical choices

The stack depends on the need, not on habit.

20 technologies are used in the live projects; each one is listed with its references.

  • A website: static pages

    A showcase site is generated as static pages with Astro: it loads fast and has no database to maintain.

    The live sites
  • A business tool: an application and its database

    Next.js, TypeScript and PostgreSQL for the management foundation; Laravel, Filament and MySQL when a document-heavy back office is needed.

    The tools in service
  • A product: one instance per subscriber

    SPEIA Immo is installed for each subscriber: their database, their address, their nightly backup.

    SPEIA Immo
  • All technologies, with their references

    The list is derived from the references, not written: a technology only appears if a live project uses it.

    See the list

FAQ

Frequently asked questions

Why one database per client?

So that a programming error cannot show one client's data to another, and so that one client's data can be backed up or restored without touching the others.

What happens if a go-live goes wrong?

The version in service keeps answering until the candidate has passed its checks. If a step then fails, the procedure returns to the previous version on its own.

Are the tools isolated from one another?

Each tool has its folder, its process, its domain and its database. The server's hardware resources remain shared between the tools: we say it as it is.

Who decides on the architecture: you or the AI?

An engineer. AI agents write and verify; architecture choices are written decisions, taken by a person.

What if we started from the way you work?

One first conversation is enough to know whether SPEIA can help.