The Problem

A restoration project rarely starts from a blank page. It starts from a filing cabinet, a shared drive with three different folder naming conventions, and a box of scanned surveys from the last renovation in the 1990s. When a structural engineer asks "what did the original masonry survey say about the north wall," someone has to remember which subfolder holds the answer, or open forty PDFs one by one.

This is where projects lose weeks. A senior architect ends up doing the job of a search engine: flipping through hundreds of pages of handwritten site notes, scanned Soprintendenza permits, and photogrammetry reports just to confirm one measurement. Every hour spent searching is an hour not spent designing or supervising the site.

The obvious fix, uploading everything to a cloud AI tool, creates a new problem. Heritage restoration files often include client property details, structural vulnerabilities of protected buildings, and permit correspondence with public authorities. Sending that into a general purpose cloud model means the data leaves your control, and under the EU AI Act and Italian data protection rules, that is a risk few studios can justify.

The Noot8 Solution

Noot8 is a small edge appliance that sits on your studio's network. Unbox it, connect it, and start asking questions. There is no server to configure, no IT consultant to hire, and no software to install on every workstation. It reads what your team already has: scanned survey binders, CAD exports, PDF reports, site photos, and permit files, and turns all of it into one searchable knowledge base.

Eye Cortex: Vision That Reads Drawings, Not Just Text

Most document search tools choke on the kind of files a restoration studio actually produces: hand annotated survey sketches, tables inside scanned engineering reports, and photographs with measurements written directly on them. Noot8's Eye Cortex engine is built for exactly this. Running on a 4 billion parameter ColPali visual model, it reads a page the way a human eye does, understanding layout, handwriting, diagrams, and photos together, rather than relying on brittle text extraction that breaks on anything but a clean digital PDF.

That means your team can ask questions in plain language and get answers pulled directly from the visual content of your archive, including:

• Heritage restoration dossiers, including Soprintendenza permits, conservation notes, and historic material analyses.
• Site survey photographs and field notes, with handwritten measurements and annotations preserved and searchable.
• Structural engineering reports, including load calculations, crack mapping diagrams, and monitoring data tables.
• Scanned architectural drawings and cadastral maps, even where the original files no longer exist.
• Photogrammetry and laser scan summaries, cross referenced against older paper based surveys of the same building.

Privacy Guarantee

This is not just a privacy policy. It is a physical guarantee. Noot8 is a piece of hardware that lives inside your studio, connected to your own network. Every document you feed into it, every survey photo, every structural calculation, every restoration permit, is embedded, indexed, and stored entirely on that device.

Processing happens 100% locally. There is no upload step, no background sync, and no cloud storage of your files at any point. When a question genuinely benefits from broader reasoning, only the small retrieved excerpt needed to answer it is sent out, under Google's enterprise data processing agreement, restricted to EU infrastructure, never stored, and never used to train any model. Your full documents, and everything confidential inside them, never leave the building.

For studios working on protected heritage buildings, where client details, structural vulnerabilities, and public authority correspondence all sit in the same archive, that distinction matters far more than a checkbox in a vendor's terms of service.

What Architecture & Design Professionals Use Noot8 For

• Prepping for a Soprintendenza review. Pull every relevant permit, prior conservation note, and material analysis in minutes instead of rebuilding a paper trail overnight.
• Comparing decades of surveys. Ask how a facade's crack pattern has changed since the last structural monitoring report, without manually lining up five scanned binders.
• Onboarding a new team member. Let a junior engineer or architect ask questions about a building's history directly, instead of interrupting a senior colleague for context.
• Cross checking site photos against drawings. Find the exact survey photo that corresponds to a detail in an old structural drawing, even when neither file is labeled clearly.
• Responding to client questions fast. Answer a client's question about a restoration timeline or a structural finding during a call, with the source document pulled up on screen.