Skip to the page

Solutions · IT & data

Answers for the business. Control for you. No data warehouse to build first.

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

Tarnwick Supply Co.Data · ConnectionsSample data
ConnectionWhose sign-in
1Whose sign-in each connection uses
Ordersweb APIsigns in as one accountshared with Sales and Operations, view
Orders reporting copyPostgreSQLan account that may only readboards only
AccountingOdooeach person signs in with their own login7 of 9 people linked
Trackerweb APIeach person signs in as themselvesTracking · next check in 42 min
FilesSharePointcompany access, each file's permissions followed
2Each person as themselves, where the system allows it
My access · Accounting Connected as Dana Ortiz, since 2 Oct, last renewed today
ReconnectDisconnect
Your secret is never shown back.
3Never shown back, owners included
  • 1Whose sign-in each connection uses
  • 2Each person as themselves, where the system allows it
  • 3Never shown back, owners included

Six questions IT and data leads ask.

  1. 01

    "Which systems can it read, and as whom?"

    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.

  2. 02

    "Which customer records have no sales person assigned?"

    The list of records with an empty field, and how many.

    Built withAI Assistant
  3. 03

    "How heavy will this query be, and is there a cheaper way to write it?"

    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.

    Built withDashboards
  4. 04

    "Are my history copies still feeding their charts?"

    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.

    Built withHistory engine
  5. 05

    "What would break if we removed this connection?"

    Before a delete, it lists the queries, boards, flows, analyses and history copies that use it.

  6. 06

    "Here is our order system's field guide as a PDF. What does the status 'Open' mean, and on which page?"

    It answers and names the page.

    Built withAI Assistant

One question, all the way to the follow-up.

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).

  1. 1

    Ask.

    "Which customer records have no sales person assigned?" The answer: 7 of 150 customers, with the list.

    AssistantData checksSample data
    Which customer records have no sales person assigned?
    Assistant

    7 of 150 customers have no sales person.

    CustomerSales person
    Marrowick Fit-Outnone
    Juniper Row Fit-Outnone
    Eskwith Property Servicesnone
    Showing 3 of 7Download to Excel
  2. 2

    Keep it.

    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.

    Data checksBoardSample data
    Data checksRefresh
    Customers with no sales person7Updated 07:02
    Products with no supplierNoneUpdated 07:02
    Invoices with no due date2Updated 07:02
    Queries behind this board
    Customers with no sales personRecommended
    Products with no supplierRecommended
    Invoices with no due dateRecommended
    Recommended: the query to reach for first
    • Recommended: the query to reach for first
  3. 3

    Follow up.

    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.

    Monday data checkFlow designerSample data
    Every Monday at 07:00
    Read customers with no sales personOrders · web API
    Make an Excel file
    Send the e-mailsales lead
  4. 4

    Watch it run.

    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.

How it reaches your systems.

  • A database (PostgreSQL, MySQL, SQL Server or MongoDB), any web system with an API, a ready-made connector, your Microsoft 365 files in SharePoint and OneDrive, and the documents people attach.
  • Ready-made connectors for Xero, QuickBooks, Odoo, HubSpot, Stripe, SendGrid, Notion, Airtable, GitHub and OpenWeatherMap, and any other system with an API. Xero and QuickBooks first ask your company to register an app with them.
  • Eight sign-in settings for a web system, from none to API keys, tokens, username and password, and OAuth 2.
  • It reads your systems when you ask. On a web system, a list it has read is reused for about two minutes, then read again.
  • A question reads only the lists it needs, at most 20,000 rows of each. To a web system it sends a few reads at a time and queues the rest, so a busy system is not sent a burst. If you would rather questions did not reach your live database, connect a copy of it, with an account that may only read. Answers are then as fresh as the copy.
  • Point it at a system's API. The assistant reads the API's own description, makes safe read-only test calls, and proposes the lists that answered. You approve, and they are added. In July we ran it end to end on a real, thinly documented, self-hosted engineering tool, with fixes made along the way.
  • Each connection keeps what its lists mean in your people's words: what one row is, what your team calls it, which list to read first. A new system starts with list and field names only; anyone who may edit the connection adds and corrects the meaning.
  • Sign-ins are typed into a form, never into the chat. They are kept in your company's own vault, and no read ever returns them.
  • Calls out of nexibi refuse private and internal addresses. Flows reach only the web addresses your owner allows.
  • nexibi runs as a managed service on Microsoft Azure in the European Union (Frankfurt). Its AI runs in Microsoft's EU Data Zone. Each company's data is kept in its own databases, apart from every other company's.
