continON is a product. Here is what it is built on.
continON is a configurable operating platform for running an organization. It is not a category list assembled into a suite: it started from one problem — that an organization’s structure, its people, its work and its records are the same subject, and software that splits them into separate systems makes everyone else do the joining.
Each statement below links to the page on this site where you can check it, because a company page is the easiest place in the world to assert something nobody can test.
What continON is built on
The organization is modelled before the work is.
Most operational software stores people and bolts a hierarchy on later. continON starts from the unit tree and the positions inside it, and a position placed in a unit becomes a seat. Access, approval routing, notification targeting and reporting scope all resolve against that seat — so a person leaving is an assignment ending, not a permissions project.
Check itOrganization & positions
How work moves is configuration, not a release.
Processes, forms, reports, dashboards, documents and queries are definitions stored as metadata and interpreted at run time. Changing one changes what the next request does, without rebuilding the applications around it. Where a requirement outgrows the designers, it is extended with SQL and JavaScript — which is why continON is described as configuration you can extend rather than as a product without code in it.
Check itBuilders
It is one system, not a suite joined at the login screen.
The domains share one identity, one organization model and one record layer, which is why a purchase raised on a warehouse floor can arrive at the ledger still carrying what happened to it on the loading bay. That coherence is the product; the module list is a consequence of it.
Check itHow it works as one platform
It runs on ground somebody names.
continON is delivered as one containerized workload through a governed release pipeline, on infrastructure we operate or on a cluster your organization controls. The application repositories own their source and cannot change where or how the product is deployed. Which of those two placements applies is recorded in the licence itself.
Check itDeployment & hosting
It does not require the estate you already run to disappear.
Databases and files an organization already operates can be queried where they are, through saved definitions that feed forms, reports, dashboards and generated documents. What crosses that boundary is named, and what is not supported is stated as not supported.
Check itConnect what you already run
How much of it is written down.
The usual way to convey the size of a platform is a number nobody can check — customers, countries, seats. Instead, here is what this site itself publishes, all of it open in front of you right now.
Where a screen has not been cleared for publication, the page says so rather than showing a different one. That rule is why some pages here carry no picture at all.
What this page does not say.
- No customer names, logos, counts or testimonials. continON has customers; which of them may be named publicly is their decision, not ours to pre-empt.
- No founding story, milestone timeline or headcount. Where a date or a number is not verified, the honest move is to leave it out rather than round it.
- No awards, certifications or market position. What is and is not certified is stated on the security page instead.
Orient yourself across the site
Ask us something this page avoided.
If a claim here matters to your evaluation and the linked page does not settle it, that is the conversation worth having.