ERP, schedules, mail and files continue to hold the operational record.
PlatformNexcore
One operating layer for your ERP, email, files and project sites.
Nexemble products, from project cost control to vendor management and field tracking, run on a shared platform. They work with the same project, people and supplier records, workflows, data warehouse and AI audit trail. That shared foundation helps each product work in context across your organisation.
Project, people and supplier information moves with the workflow instead of being re-keyed.
Nexcore prepares the work, then keeps review, approval and enterprise execution visible.
A platform built to work together
Connect enterprise information, workflows and intelligence.
The shared foundation brings systems, people, services, analytical data, agents and documents into the context used by Nexemble products.
Connect to the systems you already use
Nexemble connects with Odoo, Microsoft 365 mail and SharePoint through Microsoft Graph, and Primavera P6 schedules. Its adapter pattern supports connections with other ERP systems. Your ERP remains the system of record. Nexemble reads and analyses its data, then writes back through its own API according to your approval rules.
Put your procedures into motion
Define workflows in YAML and run them on a durable workflow engine. Processes such as purchase orders, vendor onboarding and expense claims can run over time while keeping their place. Approvals can include timeouts, escalation and delegation, with approvers determined from your organisation structure.
Keep people and services in sync
Platform changes generate events that can reach people as inbox items, email, mobile push notifications or Teams notifications. Events can also be shared with connected services without repeated polling. Alarm deduplication and rate limits help keep notifications useful.
Bring data together for analysis
Each customer has a ClickHouse data warehouse for ERP, schedule and platform data. dbt models that data into facts and marts for dashboards and the Data Agent. Multiple ERP instances and companies can feed a warehouse while keeping their records distinct.
Give agents a shared runtime
Agents run within the platform with access to tools, memory and per-turn evaluation. Model calls, tool calls and drafts are recorded in typed tenant records, where they can be reviewed turn by turn.
Make documents and knowledge easier to use
Shared services support schema-driven document extraction with confidence bands, and knowledge indexing across SharePoint and email. Canonical entities help connect information across sources for use by products and agents.
How the platform connects the work
Enterprise context in. Shared products and accountable action out.
Nexcore connects enterprise sources to shared records, workflows and intelligence. People review consequential actions, while approved updates continue through the systems already in place.
01 · Existing systems
Enterprise context
- ERP records
- Primavera project schedules
- Mail and SharePoint sources
- Field and supplier inputs
02 · Connected information
Integration & processing
- ERP and project-system connections
- Document and message processing
- Structured records and source links
03 · Shared operating layer
Nexcore
Shared recordsProjects, people, suppliers, documents and financial context
Workflows & reviewConfigured procedures, routed work and accountable decisions
Data & intelligenceWarehouse models, retrieval, extraction and analysis
Identity & auditAccess controls, tenant configuration and inspectable activity
04 · Products and people
Work in context
- Web, mobile and supplier experiences
- Analysis, drafts and visible evidence
- Human review and approval points
From review to execution
The ERP remains the system of record.
- Person reviews
- Action is approved
- Enterprise system updates
Products share the foundation. Connected records and workflows can carry context from procurement into cost control, document review or another supported product experience.
Each environment fits the operation. Connectors, interfaces, deployment and responsibilities align with the customer systems and procedures they support.
Security and tenancy
Your tenant, your data, and permissions built into the access path.
Enterprise identity, platform grants, customer-specific isolation and deployment choices shape each customer environment.
Identity and accessYour tenant, your dataConnect enterprise identity to each customer environment.
Keycloak supports single sign-on through Entra ID and other OpenID Connect identity providers. Directory groups and roles can inform what people are allowed to see and approve.
Permission enforcementPermissions built into the access pathApply grants and operating scope before information reaches a person or service.
API access is denied unless a grant is in place. Permissions are checked at the gateway, while data-level scope keys can limit access by company or division, including at the warehouse row level.
Customer-specific isolationKeep every customer environment separateEach customer has separate data stores, credentials and supplier-facing access.
Each customer has a separate tenant with its own database, warehouse, connector credentials and encrypted API keys. The supplier-facing portal runs separately from internal consoles.
DeploymentDeploy to suit your requirementsRun Nexemble on customer infrastructure or in a selected region.
Nexemble can be deployed on customer infrastructure or in a selected region. In-country processing depends on the chosen hosting arrangement.
Each customer has a separate tenant with its own data stores, connector credentials, encrypted keys and configured access rules.
AI you can audit
Choose the models you use. Keep the work accountable.
Model choice and cost remain visible, business calculations remain deterministic, and people retain responsibility for consequential action.
Platform controlHow it works
Model choiceChoose the models you use
Tenant-scoped connectors support Anthropic, OpenAI and Gemini, with encrypted API keys. Self-hosted models can be used for extraction and embeddings when text cannot be sent to an external API.
Cost visibilityTrack model costs
Model calls are recorded with the person, task and applicable price at the time of the call. Rate changes can be reflected in cost history without rewriting or backfilling records.
Deterministic calculationKeep business calculations deterministic
Scores, exposures, budgets and totals are calculated by code and SQL over your data. Models can explain the results in plain language, with the underlying reasons available for review.
Human responsibilityKeep people in control
The platform can prepare drafts, route approvals and raise alarms. A person remains responsible for sending messages, approving purchases and closing tasks.
Products on the platform
Start with one product. Build on the same foundation.
Because products share project, person and supplier records, information can carry across workflows. A purchase order created in procurement can appear in cost control, while a NexSentinel risk can reference a supplier already onboarded through the vendor portal.
Project, supplier and financial workflows
Carry approved commercial context into project controls, procurement commitments, cash visibility and corrective action.
Knowledge, documents, field and decision workflows
Relate questions, documents, operational signals and exceptions to the people, projects, suppliers and assets they affect.
Commercial and engineering workflows
Turn enquiries, tenders, drawings and specifications into reviewable requirements, estimates and responses.
For IT teams and implementation partners
Configure the platform around your procedures.
Workflows, connectors, dashboards and interfaces use the same platform foundation while reflecting the customer’s operating environment.
Configure workflows around your procedures
Configure workflows, connectors and dashboards without changing the platform source code.Workflows are configured in YAML, connectors are managed through tenant settings, and dashboards can be published as templates on the customer’s warehouse. Partners can map customer procedures and configure a tenant without changing the platform’s source code.
Interfaces for every team
Use the web app, mobile apps, supplier portal and platform APIs.Use the web app for internal teams, the Android and iOS mobile app for field work, and a separate portal for suppliers. REST and gRPC APIs use the same gateway and permission model as the applications.
Review where Nexcore fits in your operation.
Walk through one workflow, the systems and information it depends on, and the decisions that need to remain accountable.