Data connections
Databases and any web API, each person as themselves where the system allows it.
Data connectionsPlatform
One AI platform on the systems you already run
Platform overview Watch the tourAsk, see and act on one sample companySolutions · IT & data
nexibi reads the systems you already look after, when someone asks. Each connection says whose sign-in it uses, each person signs in as themselves, and everything people save is private until it is shared.
Never shown back, owners included
Each connection shows what it reads and whose sign-in runs. Where a system has its own logins, each person signs in with theirs and sees what that system lets them see.
The list of records with an empty field, and how many.
Before it runs, Query Studio shows a row-budget chip and a size estimate from the database's own planner, and offers cheaper ways to write it, shown as a change you accept or not.
The History page lists every copy you own and says, in plain words, whether each is healthy, waiting, failing or paused, and what to do.
Before a delete, it lists the queries, boards, flows, analyses and history copies that use it.
It answers and names the page.
On Tarnwick Supply Co., sample data. Its order system is connected through its web API; a reporting copy in PostgreSQL serves boards (a flow cannot read a connected database today).
"Which customer records have no sales person assigned?" The answer: 7 of 150 customers, with the list.
7 of 150 customers have no sales person.
| Customer | Sales person |
|---|---|
| Marrowick Fit-Out | none |
| Juniper Row Fit-Out | none |
| Eskwith Property Services | none |
A board "Data checks", one tile per check: customers with no sales person (7), products with no supplier (none), invoices with no due date (2). A company owner marks the queries behind it as "Recommended", so people reach for them first.
| Customers with no sales person | Recommended |
| Products with no supplier | Recommended |
| Invoices with no due date | Recommended |
A company owner builds a flow in the flow designer: every Monday at 07:00 it reads the customers with no sales person from the order system's web API, makes an Excel file and e-mails it to the sales lead. Try it first: nothing is sent and nothing is changed.
Each run has its own page. If a run fails, the flow shows one notice and its owner gets one e-mail, and the flows list has a "Needs attention" view.
••••••••••••••••
A third way of working does not ask.
So you know before the demo.
Databases and any web API, each person as themselves where the system allows it.
Data connectionsQuery Studio, size estimates and cheaper rewrites.
DashboardsRuns as a person, tried first, with a page for every run.
WorkflowsAlso behind these answers: History engine.
In the demo we connect one of your systems, and you ask the questions.