Skip to content

Architecture

In a few words: a screen, an organizer, the agents and a record, in an isolated environment for each project.

flowchart LR
    VOCE["You<br/>(browser)"] -->|"protected access"| TELA["Husvord screen<br/>requests, board, cards"]
    TELA --> ORG["Organizer<br/>hands out and follows up"]
    ORG --> AG["AI agents<br/>each with its own role"]
    AG --> ORG
    ORG --> REG["Record<br/>of everything that happened"]
    ORG --> NOAR["Delivery, live"]
Piece What it does, for the buyer
Screen Where you ask, follow up and approve. Works in the browser and on the phone.
Organizer Receives the requests, splits them into steps, hands them out to the agents and makes sure nothing gets stuck.
AI agents Do and check the work. Each one has a fixed role and only touches what belongs to its job.
Record Keeps every step and every decision, with no way to delete or change them later.
Delivery Takes the result to production after the tests and your approval, and rolls back by itself if something goes wrong.

Security and isolation

  • A dedicated machine for each client. The core that coordinates the platform is shared and lean, but each client's work runs on a server dedicated to it, not shared with any other client.
  • A separate entrance for each client. Each project has its own address, in the format 001-floor-tower-00001.husvord.com, and a client's entrance is isolated from the others: turning a client on or off does not affect any other.
  • One environment per project, separate from the other projects.
  • Encrypted secrets (passwords, keys and tokens are never kept in plain text).
  • Optional high availability, for those who need the environment to never stop.
  • Protected access: the screen only opens after identity verification, with corporate sign-in (Entra ID and Google Workspace, with SSO, plus GitHub and Google), and approvals ask for a password.
  • Nothing exposed for no reason: the environment opens no ports to the internet; only the essentials go out.
  • Client data stays with the client: Husvord's operations panel only sees whether the environment is healthy, never its content. A project can even run on the client's own infrastructure.