AEC Magazine reported on 3 November that nCircle Tech has launched nVibe, an AI-powered development platform that lets AEC professionals build working applications without writing code. The product’s own site says co-founder Tarika Jain gave nVibe and a companion product, nVibe for Revit, their first public showing at the Autodesk University 2026 Platform Leadership Forum in Las Vegas — so the magazine’s report is the launch notice, not the product’s first appearance, and this article does not assign it a single launch date.
The pitch, in the site’s own words: “Your AEC experts know what to build. Now they can build it.” A domain expert — the site names VDC leads, BIM coordinators, superintendents, project engineers and operations teams — describes a tool in chat, by typing or speaking. The platform generates the interface, the data model and the validation rules, connects to the project systems without integration code, and deploys the app, each one with its own database.
That is a familiar enough product shape in 2026 that it would not ordinarily be worth 1,500 words. What makes it worth them is the step in the middle of that sequence, which the site states plainly: the builder deploys after IT approval.
Three Days Ago, This Was the Gap
On 2 November, AEC Magazine published a Q&A with AMC Bridge’s Igor Tsinman about what it called the home-brew estate — the accumulating stock of AI-built applications inside architecture and engineering firms that nobody formally owns. This publication’s read of that interview, set against its own archive, was that far more companies had announced the connectors than had announced work on the records. Tsinman’s list of what a firm should be able to show — which automated tool was used, where, who authorised it, which version ran, and what it changed — was described there as not technically difficult, merely something far fewer companies had announced work on than had announced the connectors.
nVibe’s site is, on its face, a product that answers most of that list. The controls it advertises:
- centralised policy enforcement across apps,
- “Mandatory IT review before production rollout”,
- role-based access control,
- single sign-on via SAML 2.0 and OAuth2,
- audit logs of data queries and builds,
- security the site describes as NIST 2.0 aligned, with TLS 1.3 encryption,
- bring-your-own LLM, from OpenAI, Anthropic or Azure,
- hosting in a managed cloud or in the customer’s own virtual private cloud.
Those are the site’s claims about its own product and are reported here as such — this publication has not tested the platform, audited the controls, or seen the logs. The point is not that the claims are verified. The point is that somebody is now making them, in a product, as the selling proposition rather than as a compliance appendix. That is a change in what the market is being sold, and the change happened within a week of the gap being named.
It is worth being careful about the direction of that arrow. nVibe was shown at Autodesk University, which ran 15–17 September, and was plainly not built in response to a magazine interview published on 2 November. The sequence is coincidence, not causation, and the useful reading is the duller one: two parties arrived independently at the same conclusion about where the unsolved problem in AI-built AEC tooling sits, and one of them was already building the answer.
The AEC Vocabulary Is the Moat Being Claimed
The differentiator nCircle claims against general-purpose AI coding tools is domain knowledge. Per the magazine’s account, nVibe understands AEC terminology — WBS codes, CSI MasterFormat, RFIs, submittals, and LoD 100 through 500.
Whether that is a durable moat is a reasonable question and not one this article can settle; a frontier model with a good prompt knows what a submittal is. The stronger version of the same argument is not vocabulary but wiring, and the site’s connector list is where it lives:
- Autodesk Construction Cloud — issues, RFIs, submittals, checklists
- Autodesk Platform Services — model views
- Autodesk Navisworks — clash reports
- Autodesk Revit — parameters, worksharing, model health
- Procore — contracts, punch items, daily logs, subcontracts
- AEC Data Model — object-level properties in cloud workspaces
- SAP and other ERP systems — job costing
- Model Context Protocol
Those are object-level hooks into the systems where the work actually lives, and assembling them is unglamorous, slow and hard to copy quickly.
How many of them a buyer can use today is not settled by the two accounts, and it is worth saying so plainly in an article that spends a section on availability. The site marks all eight as connected. The magazine’s 3 November report lists Autodesk Forma, Autodesk Platform Services, the AEC Data Model, SAP and other ERP systems, and MCP as the pre-built connectors, does not mention Autodesk Construction Cloud, and says integrations with Navisworks, Procore, AutoCAD and Revit are “coming soon.” A prospective buyer should ask which of the eight is live rather than take either list as the answer. The site’s illustrative use cases are correspondingly mundane: clash-tracking dashboards, Level 1 to 5 commissioning checklists, project dashboards, daily labour and safety trackers. The single case study on the site is anonymised — a VDC coordinator who built an ACC issues dashboard in an afternoon to replace a manual coordination status meeting.
Neither the product site’s home page nor the magazine’s report names a single customer, so this article names none either. Customer claims are the strictest class in this newsroom’s standard, and an anonymised case study does not meet it.
nVibe for Revit is listed as a separate, new product. The magazine describes it as intended to translate plain-language instructions into native Revit plugins that appear on a team’s Revit ribbon — intended, not stated as shipping, and that distinction is the magazine’s. Per nCircle, by way of the magazine, runs of the application after AI has been used during the build are token-free; the magazine does not independently verify that.
Flat Rate, Which Is the Third Answer in Two Months
The site is explicit that nVibe is priced at a flat rate rather than per token, so that costs do not rise with each build or each use. No figures are published; pricing is sized to the customer’s projects after a demo.
Put that beside the two other AEC AI pricing structures in this archive and the sector is visibly unsettled. Motif priced its agent-native BIM tool per AI user rather than per seat — the AI is a licence. Qonic, launching agents inside its BIM platform today, meters them in tokens on top of a platform sold by portfolio size with unlimited users — the AI is a utility. nVibe sells it as a fixed cost and says so as a feature. Three vendors, three answers, inside two months — Motif’s on 11 September, the other two this week. The comparison is this publication’s, drawn from each company’s own published pricing, and it is too early to say which of them a construction client’s procurement function will tolerate.
The flat-rate choice does sit oddly with bring-your-own-LLM, and the resolution is probably the obvious one: if the customer supplies and pays for the model, the vendor is not absorbing inference cost and can price its own layer flat. The site does not spell that out, and this paragraph is inference, labelled as such.
Availability Is the Thing the Site Does Not State
What nVibe’s site does not say — on the pages read for this article — is whether the product is in beta, waitlisted or generally available. It offers demos, “early pilot access,” and a four-week pilot programme — scope use cases in week one, build with domain experts in weeks two and three, deploy to jobsite teams and gather feedback in week four, evaluate and scale from week five.
A structured pilot programme as the primary route to the product is how early-stage enterprise software is sold, and it is not the same as general availability. A firm reading the governance list above should establish which of those controls are shipping and which are roadmap before treating the list as an answer to its own audit problem. That is not a criticism of the product; it is the question the site leaves open.
Who nCircle Tech Is
nCircle Tech is headquartered in Pune, India, with offices its product site lists in Chigasaki (Japan), London and Dallas. Its own site describes the company as “a one-stop 2D/3D Product development Center for AEC and Manufacturing,” with service lines in BIM and CAD workflow automation, Scan to BIM, AI and machine learning, IT staff augmentation, and web and mobile development. It also sells CAD and BIM plugins directly, including a point cloud importer/exporter for Revit and a BIM model rule checker. The magazine quotes Varun Bhartiya, co-founder and CEO, on the premise: that turning an idea into software has traditionally meant finding a developer and waiting months, and that the company wanted to change that.
That background matters to how the product should be read. A services firm that has spent years building CAD and BIM integrations for other people’s platforms is well placed to build the connector layer nVibe depends on, and badly placed to be mistaken for a frontier-model company. The moat claim is the plumbing and the governance, not the intelligence — and the bring-your-own-LLM option says the company agrees.
What to Watch
The governance claims are the whole proposition, so they are the thing to verify. “Audit logs of data queries and builds” is the single most consequential line on the site: it is the record that this publication found the sector was not building, while Autodesk’s own documentation confirms two of its three Revit MCP servers can change your model, and that CMiC made the headline feature of the MCP server under its ERP in a different form, as permission inheritance. What those logs capture, how long they are retained, and whether they survive an app being rebuilt are the questions a firm’s own risk function will ask, and the site does not answer them.
The second is the approval gate itself. Mandatory IT review before production rollout is a strong control and a potential bottleneck, which is precisely the friction that drove firms to build unsanctioned tools in the first place. A gate that is too slow gets routed around — and on the account of the AMC Bridge interview this publication covered on 2 November, waiting for a conventional software project is exactly what firms stopped doing. Whether nVibe’s gate is fast enough to be used is an operational question no product page can answer.
And the third is the one that applies to this entire week of announcements. Autom8Labs gave away 22 AEC skills on the argument that the connector was never the hard part; Qonic put agents inside the model; nVibe sells the governed container around tools a firm builds for itself. Three different companies, within three days, all betting that the scarce thing in AEC AI is no longer capability. On the evidence of this archive, they are right about that — and nVibe is the one of the three whose product is mostly the paperwork.
