Start free

    Solutions · Living Architecture · In development · pilots open soon

    A map of your systems that stays alive.

    Your body keeps a map of itself and updates it as you move. Living Architecture does the same for your infrastructure: your systems, what connects to what, the evidence behind every fact, kept current by your own people and your own AI.

    And when it must respond: the Immune System

    Live software we run on our own estate. Customer pilots run on a mirror of three of your systems that we build and run.

    A map of systems builds itself from three sources: a document, a workshop answer and a connector. Each system lands with a pin for its source. One system's version changes, the threat assessment on the system next to it turns amber because it is out of date, and the Owner's tick brings it back.DocumentsWorkshopsConnectorsSign-inCustomer portalOrdersPaymentsDatabasev 4.2v 4.3Assessment currentAssessment out of dateOwner
    Illustration · A fact with its source Out of date after a change

    Your body keeps a map of itself.

    One system in focus with a source card pinned to it: a line from a document, the person who confirmed it and the date. Two neighbouring systems carry pins of their own. One link nobody has described is drawn dashed and marked unknown.Link: unknownCustomer portal runs in the EU zoneSource: architecture overview, page 4Confirmed by the service owner12 October 2026Customer portal

    Biology: proprioception. You know where your hand is in the dark.

    Every fact on the map has a source.

    Which systems you run, what they connect to, which data sits where, who owns each. Living Architecture holds them as a map, and behind every fact sits the document, the answer or the record it came from. Nothing unconfirmed is shown as fact; an unknown stays marked unknown.

    In your estate

    The map is built from your documents, from workshop answers your Owner gives an agent, and from read-only connectors to tools you already run. Each import quotes its source and is checked against the source text.

    A warning card at the edge of the map, a new vulnerability with a version string. A signal travels along one vessel to the one system that declares that version, which lights amber with a tag: potentially affected. The systems behind it on the route tint faintly. The rest of the map stays at rest.Potentially affectedNew vulnerabilityVersion 5.2 affectedCustomer portal

    Biology: a nerve carries the warning to the place it concerns.

    A warning lands where it matters, not in your inbox.

    A new vulnerability or a new rule arrives every day. The map shows which of your systems it touches, which data sits behind them and who owns them, so the person who decides sees the question in their own terms.

    In your estate

    Vulnerability feeds are matched against the software versions your map declares. A match is affected, potentially affected or unresolved; against a declared list it reads “declared version potentially affected” until your owner confirms what actually runs. Regulations and standards are matched the same way, through scoped assessments on your frameworks.

    A proposal card: change to the map, new version on Customer portal, proposed by an agent from the deployment record. The Owner's tick approves it. Beside it, the change-control dial with three stops, Strict, Balanced and Open, set to Balanced.Change to the mapNew version on Customer portalProposed by an agentSource: deployment recordApproved on TodayOwnerStrictBalancedOpenBalanced, the default

    Biology: healing under control. The body repairs itself without rewriting itself at random.

    Every change to the map is a proposal.

    Your people and your agents propose changes; your Owner approves them in one place, Today. One setting decides how much agents may apply on their own: Strict, Balanced or Open. Balanced is the default.

    In your estate

    Strict holds every change for a person. Balanced lets agents apply what a source states and holds what an agent inferred. Open lets agents apply more, above a fixed floor of changes that always needs a person, in every mode. Each agent run reaches your Owner as one entry, not a pile of items. Every applied change carries who proposed it, which source, and when, and can be reverted item by item.

    A system that changed shape, its old outline dashed beside it. The threat assessment attached to it has turned amber: out of date. One threat, drawn once, is linked to this system and to a second one; it is not copied.Changed this weekAssessment out of dateSecond systemOne threatRecorded once, applied to each system

    Biology: scar tissue remembers.

    One threat model for the whole estate, that knows when it is stale.

    Threats are recorded once, by what they attack and how, and applied per system. When a system changes, the assessments that depend on it are marked out of date, so your threat model never quietly goes wrong.

    Re-checking stale assessments automatically is in development.

    In your estate

    The register holds one scenario per mechanism and protected object; look-alikes are held for a person, never merged by a machine. Every conclusion is recorded against the exact inputs it rests on, and when one of those inputs changes, the map flags the conclusion on Today.

    Confocal micrograph: a dense web of glowing orange nerve fibres on black, with a few cell bodies where the fibres meet.
    Nerve fibres of brain cells in culture, each a line that carries a signal to one place · Photo: MikeRoscopy · CC BY 4.0

    One warning, answered on the map.

    A fictional company's map: the internet, a proxy, a customer website and an order system, with sign-in and payments beside them.PHP 8.3 · running, confirmed by the ownerInternetProxyCustomer websiteOrder systemSign-inPaymentsCould reach nextnot part of the verdict

    The version matches, the route is reachable, the owner confirmed what runs: exposed now. Next door sits the order system, shown for planning only. Exposed now: version matches, route reachable from the internet, owner confirmed what runs. The order system could be reached next; it is not part of the verdict.

    The advisory rows are a recorded Ansvar run from 28 October 2026. The company and its map are fictional; the route and the owner's confirmation show what the pilot builds for your systems. Nothing here changes a system.

    We run Ansvar on it.

    Our own estate lives in a Living Architecture twin. Our threat register has been kept there, as the authoritative one, since 2 November 2026, and every change to it goes through the same proposals and the same Owner approval we offer you.

    Read how we run Ansvar

    The brain seen from above as a mass of fine fibres coloured green, blue and violet by direction, with a red band of fibres crossing between the two halves.
    The brain's own wiring map, its fibres traced by diffusion MRI and coloured by direction · Photo: Andreashorn · CC BY-SA 4.0

    Regulators expect it. Attackers move faster.

    • Cyber Resilience Act, Art. 13

      From 11 December 2027, product makers document a cybersecurity risk assessment and keep it updated while the product is supported.

    • NIS2, Art. 21

      Essential and important entities need policies on risk analysis and information system security.

    • DORA, Art. 8

      Financial entities assess cyber threats continuously, and all but microenterprises repeat the risk assessment after each major change to their ICT systems, processes or procedures.

    • Microsoft Digital Defense Report, October 2026

      Under 24 hours from a flaw found in the wild to a working exploit (median), and 30 to 60 days for a company to fix a critical external vulnerability. A threat model reviewed once a year cannot keep pace.

    Where it stands, in November 2026.

    Live today

    Running on our own estate.

    The map, the Today inbox, the three change-control modes, the threat register, scoped assessments on your frameworks and vulnerability matching over declared software are live software we run on our own systems every day.

    In the pilot

    Your map, built with you in about two weeks.

    We build your map from your documents and two one-hour sessions with your Owner, match your declared software, run the assessments for your frameworks, and attack and defend a mirror of three systems you choose. A person approves every change.

    In development

    Re-checking, learning, responding.

    Re-checking stale assessments automatically. Learning your systems' normal from their own traffic. The response layer, the Ansvar Immune System, with its own page.

    A pilot of about two weeks, without touching production.

    You describe your systems. We build the map and a mirror of three systems you choose, attack the mirror, and defend it live with you in the room.

    Two servers we run for the pilot. The twin server holds your documents and your map, and the map shapes the mirror on the range server. There is no line from either to your production systems.Twin serverYour documents and your mapMap shapes the mirrorRange serverThe mirror we attackNo line to your production

    You bring descriptions.

    Architecture documents, a list of the software you run, two one-hour sessions with the person who owns the systems, and the three systems you care about most. No access of any kind.

    We run everything.

    Two servers we operate for the pilot only: one holds your documents and your map, the other holds the mirror we attack. Torn down at the end, with the deletion recorded.

    You keep the results.

    Your map, exported to you. A readout of what the attack-and-defend sessions showed. A plan naming which of your tools would replace each stand-in.

    About six hours of your time.

    Over about two weeks. The shape is a proposal and we confirm it with you before we start.

    A pilot starts with an NDA and a pilot data-processing agreement. We never touch your production systems, logs or credentials.

    You stay in control.

    Every claim has a source.

    Follow any finding back to the record behind it.

    Unknowns stay unknown.

    Nothing unconfirmed is presented as fact. A link nobody described is marked “auth: unknown”.

    People decide.

    A named person approves each response. Ansvar does not change your systems by itself.

    It runs where you decide.

    The pilot runs on a mirror we operate, never on your production. After the pilot the product runs in your environment, standalone or on your own platform, and your map comes with you, exported. Only the pilot runs on Ansvar's side.

    Start with three systems.

    One conversation about the systems you care about most. Bring a diagram and one recent change.

    How a partnership works