Skip to content
Close
SEARCH
Get a demo
Get a demo
Platform Overview Your business teams maintain the data that drives analytics and AI, directly on your enterprise data platform.
The platform
Built for business teamsYour team edits its own data in a familiar grid, guided by value help.
GovernedEvery change is validated at entry, authorized to the row and logged.
Powering AIBusiness teams and their AI assistants maintain the data your AI models use.
By data platform
SAP Business Data CloudWrite validated data back to SAP Datasphere, inside your spaces and roles.
DatabricksWrite validated data back to Databricks, inside your schemas and roles.

SnowflakeComing SoonMicrosoft FabricComing Soon

NextTables also runs on PostgreSQL.

On-premise add-onNextTables for SAP BW Your SAP BW users maintain data in a validated grid, on SAP authorizations.
NextTables in one deck

See real use cases and how NextTables writes validated, authorized data back to your platform, in one file you can forward.

Get the deck
By team
MarketingKeep product groups and campaign reference data current, validated as you type.
ESGCollect subsidiary ESG data, validated at entry and traced by row.
FinanceMaintain the mappings and rule tables your reports run on, checked at entry.
Product master data grid in NextTables: a group ID picked from the value helpMarketing data, current and trusted, on your enterprise data platform

See the Marketing solution

ESG upload preview in NextTables: an unknown subsidiary ID marked as an errorCollect, maintain, and monitor ESG data on the platform you already run

See the ESG solution

Upload preview of a cost center mapping in NextTables, with one error and one warningNextTables lets finance maintain the reference data its management reports run on

See the Finance solution

The NextTables deck

The deck covers use cases, architecture and pricing in one file.

Get the deck
Learn
Knowledge BaseFind how-to guides, configuration reference and troubleshooting steps.
WebinarsJoin a live session or watch the recording, with demos and Q&A.
BlogRead how business teams keep the data behind their reports correct.
Stay current
ReleasesSee every new feature and connector, month by month.
Get help
Support PortalCustomers raise and follow their support tickets in one place.
Contact usTalk to the team that builds NextTables.
Keep up with what ships

Each edition brings new features, design patterns from real setups and builder playbooks from the team building NextTables.

Get product updates
Help from the NextTables team

Pick the product, describe the issue and attach a screenshot, then follow every reply in the Support Portal.

CTA

Evaluating NextTables? Talk to the team that builds it.

Validated, authorized, auditable

Every change checked, authorized and on the record

Entries are checked against your master data before they are written, roles decide access down to the row, and your business data stays in your platform.

Upload preview in NextTables stopping one value that does not exist in master data, with the reason shown at the cell

Validated before it is written

Every entry is checked against your master data and your rules before it reaches the platform. The message goes to the person who can fix it, and only values that pass your checks are written.

Checked against your own master data

A master data object reads a table, a view or a remote table in your platform, or in another connected one. In this upload of cost center mappings, cost center 99999999 is refused with the exact key that failed: “Value (EU01, 99999999, 1000) does not exist in master data”.

An upload preview in NextTables with the message Value (EU01, 99999999, 1000) does not exist in master data at the cost center cell

The NextTables grid of an ESG emissions table showing No item found for the subsidiary key BN4320

The same check in the grid

In the grid, the same master data stands behind the value help. A subsidiary key with two digits swapped, BN4320 instead of BN4230, finds no match while it is typed, so it never reaches your ESG figures.

Rules your key users write

Each field carries its own validation rules for text, patterns and expressions, with the message a person reads when an entry misses one. This note asks for a reason whenever a mapping changes during the year, so the next controller knows why.

The validation settings of the note field in a NextTables form, with the message A change during the year needs a reason

Six checks and rules, and where each one is set

Swipe the table sideways to read each row in full.

Check or ruleSet inExample
Master dataField definitionThe cost center (EU01, 10001400, 1000) must exist in your master data
Unique keyTable keyEach combination of controlling area, cost center and valid-from date appears once
Required ifForm conditionA note becomes required when a mapping starts during the year
TextValidation ruleA comment between 10 and 500 characters
RegexValidation ruleAn order number in the pattern PO-123456
ExpressionValidation ruleA discount between 0 and 30 percent

