Nexxa AI

The agents write into the customer's systems of record, but the connectors that reach those systems are installed per engagement and are not part of the product. The homepage reads "We don't recommend. We execute. AI agents write into your systems of record", which puts it on the read write, actionable side.

The vendor's own terms place the connection layer outside the product. Section 4.6 has Nexxa install "data extraction tools, middleware, connectors" per engagement and states they "are not part of the platform or AI agents"; section 4.1 makes the customer responsible for the APIs and interfaces integrated with. No native integration, named system or connector the platform ships is documented.

Sourcenexxa.ai home, nexxa.ai/terms-of-service; readread 2026-09-15

Agents plan and run named operational workflows on their own, but no workflow structure is documented. The terms define AI Agents as software designed to "understand goals, create plans, execute actions, and interact with systems", and the industry pages describe agents running named operational workflows (RFQ-to-proposal, reconciliation and operations workflows), with four marked Deployed. That is autonomous multi step execution.

No sequencing, routing, branching or retry is described, and nothing shows workflows mixing deterministic steps with autonomous agent steps; the site says only that agents plan and act. A multi agent orchestration platform is described nowhere on the vendor's own site.

Sourcenexxa.ai/terms-of-service, nexxa.ai/all-industries/rail, nexxa.ai/all-industries/automotive; readread 2026-09-15

The agents are grounded in the customer's own data, such as floor plans and order history, but no maintained index the customer adds to is documented. The Construction page, marked Deployed, reads "Extract and organize key information from floor plans"; the Automotive page grounds demand forecasting in "order history, customer signals, and operational data"; and the homepage says Nexxa captures "Decision logic. Institutional knowledge. Operational judgment", held by the customer's system.

The site documents no maintained index or graph into which new customer knowledge can be added without retraining. The only structure named is contractual: the terms define Trained Models as weights, embeddings or other learned representations created from Customer Data, which does not say whether new knowledge enters an index or only through training. No indexed, refreshed or permissioned source is named, and nothing shows which documents influenced an output.

Sourcenexxa.ai/all-industries/construction, nexxa.ai/all-industries/automotive, nexxa.ai home, nexxa.ai/terms-of-service; readread 2026-09-15

No approval or guardrail mechanism ships with the product; the terms make the customer responsible for overseeing agent actions. No console, rule layer or approval surface is documented anywhere on the vendor's site.

Terms section 4.3 requires the customer to "implement appropriate human oversight, validation procedures, and safety controls" for all AI agent actions, and section 7.1 makes the customer solely responsible for reviewing, verifying and approving all agent actions before relying on them. That is a gate the customer is contractually required to build and own, not a vendor mechanism.

No approval step, escalation rule or pause and resume control is documented, so there is no node, workflow or policy layer at which an approval could be inserted.

Sourcenexxa.ai/terms-of-service (updated 1 April 2026); readread 2026-09-15

Security rests on contract terms: no certification is claimed and no customer facing access control is documented. There is no single sign on or SAML, no roles and no audit trail. The privacy policy names sign-in through third-party authentication services such as Google, Microsoft and Apple, which is account login rather than a provisioning standard or an access control. The footer carries only Privacy Policy and Terms of Service links, with no badge and no trust portal link, and trust.nexxa.ai does not resolve.

What the site does state is contractual: terms section 8.2(d) warrants a "commercially reasonable information security program", and section 5.2 sets a model-training policy whose scope (full, limited or no training rights) is fixed per order form. That answers the training question as a contract term rather than a control the customer operates.

Sourcenexxa.ai/terms-of-service (updated 1 April 2026), nexxa.ai/privacy-policy, nexxa.ai footer; readread 2026-09-15

What the agents do leaves no documented trace, log or audit event. Nothing on the site lets a buyer inspect prompts, tool calls, retrieved knowledge and outputs step by step, and no execution history or metrics are documented for agent behavior.

Two things look like observability and are not: terms section 6.3(d) offers "usage monitoring tools or periodic usage reports" so the customer can track consumption against usage limits, which is billing metering; and the industry pages' Operational Visibility and Throughput Visibility tiles read on the customer's plant, assets and schedules, not on the agents.

Sourcenexxa.ai/terms-of-service, nexxa.ai/all-industries pages; readread 2026-09-15

Memory is absent: no session, conversation, workflow or long term memory is described, and nothing persists context across a run, user or team. The homepage's "Decision logic. Institutional knowledge. Operational judgment", held by the customer's system, is a knowledge store, and a knowledge store is not memory. Learning absorbed into Trained Models under the terms lives in model weights, not in anything an agent reads back.

