Security and architecture

    Built to be secure.Explained in the open.

    How Staub IT's AI employees are built, where your data lives and who can access what. Including the residual risks that remain.

    As of September 2026 · applies to the standard setup of Staub IT's AI employees

    Your team

    each with their own AI employee

    • You
    • Colleague
    • Colleague

    Slack or Teams

    private channel

    Your own server

    European data centre, ISO 27001

    Firewall: all inbound closed
    • AI employee
    • AI employee
    • AI employee

    Company memory

    Shared company knowledge
    Private, separate per person
    Internal services · reachable only on the server
    • Microsoft 365

      Mail, calendar, files

    • AI models

      only the snippet needed

    • Knowledge database

      encrypted, usually Zurich

    • Backup

      every 30 minutes, your account

    Maintained by Staub IT

    private network and keys only

    Every connection is encrypted. The server opens them itself, outbound.

    How a request flows

    Why that is safer

    • No black box

      Experts anywhere can review every line of code. Vulnerabilities are reported publicly and fixed quickly.

    • No lock-in

      You are not tied to a single vendor. Software and data run on your accounts and stay usable.

    • Proven, not homegrown

      The foundation is widely used and battle-tested. Staub IT adds what your operations need.

    • 4×automated health checks a day
    • 1 hcycle for collecting errors
    • 30 mincycle for versioned backups
    • at nightlarger updates and reboots

    Ask us what's missing here.

    We're happy to walk through the architecture with you or whoever runs your IT, point by point.

    hello@staub-it.ch