Skip to content

Platform

One platform for all your processes

You build the data model, interfaces, flows, permissions and integrations in low code in the editor. If you wish, AI can take over the implementation in a draft that you review. However many applications you build, they all run on the same platform and pass through the same central permission check.

  • Built in the editor, with AI if you wish
  • Changes possible while the system runs
  • One permission check for every route in
  • As many applications as you need

What everything stands on

Three foundations every application shares

One model For everything you build A field you create once is available in forms, lists, reports, flows, permissions and the AI assistant.
One platform For every route in User interface, customer portal, interfaces to other systems, assistant and automation all work with the same rules and the same permission check.
Directly changeable Without installing a new version The configuration is not program code. You make changes in a draft and publish them while the system runs. If needed, you return to the previous state.

One process after another

Examples of processes on the platform

  • Incident management
  • Onboarding
  • Purchase requests
  • Complaints and 8D
  • Contract deadlines
  • Maintenance
  • Customer portal
  • Audit actions
  • Supplier approval
  • Access requests
  • Invoice checks
  • Document control
  • Fleet
  • Training records
  • Capex approval
  • Offboarding

The principle

A field created once is available everywhere

In many tools, forms, reporting, automation and permissions are kept apart, each with its own settings and its own vocabulary. Adding a field means updating it in several places, and one of them is easily missed.

In nexxcite, every part follows the same principle and is connected to the rest. Add a "cost centre" field for procurement and it is immediately available in the request form, the approval list, the budget dashboard, the approval rule and the access rule "own cost centre only". The assistant knows about it too.

You create it once and use it everywhere. That is what distinguishes a platform from a form builder.

  • Captured in forms, with required and validation rules
  • Sortable and filterable in lists
  • Aggregated in dashboards
  • Read and written by flows
  • Usable in permission rules
  • Visible to the AI assistant, within the user's rights

Build and design

What an application is made of

Six building blocks, each easy to understand on its own, together make up a complete business application. You build in low code, and if you wish, AI takes over the implementation.

Optional

If you wish, AI takes over the implementation

Data model, forms, flows, rules, roles, themes and navigation can also be created by asking the AI. The changes are collected in a draft where you can see each one individually. Nothing is published until a person approves it.

  • Changes go into a draft first
  • Origin of every change
  • Can be undone at any time
Building with AI

Data model

Data objects, fields, relationships and number ranges, structured the way your organisation works.

Explore

Interfaces

Forms, lists and dashboards from building blocks, adapted to each role and usable on any screen size.

Explore

Flows and rules

Branches, loops and deadlines in business hours, plus rules that apply without a flow.

Explore

Areas and themes

IT, HR, procurement, customer portal: each with its own navigation, theme, logo and strictly separated data.

Explore

Integration

An interface in both directions, connection to your directory, mailboxes, file storage and calls to other systems.

Explore

AI as an option

If you wish, AI takes over the implementation

You describe in your own words what the process needs. AI implements it with the same building blocks you use in the editor and places every change in a draft. You review the result, continue in the editor or discard it. Only what a person approves is published.

Draft
Draft
MB

Set up complaint handling: sales records the complaint, quality reviews it, an 8D report is required for recurring defects.

  1. + Data model Complaint
  2. + Form Record complaint
  3. + Workflow Review and 8D escalation
  4. + Rule Detect recurring defects
  5. + Role Quality assurance
  6. + Dashboard Complaints by cause
6 changes in the draft · none of them is live Review changes Approve
Draft
MB

From now on, every order above €25,000 also needs approval from the management board.

  1. ~ Rule Approval level by amount
  2. ~ Workflow Approval with escalation
  3. + Role Management · Approval
  4. ~ Notification Approval requested
4 changes · requests in progress stay untouched Review changes Approve
Draft
MB

Give the customer portal a light theme in our brand colours and our logo. Customers only see their own requests.

  1. + Theme Customer portal light
  2. + Navigation Portal menu
  3. ~ Role Customer (external)
  4. + Access rule Own requests only
4 changes · apply to the customer role only Review changes Approve

Reversible at any time

Building blocks, not source code

AI works with the same building blocks your team sees in the editor. No program code is created that someone has to understand and maintain later.

Every change in a draft

What AI proposes is collected in a draft, visible change by change. Nothing is published until someone approves it.

Only with the user's permissions

The assistant acts within the permissions of its user. If you can't change roles, you can't change them through AI either.

Undo changes

Every draft knows the state before its first change. One click takes you fully back to that state.

Traceable origin

Each change records which AI request it came from. So you can still see later why something was set up the way it is.

You choose the AI model

AI runs through your own account with the AI provider, or with an open model in your own data centre if you prefer.

Secure and run

What your IT team can rely on

When many processes run on one platform, what matters is what stays the same for all of them.

Architecture and governance

All applications share one model and one way of running them. That keeps application number twenty as orderly as the first.

Explore

Central permission check

One permission check for the user interface, portal, interfaces, AI and automation. There is no way around it.

Explore

AI at work

Assistants for employees and customers, with your keys, your model and your permissions.

Explore

For developers

REST with OAuth2, MCP in both directions, containers, clustering. The facts you need for a technical evaluation.

Explore

Platform and individual tools

On one platform, one permission model covers every process

The usual way

A separate tool for every process

The form sits in one tool, the automation in another and the reporting in a third. Permissions work a little differently in each.

  • Every application brings its own vocabulary and its own admin
  • Data moves from system to system by export
  • Every new application is a new project with a new licence
  • Nobody can say who sees what
With nexxcite

Every process on the same platform

One data model and one central permission check for all applications. Areas can be kept strictly separate where needed.

  • The same building blocks and patterns in every application
  • Data stays connected, without exports
  • Further processes need no further licence
  • One permission check for every route in

One consistent system

Application number twenty is part of the same system

Whether your team builds in the editor or the AI takes over the implementation, everything goes into the same model and runs on the same platform. One update, one way of operating and one security model apply to everything you build.

Architecture and governance

The path

From your first process to a platform in-house

  1. 01

    Start with the most pressing process

    You bring a process for which there has been no suitable solution so far. In the live demo we build exactly that process with you.

  2. 02

    Build together, learn along the way

    We support the first process all the way into production and train your team as we go.

  3. 03

    You build the second one yourselves

    The goal is for your team to carry on building on its own, in the editor and with the AI if you wish. The data model, roles and knowledge are then in place, so every further process goes faster.

  4. 04

    Roll out workspace by workspace

    HR, procurement, quality, a portal for your customers: each workspace has its own roles, its own theme and strictly separated data. You license the platform and the number of users signed in at the same time, regardless of how many applications you run.

FAQ

What customers want to know first

Do we need programming skills?

No. You build in the browser, in the editor or, if you wish, by asking the AI. Connecting other systems benefits from technical understanding, but you do not need a development team for it.

What if the AI builds something wrong?

Nothing changes until someone approves it. Every change the AI makes goes into a draft that you review change by change. If needed, you reset the draft to the state before its first change.

Where does the platform run?

As SaaS, in your own data centre or in your private cloud. Switching the operating model later does not mean rebuilding anything.

What does the second application cost?

No additional licence. You license the platform and the number of users signed in at the same time. Any number of applications is included, and there is no separate AI licence.

Will every department see everyone's data?

No. Areas can be separated completely, to the point where one cannot see that another exists. That applies to the user interface just as much as to interfaces, the assistant and automation.

Live demo

See the platform at work on your own process

We take a process from your organisation and build it live with you, in the editor and with AI if you wish.

  • A process from your organisation
  • Built live, in the editor or with AI
  • Remote or on site