Works with Claude, ChatGPT, Microsoft 365 Copilot and any MCP client
Enterprise Context for every AI agent.
Nexatron sits between your AI agents and your business systems, so every agent works from the same connected data, approved definitions, business rules and permissions.
Connected data brings the figures from where they live. Semantics & ontology says what they mean. Business context applies your rules. Governance decides who sees what and keeps the record.
Illustrative example with sample figures.
Connected data · Queried in place, 1 of 4
Straight from your systems, with no warehouse to load.
Queries run in your systems with user-level access. There is no warehouse to load. Nexatron keeps what it needs to answer and show its work, inside your tenant: the catalog, value lists from tables that aren’t row-secured, and the answers and rows people save or receive.
Illustration: the $42.8 million answer traced through the approved definition to revenue lines in the NetSuite general ledger for July to September 2026. Nexatron connects to 279 systems: 200 systems of record such as Salesforce, SAP S/4HANA, Oracle Fusion, NetSuite and ServiceNow; 30 data platforms such as Snowflake, Databricks, BigQuery and Amazon Redshift; 11 BI and semantic model tools such as Power BI, Tableau, Looker and dbt; and 38 docs and knowledge systems such as SharePoint, Google Drive, Confluence and Notion.
Semantics & ontology · Approved definitions, 2 of 4
Your definitions, not a model’s guess.
Definitions say what a metric counts, which entities it covers and how they connect across your systems. Every answer shows its trust level: approved by an owner, or interpreted and labeled so.
Illustration: the approved definition of recognized revenue, version 14, owned by Finance: revenue earned in the period, net of credits and intercompany eliminations, from the NetSuite general ledger. Below it, how the business connects: a customer, held in Salesforce and NetSuite, signs a contract in Salesforce; the contract is billed as invoices in NetSuite, and invoices post to ledger lines in NetSuite. Bookings, owned by Revenue Operations, counts contracts. Recognized revenue, approved by Finance, counts ledger lines. Agents follow these links, so bookings and recognized revenue never get mixed up.
Business context · Rules and calendars, 3 of 4
Your calendar, your close, your eliminations.
Quarters follow your calendar, figures stay labeled preliminary until the books close, and intercompany revenue is eliminated the way Finance does it. Nexatron learns these rules from your docs, dashboards and queries, and owners approve them.
Illustration: Q3 2026 runs from July to September. The books closed on October 12, so Q3 figures are final; before the close they were labeled preliminary. Intercompany revenue is eliminated on consolidation, and the answer is compared with the Q3 plan of $44.2 million.
Governance · Access and audit, 4 of 4
Answers that respect who is asking.
Row and column rules follow the person, whether they ask directly or through an agent. Anything outside their access never appears in an answer, and every request is on record.
Illustration: an access table. The CFO sees revenue for all four regions and the cost fields. The regional VP for APAC sees APAC only. An account executive in Northern Europe sees their own accounts, and so does ChatGPT acting for them. When that executive asks ChatGPT what bookings were in Q3, the answer is $2.4 million, for their 14 accounts; accounts outside their access never reach the answer. Every request is on record: who asked, through which agent, and what they saw.
Every agent, one answer.
Definitions, rules and permissions live in Nexatron, so Claude, ChatGPT, Microsoft 365 Copilot, Slack, Teams, your own agents and your apps all answer from the same context.
The questions your leaders ask every week.
Pick a leader and a question. Every answer shows its trust level, the system it came from, the definition it used, the rule it applied and what the asker can see.
The same approved answer comes back in any agent.
Claude, for the CFOApproved
What was recognized revenue against plan in Q3?
$42.8M3.2% below the Q3 plan of $44.2M
How Nexatron answered
Connected data
NetSuite general ledger
Semantics & ontology
Recognized revenue, v14
Business context
Q3 closed Oct 12: final
Governance
CFO: all regions
Claude, for the CFOApproved
Which region missed plan by the most in Q3?
Northern Europe$8.1M against a plan of $8.9M, 9.0% below
How Nexatron answered
Connected data
NetSuite general ledger
Semantics & ontology
Region, as Finance maps accounts
Business context
Compared with the approved Q3 plan
Governance
CFO: all regions
Claude, for the CFOApproved
What was gross margin in Q3?
68.2%Up 1.1 points on Q2
How Nexatron answered
Connected data
NetSuite general ledger
Semantics & ontology
Gross margin, v6
Business context
Intercompany eliminated
Governance
CFO: cost fields included
Illustrative example with sample figures.
Ask the way you work.
Chat, dashboards, agents and your own product all read the same approved definitions, so a number never changes with the tool.
Nexatron/Conversational BIAI-powered dashboardsAnalytics agentsEmbedded in your productCFO
Conversational BI. Ask in your own words. Every answer comes with the query behind it and the rows it returned. Example conversation. Asked how revenue compared to plan in Q3, Nexatron answers $42.8 million in recognized revenue, 3.2% below the Q3 plan of $44.2 million, approved, with revenue by region against plan: North America $18.9 million against $19.3 million, Northern Europe $8.1 million against $8.9 million, Southern Europe $7.9 million against $8.0 million, APAC $7.9 million against $8.0 million. The answer cites the NetSuite general ledger and recognized revenue version 14, with the SQL and lineage. Asked which region drove the gap: Northern Europe, 9.0% below plan; the other three regions were within 2.1% of plan.
New question
Recent
Q3 revenue against planPipeline coverage by regionRenewals due in November
How did revenue compare to plan in Q3?
$42.8M in recognized revenue, 3.2% below the Q3 plan of $44.2M.Approved
By regionQ3 actualPlan
North America$18.9M
Northern Europe$8.1M
Southern Europe$7.9M
APAC$7.9M
NetSuite general ledger
Recognized revenue, v14
Query
Which region drove the gap?
Northern Europe: $8.1M against a plan of $8.9M, 9.0% below. The other three regions were within 2.1% of plan.
Ask about your business
AI-powered dashboards. Built on approved metrics, with lineage that explains every change. Example dashboard: revenue operations for Q3 2026, final after the October 12 close, built on approved metrics. Closed won up 18.2% year on year, win rate 31.4%, up 2.1 points, average cycle 38 days, down 4 days, and Q4 pipeline coverage 3.4 times against a 3.0 target. Pipeline coverage by region: North America 3.6, Northern Europe 2.9, below target, Southern Europe 3.3, APAC 3.7. The win rate tile shows its lineage: win rate version 3, from Salesforce opportunities, for July to September, approved.
Revenue operations
Q3 2026, final after the October 12 close
Approved metrics
Closed won+18.2%year on year
Win rate31.4%up 2.1 points
Average cycle38 daysdown 4 days
Pipeline coverage, Q43.4×target 3.0×
Pipeline coverage by region, Q4Target 3.0×
North America3.6×
Northern Europe2.9×
Southern Europe3.3×
APAC3.7×
TargetBelow target
Win rate, 31.4%
Definition
Win rate, version 3
Source
Salesforce opportunities
Period
Q3, July to September
Status
Approved
Every tile is an approved metric. Open any number to see where it came from.
Analytics agents. Agents query with the permissions of the person they act for, and every call is logged. Example agent run: a Q3 board pack agent, your own agent over MCP, acting for the CFO. It calls ask for recognized revenue against plan and gets $42.8 million, approved; explain_metric for recognized revenue, version 14, owned by Finance; query_metric for gross margin in Q3, 68.2%, up 1.1 points; and audit, 3 calls logged. Applied to every call: it acts for the CFO, sees all four regions and the cost fields, and every call is logged. An agent never gets more access than the person it acts for.
Q3 board packYour own agent, over MCP, acting for the CFO
Run complete
1
askRecognized revenue against plan, Q3
$42.8MApproved
2
explain_metricrecognized_revenue
Version 14, owned by Finance
3
query_metricgross_margin, Q3 2026
68.2%, up 1.1 pointsApproved
4
auditthis session
3 calls logged
Applied to every call
Acting for
The CFO
Answered from
NetSuite general ledger
Rows
All four regions
Columns
Cost fields included
Record
Every call logged
An agent never gets more access than the person it acts for.
Embedded in your product. Your product, our answer engine. Customers ask under your brand, with lineage and the same security model. Example of an answer embedded in your own product: in a supplier spend page, your customer asks what they spent with suppliers this quarter and gets $1.9 million across 42 suppliers, seeing only their own data. It is added with an SDK provided during onboarding, an iFrame or the REST API, and keeps lineage and security.
OverviewSuppliersContractsInvoices
Supplier spendYour product
Ask about your spendPowered by Nexatron
What did we spend with suppliers this quarter?
$1.9M across 42 suppliers
Which three suppliers are the largest?
Your top three hold 38% of spend
Answered from SAP Ariba, with its approved definition
Your customer sees only their own data
Ask about your spend
SDKiFrameREST API
// one token per viewer<NexatronProviderconfig={{ baseUrl, token }}><ChatPanel /></NexatronProvider>
Your brand and your interface
Each customer sees only their own data
The same approved definitions
Ask in your own words. Every answer comes with the query behind it and the rows it returned.
Built on approved metrics, with lineage that explains every change.
Agents query with the permissions of the person they act for, and every call is logged.
Your product, our answer engine. Customers ask under your brand, with lineage and the same security model.
Illustrative example with sample figures.
Three steps, no data project.
No migration and no new warehouse. Nexatron works with the systems and permissions you already have.
Your systems
+271
279 connectorsQueried at source, no warehouse to load
1
Connect what you already run
Queries run where the data is, under the permissions it already has. Most of the work is connecting and approving definitions, not moving data.
Salesforce, NetSuite, SAP S/4HANA, Oracle Fusion, Snowflake, Databricks, BigQuery, ServiceNow and 271 more.
It reads your schemas, profiles and query history, imports definitions you already have, and proposes definitions, joins and rules. Owners approve them, and every version is kept.
Your people and agents
$42.8M, approvedThe same answer in every agent
3
Ask in your own words
In text, by voice or through your AI assistant. Every answer shows its work.
Claude, ChatGPT, Microsoft 365 Copilot, Slack, Teams and voice.
Popular connectors
See what your teams can ask of the systems you already run, in Claude, ChatGPT and Microsoft 365 Copilot. Every connector is available today.
An enterprise context platform. It gives people and AI agents the same approved definitions, business rules and permissions, so the answers match wherever they are asked.
What is a semantic layer?
Shared definitions of your metrics, joins and rules. Nexatron proposes definitions from your systems, and your owners approve them. Every change is versioned.
Which assistants can connect over MCP?
Claude, ChatGPT, Microsoft 365 Copilot and any MCP client that supports remote servers, over Streamable HTTP and JSON-RPC 2.0, with OAuth 2.1, PKCE and Dynamic Client Registration.
Which data sources does it support?
Warehouses and databases such as Snowflake, BigQuery, Amazon Redshift, Databricks, PostgreSQL, MySQL, SQL Server and DuckDB, files in S3 and Parquet, and business apps such as Salesforce, NetSuite, QuickBooks, ServiceNow, HubSpot, Stripe, Microsoft Dynamics 365 and Atlassian. Users sign in with their own account in each business app (or your SSO), and Nexatron inherits their existing permissions.
How is our data kept separate?
Every request is limited to your tenant and checked against row-level security before it runs. Warehouse credentials are encrypted with AES-256-GCM, and your data is never used to train foundation models.
What comes with an answer?
The result rows, the query that produced them, the tables it read, its trust level, and who on your team reviewed the logic behind it and when, once someone has.
Do people and agents get the same answers?
Yes. Both use the same approved definitions, access rules and audit log.
Give every agent the same context.
Tell us which systems you run, and we plan a pilot on them with you.