Verity is a self-hosted, multi-service AI orchestrator: a Go gateway, a Python brain, a Rust core and a Rust node daemon, with a web workspace on top. It runs flows and scheduled offices over whichever model providers you configure, remembers by filtering rather than accumulating, and can farm work out to volunteered machines that check each other.
Theambitionisnotasmarteragent.Itisanagentwhoselimits,costsandfailuremodesarewrittendownwhereyoucanfindthem.
Every dependency has a fallback and every fallback is exercised. Memory drops from the graph store to a vault on disk. The tag registry drops from Postgres to a file to memory. A service that cannot reach its ideal backend comes up worse, not down.
The tenant is established from a verified token and carried as call metadata. No handler reconstructs it from something the caller wrote, because a caller who can name the tenant can name a different one.
A web page, an MCP response, a node's output, an uploaded file: all of it is content from elsewhere, and all of it is wrapped before it can influence a model. There is no fast path for sources that look safe.
When a check cannot be completed, the answer is no. A vector query without a tenant filter does not run unfiltered; it does not run.
Tool iterations, worker counts and office concurrency are all capped. Publishing the caps is part of the product: an agent with an unstated budget is an agent you cannot plan around.
Documentation drifts. Where a document and the source disagree, the source is right and the document is a bug. That is why Verity's own audit refuses to cite anything but a file and a line.
Verity keeps a gap audit against the strongest comparable products, with a file-and-line citation behind every claim it makes about itself. These are the findings that went against it.
It can call skill scripts that already exist on the server, choosing the script and its arguments, but it never authors a program.
The sandbox to run one (path jail, scrubbed environment, network isolation, resource limits) is already built and tested. The tool that would let a model use it is not.
The turn model is text-only. Uploads are converted to markdown, so a screenshot contributes nothing. "What is wrong in this picture" is a question Verity structurally cannot answer today.
Flows and offices are start-and-poll. There is no cancel route, and the queue only drains cooperatively at shutdown. Steering a long run mid-flight is not available.
Artifacts, projects, the knowledge base, memory inspection and MCP server management all have working service routes and no user interface.
The backend is further along than the product, and that gap is the top item on the plan.
You give Verity a base URL and it connects without credentials. The encrypted vault that would hold a per-server secret exists and holds provider keys; wiring connectors through it has not been done.
Some of what competitors ship is missing from Verity because it has not been built. The following are missing because building them would make it a different product.
The audit, the plan, the tests and the code are all in one repository. If a claim on this site is wrong, the file that proves it is right there.