Build status
The authoritative record of what Syntur has built and who can reach it: Varra, the infrastructure beneath it, and Lucentra — updated as things genuinely change, not on a marketing schedule.
Last updated
This is build and capability status, not uptime. It says what exists and who can use it; it does not say whether Varra is up right now.
Seven words, because “built” hides the distinctions that matter. Implemented: the code exists and is tested. Enabled: switched on where it is deployed. Public: anyone with a Varra account can use it in the product. Internal: used by the team only, or reachable only through the engine’s API with no interface in the product. Partial: some of it is one of the above and some is not; the row says which. Building: under active construction. Future: a direction, not built. Implemented never implies public, and nothing on this page is described as more than it is.
Varra, by layer
The nine layers are described on the Varra page, and they are numbered the same way here.
01 — Generalist core
Public
Deployed as a real, publicly usable web application — not a prototype or a closed demo — backed by a real database, real accounts, and a genuinely tested codebase. Real-time streaming and prompt caching are both wired in. Image and PDF input work. An optional working memory lets the model keep its own notes across a session. Effort is selectable between faster and deeper.
02 — Router
Implemented Default off
Built, tested and carrying its own eval set and telemetry: deterministic rules first, a model classifier only where the rules are inconclusive, and every failure path — timeout, invalid output, telemetry error — failing open to the ordinary response path. It supports off, shadow and active modes: shadow routes and records a decision without applying any Skill, and active may apply only the approved Skills. The source default is off. Current production configuration is not asserted on this page. A routing decision is not permission. Model selection and risk scoring are design, not code.
03 — Work Items
Public by hand only
The record that lets a piece of work be tracked rather than only answered: an account-owned item with a title, a description, one of four states — open, blocked, resolved, cancelled — an optional link to the conversation it came from, and versioned edits that reject a stale write. POST/GET/PATCH/DELETE /api/work-items exist in the engine, with database-backed tests, account export and fail-closed deletion. An outcome can be appended to one — achieved, partly achieved, not achieved, indeterminate. The app carries a Work Items view and a New Work Item control, so an item can be created, tracked and resolved by hand. What still does not happen is anything automatic: nothing creates a Work Item on its own, and no routing, verification or execution path acts on one. Saving is explicit, and resolved never means verified, approved or executed. A resolved Work Item is not a verified business outcome. The layer →
04 — Specialist Skills
16 modes public 8 registered, 3 approved Building
Sixteen work modes ship in the product and you select them yourself. Separately, eight Skill descriptors are registered and enabled in the routing registry — construction invoice audit, document evidence analysis, electrical troubleshooting, HVAC diagnostics, financial analysis, investment research, operational exception analysis and operational financial impact — declaring which others they compose with. Three of them, electrical troubleshooting, HVAC diagnostics and construction invoice audit, are currently approved for application when Router mode is active. The other five are registered but not applied in any mode. Modes and Skill packs →
05 — Company context
Partial account values live Future
There is no company workspace in Varra. You cannot upload policies, connect a system, or set an approval rule. One narrow piece is live and in production: per-account reference data. GET/PUT/DELETE /api/reference back a “Your reference data” panel in the account menu, entries persist per account and per mode, and the precedence is account value, then built-in table, then the model's own memory. It applies on all four response paths, and an answer that used it is stamped as coming from the account. Labels are stored under the same canonical reduction lookups use, so an entry matches the same questions however its label is written. The intended layer →
06 — Tools
Partial
Live in the deployed product: document and image input, and the session working memory. Built into the engine but not available in the current Varra product interface: web search, which finds pages (bounded and opt-in, not enabled); web fetch, which reads a specific page; and the Advisor model, a stronger model for hard questions. Code execution is built into the engine and is not available in the current Varra product interface. Not in the product: any connection to an external business system — storage, project management, accounting, databases — with one exception. The engine’s one connector, a Gmail connection used only by Relay to send approved email, is available in Varra to eligible accounts and is not generally available; see row 08.
07 — Varra Assurance
Partial substitution public run verdicts internal
One mechanism works end to end: where an answer's key figure matches a verified table, the table's entry replaces the model's text and the answer is stamped with its source. Three of the sixteen modes carry such a table. Most Varra answers today are therefore not independently verified, and Varra says so rather than implying otherwise. Separately, the engine carries a deterministic evaluator whose verdicts the run path requires; it is internal. A passing check is not approval and grants no permission. Coverage and limits →
08 — Runtime and execution
Implemented Partial mostly foundations Building
Varra, the product, takes one kind of action in an external system: for eligible accounts, it can send an approved plain-text email, one per approval, through a Gmail connection the owner authorized. Since 20 September the engine has carried the foundations for acting under control. Apart from that email path, each is reachable only through authenticated API routes with no interface in Varra. Nothing moves without an explicit request from the signed-in owner. Broken down so that no part is read as further along than it is:
09 — Outcomes and learning
recording public learning future
No outcome feedback loop exists. Varra does not learn from corrections across users or sessions, and no model is trained or fine-tuned on customer conversations. The one piece of groundwork: an outcome assessment can be appended to a Work Item and read back as history, and the app now carries a form for writing one. Nothing consumes it — no routing decision, no model, no behavior anywhere. Recording an outcome is not learning from one.
Research and supporting systems
Telemetry
Implemented Internal Partial
Scoped records: routing decisions for evaluating the router, spend and usage accounting that survives a restart, and run and attempt history. Not a customer observability product, and not a measure of business outcomes.
Evaluation
Implemented Internal
Router eval sets and harnesses, run offline and in CI, and acceptance tests across the run and Assurance foundations. No public evaluation service and no benchmark claims. Research →
Training
Implemented Internal
Offline tooling to prepare a dataset and run a fine-tuning experiment on a small open model. No approved production training data, no approved trained model, no proprietary model integrated into Varra, and no continuous self-training.
Simulation and continuous improvement
Future
Neither exists as a platform. Individual tests and bounded simulations exist inside projects; they are not a simulation environment and not a learning loop.
Testing
Including real database-backed integration tests rather than mocks alone, plus a separate eval set for the routing layer.
Lucentra
No Lucentra hardware exists and none is shipping. It is a surface for the same Varra intelligence rather than a separate product, and it remains at an early, pre-hardware stage: reference-design sourcing is in progress, and every capability described for it — navigation, translation, object identification, captioning — is intended, not available. The software groundwork it will depend on is built and validated in software today, ahead of any hardware commitment: it runs the same sixteen work modes, carries automated tests of its own in continuous integration, and its heads-up display is scored for daylight legibility against worst-case backgrounds on every change — a question most projects cannot answer until hardware samples arrive.
Billing
Varra is free. An account is required so conversations persist. No card is asked for and no card can be entered. The Pro and Business tiers exist in the app and on the pricing page as descriptions of what those tiers will include, not as things anybody can buy.
Recently
-
The site was rebuilt around five sections — Research, Products, Business, Infrastructure and Company — with Varra described as Syntur’s flagship product and its other divisions described, as early as they are, on the company page. A news page now collects dated entries from this log. No capability changed, and no row on this page moved.
-
Rows 06 and 08 now record Gmail V1: in Varra, eligible accounts can prepare a plain-text email from a Work Item, approve it, and have Relay make one attempt to send it through their Gmail connection. It is not generally available, and the connection only sends; it reads no mail. The entry below was accurate on its date and is left as written.
-
Row 08 now records Relay’s production founder proof: one explicitly approved plain-text Gmail send, acknowledged by the provider and independently confirmed as delivered. It is the founder’s own account only. Relay is still not in Varra and not generally available.
-
The site was restructured around Syntur as an intelligent infrastructure company, with Varra as its core engine, and this page became build status with seven labels in place of three. Row 08 was rewritten: between 20 and 26 September the engine gained durable agent runs, deterministic Assurance verdicts, a record-only runtime step, exact-action approvals and Relay, all internal and none in Varra. Earlier entries are left as they were written.
-
Rows 03 and 09 were corrected against the deployed product, which had moved past them. Work Items and outcome assessments both have an interface in Varra now — a Work Items view, a New Work Item control and a form for recording an outcome — so the rows no longer say there is no way to reach either. What did not change is the part that mattered in both rows: nothing creates a Work Item on its own, and nothing consumes an outcome. The entry below, written when neither had an interface, is left as it was: it was accurate on its date, and a log that gets edited to match the present is not a log.
-
Work Items were added to the architecture as layer 03 — the account-owned record that lets a piece of work be tracked rather than only answered. The storage, the API and the outcome history exist in the engine; there is no interface for any of it, so the row above says so plainly. The site's wording was tightened at the same time to describe Varra as a system that carries work to a result rather than one that returns answers, and this page's layer numbering was corrected to match the overview, which it had silently disagreed with. No capability changed.
-
Varra Runtime — the planned execution layer, covering connectors, browser, sandbox and desktop environments — was added to the architecture on the overview, business and roadmap pages, and broken out here part by part. Nothing about it is built: no runtime service, no execution gateway, no connector to any external system. The two pieces of real groundwork are named above rather than rounded up.
-
The site was rebuilt around what Varra is becoming: a general-purpose system with a generalist core, a router, specialist Skills, tools, company context and verification, rather than a product defined by its trade modes. Skills and Business pages were added, the reference page became Proof, and this page gained a layer-by-layer status breakdown. No capability changed — only how accurately the site describes them.
-
Every page got a skip link, so a keyboard user no longer tabs through the whole top bar to reach the content — and the body typeface was declared as the variable font it is, which restores bold emphasis that had been rendering at medium weight.
-
The homepage was rebuilt around what can actually be checked: the reference substitution is set as text rather than a screenshot, and a composer in the hero hands a typed question straight to Varra.
-
Varra moved to its own domain, and the skill-routing layer gained its first finance and document skills — still behind the same switch, still off by default.
-
Rate limiting and the spend cap moved into the database, so neither resets when the service restarts.
-
A skill-routing layer landed in the engine with its own eval set. Its source default is off, and in that mode it changes nothing about a response.
-
The first two verified reference tables were published on this site — generated from the engine's own source rather than transcribed, so the page cannot drift from the product.
-
The logomark shipped across every page, and link previews got a declared banner instead of a bare URL.
Company
Syntur was established in 2026. Syntur, Varra and Lucentra are working names pending formal trademark clearance.