One rule on every entry path

A rule is configured once and applies wherever data is written: the form, inline editing in the grid, file imports, API writes and an AI assistant through the NextTables MCP server, with the same message in each. The upload above refuses the April mapping without a note, just as the form would.

Uploads are checked row by row

A file goes through the same rules as a keyed entry. The preview lists every row with its outcome and reason, and Finish stays locked while a row in error remains.

Your own validation code, for checks across rows and tables

Some checks need more than one value to decide. With pro-code validation, your developers write that logic as code, with read access to other tables in your platform. NextTables runs it on every entry path, and the person entering the value reads its message at the field, as with every other rule.

Coming Soon

Checks it opens up

  • Allocation shares that add up to 100 percent for each cost center
  • A limit kept in another table, such as a credit limit per customer
  • A valid-from date that follows the previous version of the same key
  • One active mapping per cost center on any given day

Four layers decide who may change what

Authorization in NextTables is layered, so a broad grant on one layer can be narrowed on another. Each layer is independent and they combine. Roles cover two things separately: maintaining data, and creating the objects that hold it.

Roles: what a person may do, and where

A role is granted on a folder and inherited by its subfolders, with read, write, create and delete rights. Most tenants need three archetypes: reader, editor for the people who maintain data every day, and key user for the smaller group who may also create and change tables.

Row-level security: which rows, for which personEnterprise

A row-level security object matches the signed-in user against a control table and decides which rows they may read and, separately, which they may write. The control table can be one you already maintain in the platform, read through the connection, or one maintained in NextTables by the people accountable for it.

Folders, the security backbone

Folders mirror your data domains, for example finance, HR and supply chain, and they are the inheritance boundary for everything above them. Restricted areas sit as subfolders inside a domain. Many customers use top-level folders as environment roots for development, test and production.

Connection scoping

A connection to a sensitive source is mapped to the folders allowed to build on it, so an application in a marketing folder stays out of the HR schema whatever its roles say. Master data objects built on a connection inherit that scope. Widening a scope is itself a site-level permission.

Row-level rules apply at the field

A person who enters a value outside their rows is told at the field, before anything is written. The same rule applies in the grid, in a form, by upload and through the API, and read and write access are decided separately.

The Add row dialog in NextTables refusing a subsidiary outside the user's rows, with the message at the field

The login methods page in NextTables with Microsoft and Google identity providers enabled

Sign-in through your identity provider

People sign in through your identity provider, Microsoft Entra ID or Google Workspace, and are authorized inside NextTables. The platform is reached through one technical connection user per schema, so maintenance-only users stay outside the platform's user management and licensing.

Table filters for everyone

An administrator can narrow a table for all of its users with filters, including values of the signed-in user such as their email or language. Filters scope what a table shows; row-level security decides access.

The filter settings of a NextTables table with the value list current user: language and current user: email

How the layers land on each platform: SAP Business Data Cloud (one Open SQL schema per space) and Databricks (one login role per Lakebase schema).

Platform accounts stay with the people who need them

NextTables reaches your platform through a technical connection user. Business users sign in through your identity provider and are authorized inside NextTables, so IT keeps platform access for the people who belong there.

Connections scoped by your administrator

Each connection points at the schema an administrator chose, and folders decide who may build on it. The platform's user management and licensing stay with the people who work on the platform itself, while reports read directly on the platform keep their own accounts.

The database connections in NextTables: two SAP Datasphere spaces and one Databricks database

An audit log of every change, stored in your own platform

EnterpriseFor every table that tracks its data history, NextTables records each change in an audit log: who changed what, the new value and when, for data and for structure such as a new column. The log is a regular table inside your own platform, so it stays within your security and retention boundaries and can be queried with the tools you already have.

Data history, set per table

Data history is on for every new table, and administrators can switch it off per table in its settings.

