Category: Status Updates

  • Supply-chain scanning is live

    Every container image running on this fleet is now scanned for known vulnerabilities, and the results are tracked in one place instead of living only in whatever tool happened to print them at build time. That answers a question this…

    Read on →

  • Status: workflow automation live, the gateway console behind SSO

    Workflow automation joined the productivity tier, and the local language model gateway’s admin console is now reachable through single sign-on instead of a shared key. A photo library was also started, and stopped almost immediately by something smaller than a…

    Read on →

  • Status: the first services meant for people

    Everything built so far has been infrastructure for the lab’s own benefit: gateways, tunnels, DNS, identity, monitoring, backups. Useful, and none of it something a person opens on purpose.

    Read on →

  • Status: the lab stops being one machine

    The second physical server is online. For the first time this project is not one computer with a lot of ambition attached to it.

    Read on →

  • Status: the identity tier is up

    Single sign-on is running. That is the tier everything above it has been waiting on since the architecture was written, and the one the runbooks warn against skipping in the strongest terms available.

    Read on →

  • Status: the loop is closed

    The tunnel from the rented edge to the house is up and carrying traffic. That was the last structural piece of the original design never exercised end to end, and it has now been exercised in both directions.

    Read on →

  • Status: the first VMs, and the tier they unblock

    Three virtual machines exist. After weeks of rented gateways and documents, something is finally running on hardware in the building.

    Read on →

  • Status: first contact with real hardware

    Two things happened that had not happened before. The standby gateway in Europe exists, which completes the pair at the edge. And a physical server was brought online for the first time, which ended the long stretch of this project…

    Read on →

  • Status: alerting that can actually reach you

    Two days on the public edge and no new hardware. The alerting path is now proven end to end rather than merely deployed, which is a distinction this project keeps having to relearn. It produced four more errata along the…

    Read on →

  • Status: tier one, the edge is up

    First status update, so it doubles as a baseline: this is where the lab stands on the day the site went up.

    Read on →