Messaging & integration

Write it once. Connect to anything.

One messaging annotation runs unchanged across 13 brokers, and a Vault-backed catalog of 25 connection types reaches every database, endpoint, file server and object store you integrate with — so switching infrastructure is a config change, not a refactor.

One messaging API, 13 brokers

You may see this described as "Kafka across 13 brokers." What it means: the same @NucleusListener and @NucleusPublish code runs against 13 different messaging systems. Your listener never knows which one is on the other end.

@NucleusListener(
    connector = "orders",
    topic     = "${orders.topic}",
    format    = MessageFormat.JSON,
    mode      = ConsumeMode.QUEUE
)
public void onOrder(Order o) {
    // first parameter type drives deserialization — no manual JSON handling
}
Apache Kafka · MSK, Event Hubs RabbitMQ · Amazon MQ Amazon SQS Amazon SNS Amazon Kinesis Google Pub/Sub Azure Service Bus Azure Queue Storage ActiveMQ · JMS Artemis · JMS Solace · native JCSMP IBM MQ · JMS

Every adapter implements the same SPI and mirrors the reference Kafka adapter's full feature set — three producer reliability tiers, manual-ack consume with dead-letter routing, keyed and headered listeners, batch and tombstone publish, and auto-reconnect.

A catalog for everything else

Where the messaging layer abstracts brokers, the integration connector service abstracts everything you connect out to — 25 connection types in a typed, client-scoped catalog.

Register onceForm-driven, per-type validated. Secrets go to HashiCorp Vault.
→
Resolve & connectThe runtime decrypts secrets and opens the native session.
→
Run operationsCataloged operations — or the native client as an escape hatch.
🌐

REST & SOAP

HTTP/HTTPS endpoints with typed request/response — the transport behind a workflow's CALL_SERVICE REST step.

🗄️

Databases

JDBC datasources — query and execute against any relational database through one profile.

📁

File & FTP servers

FTP / SFTP file transfer, plus file watchers that let a workflow wait for a file to arrive.

🪣

Object storage

S3 / MinIO-compatible object stores for upload, download and delete on standardized paths.

🤖

AI providers

Provider-agnostic LLM access — Anthropic and OpenAI built in, multimodal, with classified errors and retries.

🔑

SSH hosts

Remote command execution over SSH against registered hosts.

📨

Email (SMTP)

SMTP endpoints for the transactional mail pipeline.

🔌

Sockets & SNMP

Raw sockets and SNMP agents — for the long tail of systems that don't speak HTTP.

Secrets never live in a config file or a payload — they're stored in HashiCorp Vault (KV v2) and decrypted only at the moment a session opens. The raw native client is always available for anything the cataloged operations don't cover.

The Nucleus connections console: a client-scoped catalog of registered integration connections by type, each with a health status and its Vault-backed configuration.
The connections catalog — register a connection once, per-type validated, with its secret in Vault and a live health status.

Read the connector reference, or see the catalog live.

Connector reference → Live demo →