We built this because we kept losing the afternoon.
Virex Systems is a small pre-launch company building the operations layer for teams working with AI coding agents. Two products so far, both started as tools we needed ourselves and could not buy.
// Pre-launch. No customers to name, no funding announcement, no logo wall.
Two problems, both from our own work.
Neither product came from a market map. They came from the same week going wrong twice.
The agent stopped and nobody was there
We were running long Claude Code sessions and walking away from them, which is what they are for. Then we would come back to a session that had stopped forty minutes in, waiting on a permission request that took two seconds to answer. The work was not hard. Being at the desk was.
Every session started as a stranger
The same agents kept rediscovering things about our own codebase that a previous session had already worked out, and there was nowhere for that knowledge to live. When a teammate started their own session, it began from nothing all over again.
The account model came from the same place
We wanted both without running two vendors, two logins, and two invoices. So the platform underneath is deliberately boring: one account, one organization, one subscription with a line per product.
Four opinions the products are built on.
Stated so you can disagree with them before you buy rather than after.
Your machine should stay yours
Agents run where your code, credentials, and half-finished state already are. A control plane can coordinate all of that without ever executing it, and we think that boundary is worth protecting.
Supervision is a feature
Permission pauses look like friction and are actually where accountability attaches to a person. We build to make supervision cheaper, not to remove it.
Capability belongs behind protocols
Tool preferences change faster than the knowledge built around them. Anything meant to accumulate should outlive the client that happened to write it.
Honest beats flattering
We would rather tell you a competitor fits better than sell a seat that gets cancelled in a month. Our comparison pages say where we lose.
Small, and using the thing.
A small team
Small enough that the person who replies to your message is the person who can change the product. That is an advantage now and something we will have to work to keep.
We run our own tools
Both products are used daily by the people building them. Virex Remote watches the sessions writing Virex, and Virex Memory holds what those sessions learned.
We publish what changed
The changelog is a record rather than an announcement channel, and the blog explains decisions rather than launching things.
What we are not, yet.
A pre-launch about page is where companies do most of their lying. Here is the accurate version.
- We are pre-launch. There are no customer names, logos, case studies, or testimonials to show you, and inventing them is the one thing we will not do.
- We are not SOC 2 certified. Controls are designed to a SOC 2-oriented control set, with no audit completed.
- We are a small team, which means depth in two products rather than breadth across ten.
- Virex Remote works with Claude Code. If your team has standardised on something else, that matters more than anything on this page.
About Virex
Who is Virex Systems?
A small pre-launch company building developer tools for teams working with AI coding agents. Two products are in the lineup: Virex Remote for oversight of coding sessions, and Virex Memory for persistent agent memory.
Where are you based?
Virex Systems LLC operates as a distributed team. For anything requiring a formal entity or address, including procurement and legal review, contact us and we will provide it directly.
Are you funded?
We are not making funding announcements. It is not information that changes whether the product solves your problem, and we would rather the pages here be about the product.
How many customers do you have?
We are pre-launch, so the honest answer is that we are not going to quote a number we would have to inflate. Judge the product on what it does.
Will there be more products?
Two products exist today and we are not going to tease a third. When there is something real, the changelog will say so.
How do I get in touch?
Use the contact page. Messages reach the team building the product, and you will get a real reply rather than a sequence.
Try the thing rather than the story.
Create an organization, subscribe, and assign one seat. That is the whole setup.