Small tools that respect your machine
Guard, Agora, and ledgent look unrelated: an API, a launcher, a CLI. What they share is a stance about software, not a market.
Nexalix Labs makes three things that look unrelated. Guard is a fraud API for Telegram and TON. Agora is a launcher for Windows. ledgent is a command line tool that reads your AI coding logs. Different users, different markets, no obvious throughline.
For a while I described the company as trust infrastructure for TON. That was true for Guard and wrong for everything else. The launcher does not care about TON, and neither does the cost tool. When the description of your company only fits one of your products, the description is the thing that is broken.
So what actually connects them? It is a stance, not a market. Small tools that do one job and respect the machine they run on.
Respecting the machine has a few concrete meanings here. Agora phones home only to check for an update and carries no telemetry. ledgent makes zero network calls by default: it reads logs that are already on your disk and never sends them anywhere. Guard is a server, so the machine it has to respect is your users’ data, which is why scores are scoped and nothing leaks across tenants. None of this shows up in a feature list. It is closer to a floor we refuse to drop below.
The other half is size. A launcher installer around 1 MB. A cost tool with zero runtime dependencies. A fraud API with a hard limit of 150 lines per file. Staying small is not a constraint we put up with, it is a property we are trying to keep. Software that stays small stays legible, and legible software is the kind you can still reason about a year later.
I am not going to dress this up as a grand strategy. It is closer to a set of habits, and habits are easier to hold than mission statements. The test is boring and useful. If a product needs telemetry, a heavy runtime, or a network call it does not strictly need, it probably does not belong here.
Guard, Agora, and ledgent will keep drifting into different markets, and that is fine. The lab is the shell. What holds the shell together is how the tools behave, not who ends up buying them.