Blog · Build log · Published August 20, 2026 · Updated September 13, 2026 · James Forrester

The infrastructure weeks

Most of August at threndle.ai went into work clients never see: the servers, the architecture, and the operational and legal footing the business runs on. This log records where that work stood on August 20, with an update from September 13 at the end.

It had to come first. Client work can only move at the pace I want once the systems underneath it are dependable, so that is where the time went.

The servers are up

A dedicated VPS now runs our Hermes instance. Systems that used to run on my own machine now run on proper server infrastructure and keep running whether or not I am at my desk. That independence is what allows a client to depend on the work.

Tools our clients can use, inside Cowork

The same servers host tools we provide to clients: SEO analysis, marketing insight, and social intelligence. They run on our infrastructure and connect directly into Cowork, the environment our clients already work in. Each tool runs inside a Docker container isolated from the rest of the server, so a fault inside the container cannot spread beyond it.

The design follows from how Cowork works. Cowork is a sealed, secure environment and does not call outside tools by itself. The only way to give it a new capability is an MCP connector, a defined and permissioned link between Cowork and a specific tool, which is why each of these tools is built as an MCP server. Clients get SEO and social data inside the environment they already trust, and none of their work has to leave it.

The architecture is taking shape

The overall structure is settling. The website, the knowledge base that runs the business, and client work each have a defined place, which keeps the operation organized as it grows.

threndle.ai is moving to master service agreements and statements of work. The MSA sets the terms for the whole relationship, including confidentiality, the handling of client information, liability, and payment. Each statement of work sits beneath it and spells out a single engagement: what will be built, what it costs, and when it will be delivered.

This matters more for us than for most businesses. When threndle.ai connects to a company's books, inbox, and CRM, that company should know exactly what has been agreed before the work begins. A written agreement turns an informal favour into a business relationship a company can formally enter, and it is a basic requirement for doing this work properly.

What comes next

With the foundation in place, the next project is the new website: more interactive, and closer to an app than a set of pages.

Update, September 13, 2026

The new website is live at threndle.ai. It runs on Cloudflare with no server to maintain, and the diagnostic form sends each lead straight into HubSpot, which emails the report and the follow-ups.

The site now improves itself. PostHog compiles anonymous data on how visitors move through it, and its automated scouts file a report whenever something breaks or slows people down. Each report is fixed in the code and live within minutes. Ten of the eleven reports raised so far were real problems, and all ten are fixed, including a page that went blank for some visitors after an update. The eleventh was checked and was not a bug.

About the author

James Forrester runs threndle.ai, an AI automation agency in the Fraser Valley, British Columbia. threndle builds automations on whatever platform fits the client, Claude, Hermes, Kimi, or Cowork, connecting the tools a business already runs, teaches owners and their teams to operate them, and consults with businesses on how to adapt to the shift. This is part of a public build log about what works and what breaks. Questions, or want to talk through your own bottleneck? Start with the three-minute diagnostic or email hello@threndle.ai.