Code and extensibility
Low-code speed without a low-code ceiling.
Assemble standard steps visually, then run real code in the language and libraries appropriate to the requirement, without leaving the governed workflow.
Code inside the process
A code node is an ordinary step in the graph. It receives typed input, returns structured output and appears in execution history like any other node.
- runtime language families
- 8runtime language families
- integration actions
- 1,480+integration actions
- backed secrets
- Vaultbacked secrets
- code execution
- Auditedcode execution
The problem
Build the last mile instead of redesigning the requirement.
Predefined components cover what is common. They cannot anticipate the calculation your finance team agreed with an auditor, the encoding a partner insists on, or the internal service with an interface nobody else has.
Where low-code platforms stop
Most low-code tools handle the standard eighty percent well. The remaining work is usually the reason the process was hard in the first place, and it is where teams are told to change the requirement to fit the tool.
The usual workaround has a cost
Pushing that logic into an external microservice means another repository, another deployment pipeline, another set of credentials and another component to monitor, for a piece of logic that belongs to one step of one process.
What Nexus does instead
The custom logic runs as a node in the workflow. The process stays visible to the people who own it, and the developers who wrote the logic keep their language, their libraries and their tests.
Runtime families
Eight runtime language families, presented equally.
Nexus does not have a preferred language. Teams select the runtime that matches the task, the libraries already in use and the skills they already have.
- Python
Data transformation, document handling and AI-adjacent processing.
- Bash
Systems work, file handling and command-line tooling.
- Go
Efficient utilities and services with straightforward deployment.
- Java
Existing enterprise libraries and established JVM logic.
- .NET
Microsoft and enterprise application logic.
- PHP
Existing web and enterprise libraries already in use.
- PowerShell
Microsoft 365, Windows and administrative operations.
- JavaScript / TypeScript
API-oriented logic and typed web ecosystem code, through Deno.
Task fit
Choose the language the task actually calls for.
These are common fits rather than restrictions. Any of the supported runtimes can be used wherever it is the right tool for the requirement.
Python
Data transformation, document handling and AI-adjacent processing.
Bash
Systems work, file handling and command-line tooling.
Go
Efficient utilities and services with straightforward deployment.
Java
Existing enterprise libraries and established JVM logic.
.NET
Microsoft and enterprise application logic.
PHP
Existing web and enterprise libraries already in use.
PowerShell
Microsoft 365, Windows and administrative operations.
JavaScript / TypeScript
API-oriented logic and typed web ecosystem code, through Deno.
Contract
What a code node receives, and what it returns.
A code node is not an unmanaged script. It participates in the workflow through a defined contract.
Inputs from previous nodes
Results from connectors, triggers and earlier steps are available as structured input.
Vault-backed secrets
Credentials are resolved from the vault at run time and are never written into the code.
Packages and libraries
Existing libraries can be used where the runtime and environment support them.
Structured output
Returned values are typed for downstream nodes rather than parsed from free text.
Captured results and output
Standard output and returned results are retained with the execution record.
Governed execution
Code runs under controlled, sandboxed execution within the platform's approved deployment model.
Interfaces
Protocols and escape hatches.
Where a system exposes an interface, Nexus uses it. Where it does not, there is still a supported route.
HTTP
REST and other HTTP services with configurable authentication.
GraphQL
Typed queries against modern service layers.
SOAP
Established enterprise service endpoints.
SAP RFC
Native calls to SAP function modules.
MSSQL and Oracle
Direct database reads and writes.
SSH
Command execution on systems without a modern interface.
Browser automation
Used only where no programmatic interface is available.
Code nodes
Anything the above cannot express, written in the appropriate runtime.
Reuse
Write it once, use it where it is needed.
Custom logic becomes an asset when other teams can call it without reading it.
Modules and sub-workflows
A complete graph exposed to a parent workflow as a single node.
Actions
Configured steps applied consistently across processes and teams.
Functions
Capabilities published for on-demand invocation.
APIs and webhooks
Workflows exposed to other systems through defined entry points.
Governance
Custom code does not mean ungoverned code.
The controls that apply to a visual step apply to a code node, which is the reason custom logic can be allowed in the first place.
Secrets stay outside the code
Credentials are held in the vault and referenced at execution time, so they are not embedded in source, copied between environments or exposed in a code review.
Roles and workspaces
Permissions determine who can author, publish and run code steps, and workspaces keep teams and environments separated.
Logs and execution records
Output and results are retained with the run, so a code step can be explained after the fact like any other node.
Versions and auditability
Draft and published revisions keep changes deliberate, and the execution history shows which version produced a given outcome.
Stakeholders
Useful to developers without becoming opaque to everyone else.
Developers
Use the right language and existing libraries instead of reimplementing logic inside a constrained expression editor.
Architects
Avoid standing up unnecessary external microservices for bounded logic that belongs to a single process step.
Operations
See the custom step inside the process, with its own status, output and rerun path in execution history.
Business teams
Keep low-code visibility of the process even after organization-specific logic has been introduced.
Boundaries
What Nexus is not.
Extensibility has limits, and being clear about them makes the rest of the claim credible.
Nexus is not a replacement for every application your organization runs. It does not replace hardware systems, and it is not a substitute for specialist commercial products that must remain the system of record in their domain.
What it does is orchestrate, integrate and extend those systems. Almost any functional or infrastructure requirement can be assembled as a governed workflow, with the honest exceptions being genuine hardware dependencies and capabilities that do not yet exist in the systems being orchestrated.
Architecture session
Bring the requirement your low-code tool could not complete.
Send us the step that forced a workaround: the calculation, the legacy interface, the library that only exists in one language. We will show how it runs as a governed node inside the process.