The audit log is part of the Enterprise edition; the pricing page lists what each edition includes.

The settings of a NextTables table with the option Track data history selected

What one entry in the log holds

Swipe the table sideways to read each row in full.

TableRowColumnNew valueChanged byChanged at
Cost center mappingEU01 · 10001400 · 1000NoteMoved to logistics in Aprilcontroller@yourcompany.com2026-10-28 14:12

  1. A change is made

    It happens in the grid, in a form, by upload, through the API or from an AI assistant through the MCP server, by a signed-in person under their role.

  2. It is validated

    It is checked against your master data and your rules. Invalid values stop at the field, so only validated values reach the log and the platform.

  3. It is written

    It goes into your platform through the connection your administrator scoped, and only there.

  4. It is recorded

    The audit log row lands next to the data: who made the change, the table, the row, the changed column, its new value and the time.

Full audit trail

Coming Soon

The change history of a row, in the product interface, built on the same audit log that is on the record today.

Approval workflows

Coming Soon

For sensitive updates, edits are proposed, reviewed, and only then written, for people and for agent-driven changes alike. The decision becomes part of the record.

Safe rollback

Coming Soon

Any change can be reverted to its previous value by an authorized user, with the rollback itself recorded alongside the original change.

Your business data stays in your platform

NextTables stores configuration metadata only: applications, validation rules, roles and connection parameters. Business data passes through during reads and writes and remains exclusively on your enterprise data platform, so your platform holds the only copy.

One storage location

The tables, the views and every row live in SAP Business Data Cloud, Databricks or PostgreSQL. Reporting reads them the way it does today.

Live connections, in real time

Reads and writes go through the platform's own interface in real time. A maintained value is available in every dashboard at once.

A clean exit

Switch the connection off and the schema, the tables, the views and the data are exactly as they were. Your configuration can travel with you too, through the same export used for promotion. Coming Soon

Security and data residency

This table answers the questions a security review asks first. The platform-specific connectivity facts are on the platform pages.
ConcernHow it is handled
HostingNextTables runs as a managed SaaS application on Microsoft Azure in the EU region Belgium Central, with a dedicated metadata database per tenant. Additional hosting regions follow for specific data residency requirements. Coming Soon
EncryptionEncryption at rest and in transit for every tenant.
Backups and recoveryAutomated backups and disaster recovery for the tenant's configuration; your business data stays inside your platform.
IdentitySign-in with Microsoft Entra ID, Google or email and password. With sign-in through your identity provider, leaving the company removes the access.
Data processingA published privacy policy and a GDPR Article 28 data processing agreement.
Platform accessOne technical connection user per schema, scoped to that schema, with the IP address shown in the connection dialog for your allowlist. Rotating a password is one value in one field.
Support and releasesAn enterprise support model with one named path for your team, and a monthly release cycle, 30-plus releases and counting.

Frequently asked questions

1. Where are validation rules defined and executed?

In NextTables, per application, against the master data tables the app is connected to. Every rule runs at the point of entry, ahead of the write, on every channel that writes data.
2. Can we reuse the access tables we already maintain in the platform?

Yes. A row-level security object can read a control table in your platform through the connection, so one source of truth serves the platform's own access controls and NextTables alike.
3. Where is the audit log stored, and can we query it?

Inside your enterprise data platform, as a regular table next to the data, for every table that tracks its data history. It can be queried with your existing platform tools today; a full audit trail in the product interface is on the roadmap.
4. What does the platform's own log show for a change?

The technical connection user, because that is what a database connection is. What changed through NextTables, who changed it and when, is in the NextTables audit log next to the data.
5. Does NextTables need an account on our data platform for each business user?

One sign-in per person, through your identity provider; the platform is reached through one technical user per schema that your administrator creates.
6. What happens to our data if we stop using NextTables?

It stays where it has been the whole time: in your platform. Switch off the connection and the schema, the tables, the views and every row remain as they are.

Bring your security review

Take the deck to the review first, or spend half an hour with us on your access model, your control tables and your audit requirements.

Get the deck
Get a demo