Data connections
Add from catalogData · ConnectionsSample data
OdooSales, invoices, stock and contacts
HubSpotContacts, companies and deals
StripePayments, customers and invoices
SendGridE-mail activity and contacts
GitHubIssues, pull requests and repositories
NotionPages and databases
Stripe
API key

••••••••••••••••

Test connection
Type only the key; it is tested before saving
  • Type only the key; it is tested before saving

Who sees what.

  • Everyone signs in as themselves, with a work Microsoft account or a username and password.
  • If your company uses Microsoft 365, your owner connects it once, and your people sign in with their work accounts. A Microsoft administrator approves the app once. Once Microsoft 365 sign-in is on, passwords stop working, so your own multi-factor and leaver rules apply.
  • Owners run the company's settings and people; members use what is shared with them.
  • Everything people save is private until they share it, with a person, a team, a role or everyone in the company (view only). Sharing a board also shares the data behind it, only what the sharer may share, and says first what it cannot.
  • On a shared web system, an owner can let each person see only their own rows, their team's, or their branch's. This works on web systems, not on a database connection.
  • Where a system allows it, each person connects with their own account, so that system's own rights apply.
  • Bring departments in from your Microsoft directory's security groups, nested groups included. A share with a team reaches people who join it later.
  • Seal a department: nobody outside it sees in, owners and our staff included. An owner can open it only with a second person's approval, for 24 hours, and every read is logged in that department's Activity.
  • Anything of another company answers "There is no such …", and the attempt is logged.
  • The sign-in log keeps every sign-in and every refusal, with its reason, for 90 days. Switch someone off and their sessions end, the stay-signed-in cookie included.
  • The Activity page shows every time someone opened something not shared with them.
  • Hand a leaver's connections, queries, boards, flows, history copies and chats to a colleague in one step.
Trust center
Sami HaddadPeopleSample data
Sami HaddadMember · Sales North
Connections3
Boards12
Flows4
Sign-ins
Today, 08:12Microsoft work account · Windows laptop Yesterday, 17:40Microsoft work account · iPhone
Hand on their work
A leaver's work, moved in one step
  • A leaver's work, moved in one step

What it may change, and who approves.

A third way of working does not ask.

  • In the chat, the assistant asks before it acts. Anything it would send, share, write to one of your systems, or delete waits for a person's approval.
  • Each person chooses how much it asks. Manual: it asks before it creates, changes, sends or deletes anything. Auto, the default: it makes and changes your dashboards and saved work at once, with Undo, and asks before it sends, shares, writes to one of your systems or deletes. A third way of working does not ask. It exists only where we have switched it on for your company and your owner allows it.
  • Changes it makes for you can be undone for 24 hours. That covers what it changed without asking, not a change you approved on a card.
  • Writing to a system is off for every connection until your owner switches it on and approves each kind of change. Each connection keeps a record of every action proposed, approved, run, failed or declined, and who did each.
  • A flow does what its steps say. It runs as a person, and reaches only what that person may reach. Add an "Ask someone first" step and the flow waits for a person's yes.
  • Flows run on background workers: if one stops, another carries the run on from its last finished step. Each publish is a numbered version, and a run keeps the version it started with.
  • An owner can switch the assistant, or downloads, off for the whole company. Whole apps can be switched off too: Insights, Data, Flows or Agents. Their pages say so, and nothing is deleted.

Your data, start to end.

  • You own your data, and the answers nexibi gives you.
  • We do not use your data, your prompts or the answers to train AI models.
  • It keeps your chats (unless you choose not to save one), the files you attach, and the dashboards and queries you save. How long each is kept is on our privacy page. If you set up a history copy of a list, that copy is kept too.
  • Export everything as one file whenever you like, with stored passwords and keys left out.
  • If you leave, the company turns read-only, you have 30 days to take your data, and then it is deleted. Owners are told by e-mail at each step.

What it does not do yet.

So you know before the demo.

  • Sign-in with Google, Okta or other providers.Microsoft work accounts and passwords only.
  • Password reset by e-mail, and invitations by e-mail.An owner adds each person with a first password, or connects Microsoft 365.
  • A scheduled directory sync.Departments are brought in from Microsoft by hand.
  • Row rules on a database connection.They work on web systems.
  • Flows that read a connected database.They read systems with an API and the ready-made connectors.
  • Self-hosting.nexibi is a managed service.
  • Answers are graded on one connected business system so far.In the demo we connect yours and check the first questions together.

The engines behind these answers.

Data connections

Databases and any web API, each person as themselves where the system allows it.

Data connections

Dashboards

Query Studio, size estimates and cheaper rewrites.

Dashboards

Workflows

Runs as a person, tried first, with a page for every run.

Workflows

Also behind these answers: History engine.

Bring one system and an account that may read it.

In the demo we connect one of your systems, and you ask the questions.