Connect with ease
Configure inbound and outbound channels. Update connection settings without restarting the application.
YOUR INFRASTRUCTURE. YOUR RULES.
Different systems.
One unified flow.
Connect services, manage routes and track every message. M3 makes complex data exchange a clear, manageable process.
SELF-HOSTED / JAVA + SPRING BOOT / COMMUNITY & SCALE
MESSAGE FLOWINTERACTIVE DEMO
01 / INGESTION
ROUTING ENGINE
RULES → ACTIONS
RULES → ACTIONS02 / DELIVERY
KafkaServices and events
DirectoryFile directory
↳
SFTP → persist → rule → KafkaDEMOClick a source to change the route↖
FAMILIAR PROTOCOLS.FTP ↗SFTP ↳Kafka ⋮RabbitMQ ⇄Directory ▤REST API ⌘
01 / FEATURES
Less glue code.
More clarity.
Everything you need for messaging,
in one visual interface.
Define your own rules
Match headers, payloads and metadata. Route, transform, filter and enrich messages.
Follow every message
Inspect history, statuses, payloads and processing jobs. Investigate errors and manage retries in the interface.
02 / ARCHITECTURE
The interface rests.
The flow continues.
Management and processing are separate. Independent workers execute rules and deliver messages even when the interface is stopped.
Explore the architecture ↗▦ Control panel CHANNELS · RULES · MONITORING
▱
PostgreSQLMESSAGES + JOB QUEUE
Persisted ✓ Worker 01 Worker 02 Worker …
Multiple workers and pools are available in Scale
01Persist first
Messages and metadata are stored before receipt notifications are published.
02Retry on failure
A transactional outbox and delivery jobs retain pending work when a transport is unavailable.
03Keep a record
Processing statuses and execution results remain in the shared database.
03 / EDITIONS
Start small.
Grow with your flow.
A shared core for your integrations.
More capacity when you need it.
Community
TO GET STARTEDCore messaging in your own infrastructure.
Freefor internal use*
- All five channel types and REST API
- Visual processing rules
- Message history and retries
- Basic execution configuration
Scale.
TO SCALE UPCapacity management for a growing workload.
commercial activation
- Everything in Community
- Additional workers
- Multiple worker pools
- Queue-based autoscaling
* The licensing model is being prepared for the first publication. Community proposes free internal use without code modification or redistribution of builds. License terms and required details are still in draft form. Read the terms ↗
04 / QUICK START
Your first flow
starts here.
Clone Community and start the stack with Docker Compose. Then open the control panel at localhost:8080 and configure your first channel.
Before starting, create a file in the m3 directory named .env: set M3_ADMIN_PASSWORD (16–72 UTF-8 bytes) and M3_SECRET_KEY (32 random bytes encoded as Base64). Generate a key with openssl rand -base64 32.
QUICK START / TERMINAL
# Get the source code
$ git clone https://github.com/sysadminanywhere/m3.git
$ cd m3
# Configure .env, then start the stack
$ docker compose up --build -d Docker + Docker Compose → localhost:8080
A FEW MORE DETAILS
Good to know.
Where does my data live?+
M3 runs in your infrastructure. PostgreSQL stores messages, configuration and processing jobs. Docker Compose starts the application, PostgreSQL, RabbitMQ and a Docker API proxy.
Is M3 open source?+
The project is being prepared for publication under a source-available model. The proposed Community license allows internal use, including by businesses, but prohibits code modification and redistribution of customer builds. See the current draft license in the repository.
What if the broker is unavailable?+
Inbound messages remain in the database. Notifications wait in the transactional outbox and are sent when the connection is restored. Outbound delivery has separate jobs, statuses and retries.
How do I switch to Scale?+
The full distribution runs in Community mode without paid activation. A signed entitlement activates Scale features within the agreed limits. See the distribution documentation and draft commercial license for details.