Tender and procurement resources
What procurement and tender teams need, in one place.
This page summarises the architecture, deployment options, security posture, data handling, support model and assurance approach most structured questionnaires ask about, and states plainly what we will supply beyond this page.
- summary areas covered here
- 6summary areas covered here
- questionnaire responses supported
- Structuredquestionnaire responses supported
- detailed evidence and diagrams
- On requestdetailed evidence and diagrams
- contact for procurement queries
- Namedcontact for procurement queries
Architecture summary
How Nexus is structured.
- Execution model
- A control plane holding workflow definitions, policy and audit metadata, separated from an execution plane that runs workflow steps against your systems.
- Integration surface
- 1,480+ pre-built actions across 43 product families, plus 46 trigger sources, plus code nodes and direct database, API and RFC protocol support.
- AI components
- Self-hosted model endpoints, a model registry, knowledge bases and guardrails, run inside your environment rather than called out to an external API.
Deployment options
Where Nexus can run.
- On-premises data centre
- Full deployment inside your own data centre with no dependency on external connectivity for execution.
- Private cloud
- Deployment into a customer-controlled private cloud environment, Kubernetes-agnostic.
- Sovereign or regulated cloud
- Deployment into a cloud region meeting specific sovereignty or regulatory requirements, with execution kept inside that boundary.
- Air-gapped or disconnected
- Deployment into networks with no external connectivity, including the mechanisms for moving updates and model artefacts into the environment.
Security and access control
How identity and access are governed.
- Identity
- SSO and MFA integration, with role-based access control.
- Directory integration
- AD/LDAP integration for existing identity sources.
- Secrets management
- Vault-managed secrets rather than credentials stored in plain configuration.
- Audit and observability
- Execution records covering triggers, data retrieved, decisions made and actions taken, retained for audit and incident review.
Data handling
What stays inside your boundary.
Sovereignty in the Nexus sense means the data processed by workflows, the models used, the credentials referenced, the execution itself and the resulting audit records stay under your control. This is a property of where the platform runs, deployed inside your environment, rather than a policy layered on top of infrastructure you do not control. Specific data handling detail for your deployment topology, including retention periods and backup approach, is confirmed as part of a deployment plan.
Support model
How engagements are staffed.
Named engineering contact
Deployment and support engagements are run by named engineers rather than an anonymous ticket queue during onboarding and critical periods.
Deployment architecture support
Solutions architects work with your team on topology, sizing and integration planning before go-live.
Ongoing operational support
Support scope and response expectations are defined per engagement and confirmed in writing before contract.
Assurance approach
How we describe alignment with frameworks.
Nexus execution records link configured controls to decisions and system actions. Framework mapping connects those records to the requirements in your questionnaire. Your organisation and auditors assess the deployment and its evidence against the standards applicable to your sector.
What we supply on request
Beyond this summary.
We respond to structured questionnaires directly
This page is a starting summary. For a formal tender or procurement process, send us your structured questionnaire, security assessment or RFP document and we will respond against it directly, including architecture diagrams, product datasheets, and responses to security and data handling questions.
Where testing, technical validation or reference architecture review requires named personnel or authorisation from your side, we will state that clearly in our response rather than assume it.
Architecture session
Send us your questionnaire.
Attach your structured questionnaire, RFP or security assessment and tell us the timeline you are working to. We will respond directly against your document.