Six things are shared. That is the whole of what makes it one platform.

A suite becomes a platform when the domains stop rebuilding the same foundations independently. In continON there is one organization, one answer to what a person may do, one place definitions live, one set of services, one record layer, and one defined edge to everything outside. Every operational domain resolves against those, and none of them carries its own copy.

Request a demo How the six compose

How to read this page Below, the six foundations stay where they are while work from five different domains passes them. Each piece of work publishes which foundations it resolves against — and which it does not use. Nothing uses all six.

The six, and what each one holds.

The organization
One tree of units, nested to any depth and spanning locations, and the positions placed inside it as seats.
The organizational model
Authority
One identity for the whole suite, and what a person may do resolved from the seat they hold and the licence their organization holds.
Identity & access
Definitions
Processes, forms, documents, reports, dashboards and queries, stored as definitions and interpreted at run time rather than released as code.
Builders
Shared services
Documents, workflow, tasks and work orders, notifications and reminders, reference data and reporting — provided once, called by every domain.
The document service
One record layer
The domains read and write the same records rather than exchanging copies, so a record keeps its history when it crosses a boundary.
How the layers compose
The outside edge
Databases you already run, credentials your organization registers, and the exports that leave — the defined ways in and out.
Integrations & data

The same six, under five different kinds of work.

Purchasing & supply

A purchase request becomes stock on a shelf.

Someone raises a request, it is approved, goods arrive, and the receipt lands against a warehouse and against the ledger.

The organization: Approval resolves to the seat above the requester, not to a named manager.
Authority: Whether this person may raise it at all comes from their position and their licence.
Definitions: The stages, the form and the generated document are definitions, not a release.
Shared services: Notifications, the generated PDF and the request history are shared services.
One record layer: The receipt is the same record the warehouse and the ledger read.
The outside edge: Not used here.

Workforce

A seat changes hands.

One person leaves a position, another is assigned to it. The assignment is dated, so the organization keeps the history of who held the seat when.

The organization: The seat is the object being reassigned; the unit it sits in does not change.
Authority: Access moves with the seat. Nothing is granted or revoked by hand.
Definitions: Not used here.
Shared services: Anything that was targeted at that seat now reaches the new holder.
One record layer: The previous assignment stays on the record with its dates.
The outside edge: Not used here.

Finance

A cost is posted against a department.

An entry lands in the general ledger scoped to the unit that incurred it, with the currency that unit works in.

The organization: The department is a unit in the same tree that HR and supply chain use.
Authority: Who may post, and who may only read, resolves per form and per action.
Definitions: Not used here.
Shared services: The report that shows it is built once and permissioned by seat.
One record layer: The cost refers to the work that caused it rather than restating it.
The outside edge: Not used here.

Work management

A field task consumes material.

A task is scheduled, matched to someone with the right skill, and the material it uses is allocated — which moves warehouse stock.

The organization: The person is matched through the position they hold, not a spreadsheet.
Authority: What they can close, and what needs a second pair of hands, comes from the seat.
Definitions: The task type and what it must capture are configured, not coded.
Shared services: Tasks and work orders are a shared service, not a work-management feature.
One record layer: The stock movement is the warehouse’s own record, written once.
The outside edge: Not used here.

Reporting

A report reads a database you still run.

A saved query reaches a system that stays where it is, and the result is used by a report, a dashboard and a form.

The organization: The report is scoped to the units the reader is entitled to see.
Authority: Report and dashboard permissions are granted to seats and to partners.
Definitions: The query is a definition, and four other builders can consume it.
Shared services: Rendering and delivery are the shared reporting service.
One record layer: Not used here.
The outside edge: The external database is connected and queried, not copied in.

Sharing is a dependency, not a slogan.

Foundations that are genuinely shared are also genuinely load-bearing. The domains do not keep private copies of the document store, the workflow engine, the notification service or the reference data, which is why a document raised in one domain is the same document in another — and also why, if that shared service is unavailable, every domain loses those functions at the same moment rather than one of them degrading alone.

That trade is the reason the rest of this estate can make the claims it makes. It is worth understanding before you evaluate the rest of it, so it is stated here rather than in a footnote further in.

What each layer may see, and what would be rebuilt without it Where the whole of it runs

Watch one record cross a boundary.

A guided walkthrough on a sanitized demo tenant: raise something in one domain, and follow it — with its permissions, its documents and its history — into another.

Request a demo

All nineteen modules