ABENDLY · AI FOR INTEGRATION MESSAGING

Abendly finds what’s wrong in your messaging, from your logs in seconds or by watching your queues before it happens.

Diagram: messages moving between a store app, payments, a database, a partner bank and a mobile app, watched over by the Abendly AI.

Log Intelligence

Available today

Give us your MQ, CICS and DB2 logs, nothing else. Abendly reads millions of lines in seconds, finds the issue, and gives you the fix, step by step. No connection to your messaging systems. No access at all.

Request a demo →

The monitoring agent

Design-partner pilot

Connect Abendly read-only to your messaging estate, across platforms, read as one estate. It watches everything around the clock, warns you while there is still time, and hands you the diagnosis and the fix when things go south.

See the live demo →
The product

What Abendly is, exactly.

One engine, two doors: a logs-only product that needs no access at all, and a monitoring agent that connects read-only. Log Intelligence reads MQ, CICS and DB2 logs, on z/OS and distributed.

Connects to

Your queue managers, through a read-only, display-only service account.

The analyser and health check need no connection at all. Just log files you export.

Watches

Queues Queue managers Channels CF structures MQ events Error logs

Every signal measured against its own baseline. Each signal, in the live demo →

Outputs

The root cause, a confidence level, how much time you have, and the exact MQSC to run. In the console and to Slack.

One estate, both platforms: when a channel fails on z/OS because the remote queue manager is down on distributed, the finding names the cause on the other platform. One diagnosis, not two alerts on two consoles.

Never does

Put, get, or browse an application message. Start, stop, or alter anything. Execute a fix.

The queue manager itself enforces it, through OAM on distributed and RACF on z/OS. Your authority, revocable by you.

Runs

Inside your environment, around the clock, connecting outbound only.

Inference runs on your AI account: Anthropic, Azure OpenAI, Amazon Bedrock, IBM watsonx, or self-hosted.

Costs

A flat licence per estate, in two tiers: full support, or patches only.

Your model tokens stay on your account, capped by you. We never mark up model usage.
Caught early

Your queue starts filling at 09:42. You know at 09:51. Nobody gets paged.

PAYMENTS.INBOUND.QL · trend detectedbefore failure
watch09:51 · ~14 min of runway
Queue depth climbing 3x faster than its 30-day baseline. At this rate it reaches MAXDEPTH before the inbound channel can drain it.
confidence highcause consumer not committinghost [HOST_1]
recommended fix · MQSC
1find the stalled consumer: DISPLAY CONN(*) TYPE(HANDLE) WHERE(OBJNAME EQ PAYMENTS.INBOUND.QL)
2restart the consuming app on [HOST_1]
3confirm depth falling: DISPLAY QLOCAL(PAYMENTS.INBOUND.QL) CURDEPTH
Abendly does not run this. Your engineer reviews and executes, with time to spare.Awaiting your action
Read-only by design

It can see everything. It can change nothing.

The service account holds inquire and display authority only. The queue manager itself refuses anything more. Your own engineer runs the fixes it recommends. Abendly never executes them.

Full security model →
service account · scope
DISPLAY CHSTATUS
DISPLAY QLOCAL / QDEPTH
read SYSTEM.ADMIN.*.EVENT
STOP / START CHANNEL
ALTER / DEFINE / DELETE
PUT / GET / BROWSE application messages
Enforced by OAM on distributed and RACF on z/OS. You provision it, and you can revoke it.
Questions security teams ask

The hard questions, answered plainly.

Can Abendly change anything in our environment?
No. The agent connects with a service account that holds inquire and display authority only, enforced by OAM on distributed MQ and RACF on z/OS. The queue manager itself refuses anything more. Your own engineer runs the fixes it recommends. Abendly never executes them.
What actually leaves our network?
Raw logs never do. Hostnames, queue managers, channels, and user IDs are stripped to stable labels inside your boundary, before anything is reasoned over. With a self-hosted model, nothing leaves at all. The entire loop runs behind your firewall.
Whose AI does the analysis run on?
Yours. Abendly runs on your own AI account: Anthropic, Azure OpenAI, Amazon Bedrock, IBM watsonx, or a self-hosted model. Inference is billed by your provider and governed by your existing data agreements. We never resell tokens or mark up model usage.

Stop reading logs after the outage.
Start catching it before.

An agent in your environment, watching the estate that can't go down.

Request a demo

Point it at one queue manager and watch.

We'll connect a read-only agent to a single environment you choose, show it surface real findings from your own estate, and scope a deployment to your security and compliance requirements.

  • Read-only connection to one QM you pick
  • Deployment + data-residency review
  • Security questionnaire support

I'm interested in

Or email sales@abendly.io directly.

Thanks! We'll be in touch within one business day.