Sourcenexxa.ai home, nexxa.ai/terms-of-service; readread 2026-09-15

Delivery is only as a hosted service operated in the United States, with no region or environment choice. The site names exactly one deployment mode: the trial agreement licenses "the platform as a service located at www.nexxa.ai". Terms section 3.5 leaves hosting obligations to the order form without naming any alternative mode, and the privacy policy states the services are hosted and operated in the United States with no region or environment selection. Working inside a customer's existing tools would be integration rather than a deployment option.

The homepage's "owned entirely by you" and "What you own: the stack" are not deployment claims, and they sit against the terms: section 3.6 grants the customer no ownership interest in the platform or AI agents, and section 13.3 ends access on termination.

Sourcenexxa.ai/trialagreement, nexxa.ai/terms-of-service, nexxa.ai/privacy-policy, nexxa.ai home; readread 2026-09-15

Solution areas are listed by industry, but none is a ready made unit a buyer selects and starts from. Eleven industry pages each name three solution areas (RFQ Intelligence, Floor Plan Intelligence, Demand Forecasting, Intelligent Asset Management and others), labeled Deployed on four pages and Emerging on seven.

The shared copy on every page reads "Nexxa helps teams identify where AI agents can create the most value", which describes an engagement that scopes and builds, and the Emerging label marks most areas as not yet shipped. Named solution areas with no catalog to pick from are a list of problems addressed, not a pack of production-ready starting points.

Sourcenexxa.ai/all-industries pages; readread 2026-09-15

Nothing documented starts the agents: no event, schedule or conversational surface, and the site names no channel they work in. The privacy policy describes an AI voice chatbot on Nexxa's own services for visitors to talk to Nexxa itself; that is the vendor's contact surface, not a channel the buyer's agents work in. The site is thin and has no documentation host.

Sourcenexxa.ai home, nexxa.ai/privacy-policy; readread 2026-09-15

Model choice belongs to the vendor and is undisclosed: no model or provider is named. The terms define LLM as the "large language models and other foundation models utilized by the platform" and bill "third-party LLM services" as Variable Consumption Costs on token usage, but no routing across models is disclosed, and no customer selection, workspace policy or bring your own key option exists. A plural in a legal definition is not disclosed routing across models.

Sourcenexxa.ai/terms-of-service (updated 1 April 2026); readread 2026-09-15

The terms say the platform has APIs with documentation for customers, but none of it is public, so the API cannot be read or confirmed stable. Documentation is defined to include "API documentation" relating to the Platform, the Platform is defined to include its "interfaces, APIs", and Usage Limits are metered on "API calls". None of it is published: llms.txt returns 404, the docs, dev, api and app subdomains of nexxa.ai do not resolve, and the site links no developer surface. The API documentation is for customers only.

Whether there is a stable API and SDK or mostly interface only functionality cannot be answered: no reference can be read and no SDK is named. A definition in a contract asserts the API; it does not document it. Nexxa also has a listing on the Siemens Xcelerator Marketplace.

Sourcenexxa.ai/terms-of-service (updated 1 April 2026); readread 2026-09-15

There is no way for a buyer to test or score the agents; the terms make validation the customer's job. Nothing describes testing workflows against datasets before production, or an optimization loop after deployment.

Terms section 4.4 makes the customer "solely responsible for validating the platform and AI agents", including testing agent performance and verifying the accuracy of outputs and actions, and section 7.2 repeats it.

Section 5.2's right for Nexxa to "train, tune, evaluate, test" its own models on customer data is internal development, not a buyer surface, and the homepage's "Improves over time: continuously, by AI" names no loop, score or gate.

Sourcenexxa.ai/terms-of-service, nexxa.ai home; readread 2026-09-15

Customer systems are reached through APIs and installed connectors, by the vendor's own terms, and no browser or computer use is documented. No page on the vendor's site mentions AutoCAD, a GUI, a screen, a browser or computer control. The mechanism the vendor does document points the other way: terms section 4.1 has the customer supply the APIs and interfaces the platform integrates with, and section 4.6 has Nexxa install "data extraction tools, middleware, connectors" to reach them.

With no screen in the documented path, questions about sandboxing or breakage when UI elements change do not arise. Nothing on the site is blocked: llms.txt returns 404 and the docs, api and trust subdomains do not resolve, so the absence is visible. A third-party description of agents working inside thick-client engineering applications such as AutoCAD appears nowhere on the vendor's own pages.

Sourcenexxa.ai/terms-of-service (updated 1 April 2026), nexxa.ai home; readread 2026-09-15