noozle.io Start a pilot

Your events, your rules. Across your AI agents, applications, teams, workflows, platforms and partners.

Select business events by their fields, text and meaning. Deliver matches to the applications, agents and people that need them, through your configured destinations.

Start a Streaming pilotSee how it works

Illustrative example: shipment SHP-1042 has region EU, a delay of 180 minutes and a position about 7 km from the Milan hub. Sources: shipments from a Kafka topic, inventory from an SQL database, support from Elasticsearch, access from Google Pub/Sub, billing from AWS S3 and orders from an HTTPS API. Every rule on the Shipments source is checked at once, and two match. Rule 1, doc.region == "EU" && doc.delay_minutes > 120, sends custom JSON to the business application through a Kafka topic and to the operations team through ntfy push. Rule 2, geo.distance(doc.position, [45.46, 9.19], 50000), sends a copy to the AI assistant through an SSE stream. Each copy arrives as the original JSON and is reshaped for its outlet before it is sent: the application receives shipment, region and delay; the operations team receives the shipment and a message; the AI assistant receives the shipment ID and a context object. The workflow runner, analytics platform and logistics partner are not linked to these rules. Other examples use language detection, meaning, word proximity, fuzzy and text matching; some match one rule, some two.

Illustrative events, rules and payloads. Dispatched does not mean confirmed delivery.

Route by what the event says, not where it was published.

Topics are chosen by the system that produces an event, long before anyone knows who needs it. Field filters can compare a value, but not read a support ticket or a shipment note. Streaming lets each team describe the events it needs in one rule, and delivers only those.

Can your team…Topics and queuesField filtersNoozle Streaming
…reach a destination the producer did not plan for?Usually a new topic, or a change in the producerYes, with a filter per consumerYes, with a rule per destination
…select by the words in free text?Usually filtered later, in consumer codePrefix, suffix or wildcard on one fieldYes: words, phrases, typos and meaning
…combine any conditions with and/or?Through topic namingWithin the filter format’s limitsYes, any expression across fields
…select by place or language?Usually in consumer codeUsually in consumer codeYes, written into the rule
…see why an event was delivered?The topic it was published toUsually not recordedYes, a trace with the rule revision

A category comparison. Individual products differ, and topics or simple filters are often the right tool for fixed routes.

Rules that read the whole event.

Combine fields with words, meaning, places and language in one expression. Streaming uses Gate’s policy language, so a rule your team learns once works for AI requests and business events alike.

One event, five ways to select it · illustrative example
Incoming event 
{
  "ticket": "TKT-3016",
  "priority": "high",
  "customer": { "tier": "gold" },
  "subject": "Spedizione bloccata",
  "text": "Il pacco è fermo a Bologna
           da tre giorni: chiedo un rimborso.",
  "position": [44.4949, 11.3426]
}

Fields and logic

doc.priority == "high"             a value
  && doc.customer?.tier
     in ["gold", "platinum"]       a nested list

Match · delivered to the priority support queue

Compare values, check lists and ranges, reach into nested fields and combine everything with and, or and not.

Words

near(doc.text, "pacco", "fermo", 2)   words close together
  && fuzzy(doc.text, "rimborso", 1)  one typo allowed

Match · delivered to logistics escalations

Find words near each other, tolerate typos such as “rimborzo”, match every form of a word, names and regular expressions.

Meaning

about(doc.text, "late delivery", 0.8)   your threshold

Match · delivered to the customer care agent

The topic is written in English and the ticket in Italian. The rule selects by meaning, with a threshold you set.

Places

geo.distance(doc.position,
  [44.4949, 11.3426], 30000)         within 30 km of Bologna

Match · delivered to the Bologna hub team

Test positions in the event against a point and radius, or an area you draw as a polygon.

Language

detect_language(doc.text) == "it"   the text’s language

Match · delivered to the Italian support team

Route each ticket to the team that reads its language, and combine it with any other condition.

Add every rule you need. The stream keeps its pace.

Streaming indexes your rules by what they look for, so each event is checked only against the few that could apply. Skipping is safe: the index follows each rule’s and/or logic and passes over it only when the event lacks the prerequisites of every way it could match. It never hides a match.

  1. Every rulefor every outlet, as your teams add them
  2. Indexedby the words, values and places each rule needs
  3. A few candidatesfor this event, chosen by the index
  4. Full evaluationdecides each match, exactly as written

From your sources to the right outlets.

Use the same policy language to select business events by their fields, text and meaning. Send matching events to the teams and systems that need them, with a delivery format for each destination.

Source integrations to discuss for your pilot. The current source API supports HTTP polling; the other source connections listed below require integration work agreed for the pilot.

Sources
KafkaAMQPPulsarNATS JetStreamGoogle Pub/SubAWS SQSHTTP webhooks
Outlets
KafkaAMQPPulsarNATS JetStreamGoogle Pub/SubAWS SQSAWS SNSHTTP streamsSSEPush alerts

Sources

Your topics, queues and webhooks.

Your rules

Combine fields, text patterns, language and meaning to select relevant events.

Outlets

Deliver matching events as they are, or select and rename fields for each destination.

A delayed shipment reaches the operations queue

Illustrative example. The source event supplies the status and region; the policy checks those fields.

Event

{
  "shipment_id": "SHP-1042",
  "status": "delayed",
  "region": "EU"
}

Policy

doc.status == "delayed" &&
  doc.region == "EU"

Match: deliver this event to the configured Kafka outlet, topic operations.shipments. The receiving system handles the follow-up.

  • Business exceptions

    Send failed-payment or delayed-shipment updates to an operations queue, using status, customer tier and region from each event.

  • Team-specific feeds

    Give each team the updates it needs. Select by region, product or business unit, then choose which fields to include in its feed.

  • Data-quality review

    Flag missing business fields or inconsistent values in JSON records, and deliver the matches to a review queue.

  • Ticket routing

    Route ticket data by topic and language, combined with priority and customer attributes already in the event.

  • Operations alerts

    Send events reporting critical errors or exceeded thresholds to an operations queue or push alerts.

  • Analytics and AI feeds

    Select relevant records and fields for your existing analytics, search or AI ingestion pipeline. Deliver them through a topic or queue.

Tell us which events you want to route and where they should go. Start a pilot with Noozle Streaming.

Start a Streaming pilot

Give your AI agents the events they need, and only those.

An agent works best with relevant context and nothing else. Select events by meaning, keep only the fields the agent should see, and deliver them through an HTTP stream, a WebSocket or a queue it already reads. The same rules decide what each agent receives, so you can review them like any other policy.

  1. 1 · Select

    By meaning

    about(doc.note, "late delivery", 0.8)

    Only events about a late delivery reach the agent, however they are worded.

  2. 2 · Trim

    To the context it needs

    root.shipment_id =
  this.document.shipment_id
root.context.hub =
  this.document.hub
root.context.delay_minutes =
  this.document.delay_minutes

    A mapping for this outlet keeps three fields. Everything else stays in your systems.

  3. 3 · Deliver

    On a channel it reads

    {"shipment_id": "SHP-1042",
 "context": {"hub": "Milan",
             "delay_minutes": 180}}

    Through an HTTP stream, a WebSocket or a queue the agent already consumes.

Illustrative example. Field names depend on your events.

Each outlet gets what it needs. Nothing more is kept.

  • Your original event, unchangedwithout a mapping, each outlet receives the exact bytes your source sent.
  • A format for each outleta saved mapping reshapes the event for one destination. It runs isolated and cannot change where the event goes.
  • Only the routes you approvedevery delivery is checked against your rule and outlet links before any mapping or transport runs.
  • One failing outlet never holds back the othersevery other matching destination is still attempted, and the failure is recorded for that outlet.
  • Duplicates you can recogniseeach delivery carries an idempotency key and a correlation ID, so receivers can drop repeats.
  • No copy in our databaseevents pass through for delivery and are never written to Noozle’s database or local files.

See why an event matched, and which revision decided.

Live rule trace · illustrative example
MATCH q:212 rev 4 · event SHP-1042
Late deliveries for priority customers
AND
  ✓ field     doc.priority == "high"   matched
  OR
    ✓ semantic  about(late delivery)   score 0.8634 / 0.8000
    » geo       distance ≤ 30 km   skipped after ancestor short-circuit
Delivered to 2 outlets · q:212 rev 4
  • Revisions that mean somethinga rule’s revision changes only when its expression changes. Renaming or pausing it keeps the revision.
  • Live, for a limited timestart a trace session on a rule and follow its decisions as events arrive.
  • Evidence for each conditionwhich conditions ran, each score against its threshold, and what was skipped.

Each recipient sees only the fields it needs.

Decide per outlet which fields leave your systems, so analytics never receives a customer’s email and a partner never sees an amount. Events are never written to Noozle’s database, and the EU cloud runs on European infrastructure. These are technical controls you can show your DPO, applied to every delivery.

Fields each recipient receives from one order event
Recipientordercustomeremailamountregion
AnalyticsSentRemovedRemovedSentSent
SupportSentSentSentRemovedRemoved
PartnerSentRemovedRemovedRemovedSent

Illustrative example. Each outlet’s mapping selects its fields; the original event is unchanged in your systems.

Start in our EU cloud. Run on-premise when you are ready.

Use the same policy language to route events in either deployment.

EU cloud

Made and hosted in Europe

Start your Streaming pilot.

  • Operated by Noozle on EU-owned infrastructure
  • Connect your sources and outlets
  • Test rules against your business events

On-premise

Run in your own infrastructure.

  • In your data centre or private cloud
  • Connect to your internal topics and queues
  • Your team operates the deployment

What Streaming does today, in beta.

We run pilots with teams who route real business events, and extend Streaming around what they need.

Rules

The policy language shared with Gate: fields, words, meaning, places and language.

Sources and outlets

HTTP polling sources today, other connections through pilot integration. Delivery to the outlets listed on this page.

Delivery

Original events or a format per outlet, with failures isolated per destination.

Evidence

Rule revisions and live traces for every rule.

Designed and built in Europe, on open and inspectable foundations.

Noozle is an Italian company, and your data stays under EU law, wherever your teams work. The team that wrote the policy language, the matching engine and the delivery runtime is the team you talk to. Need a new source or outlet? Tell us: we extend the product around what customers need.

Made
and hosted
in Europe

  • Built on open foundationsrules run on the open-source Expr language, and transports on Bento, an open-source stream processor.

Start with the events you need to route.

Tell us your sources, rules and destinations.

Start a Streaming pilot

Contacts. Talk to us about Noozle.

Evaluating Noozle Gate or Noozle Streaming? Tell us which product you're interested in and what you need it to do. We're happy to answer questions about capabilities, integrations and deployment options.

We use these details to reply to your message. Privacy policy. Protected by Cloudflare Turnstile.

Privacy policy

Last updated: 29 September 2026

This policy covers visits to our public website, enquiries and related business correspondence. Processing of data through our customer services is covered by the applicable service documentation.

Who is responsible

The data controller is Noozle Labs S.r.l., Via Vincenzo Monti 4, 20123 Milano MI, Italy, VAT ID IT14795670968. For privacy enquiries and rights requests, contact [email protected].

What we use your data for

Data and purposeLegal basis
Contact details, enquiry contents and related correspondence to respond to you, discuss a pilot and manage our business relationship.Steps requested before a contract, or performance of a contract, where you are personally a party (GDPR Art. 6(1)(b)); otherwise, our legitimate interest in responding to business enquiries and managing relationships with customer representatives (Art. 6(1)(f)).
The page from which you submit a request and campaign parameters in its URL, to understand which pages and campaigns bring enquiries.Our legitimate interest in assessing the effectiveness of our website and campaigns (Art. 6(1)(f)).
Technical information, including IP address, browser information and request logs, to operate the website, verify submissions and prevent abuse.Our legitimate interest in operating and protecting the website and request form (Art. 6(1)(f)).
Analytics identifiers and information about website visits and interactions, to measure website use.Your consent (Art. 6(1)(a)).
Records that must be retained to meet legal obligations or are necessary for legal claims.Compliance with applicable legal obligations (Art. 6(1)(c)), or our legitimate interest in establishing, exercising or defending legal claims (Art. 6(1)(f)), as applicable.

Submitting an enquiry is voluntary. A valid email address is required to receive a reply. The contact form also requires a message; the message is optional in the pilot form. Analytics consent is optional and does not affect access to the website or request form.

Retention

We retain customer correspondence and business contact details for the duration of the customer relationship and for two years after it ends. Enquiries that do not lead to a customer relationship are retained until the enquiry and associated discussions are closed.

Records subject to Article 2220 of the Italian Civil Code are retained for ten years: accounting records from the last accounting entry, and invoices and business correspondence from their issue or receipt, as applicable.

Where a longer period is required by law or necessary for an ongoing legal dispute, we retain only the relevant records until that requirement or dispute has ended.

Technical logs are retained for 30 days.

Cookies and browser storage

Our Cookie policy describes consent preferences, form-draft storage and analytics cookies, including their purposes and lifetimes. You can review or withdraw optional consent through Cookie settings in the footer or Cookie policy.

Recipients and international transfers

Personal data may be processed by the following categories of service providers for the purposes described above:

These services may involve processing outside the European Economic Area, including in the United States.

Your rights

Subject to the applicable legal conditions, you may request access to, correction or erasure of your personal data, restriction of processing, and data portability. Where processing relies on consent, you may withdraw it at any time without affecting the lawfulness of processing carried out before withdrawal.

You may object, on grounds relating to your particular situation, to processing based on our legitimate interests.

To exercise your rights, contact [email protected]. We respond within the time limits required by applicable data protection law.

You may lodge a complaint with the Garante per la protezione dei dati personali or another competent supervisory authority in the EU, in particular where you habitually reside or work, or where the alleged infringement occurred.

Cookie policy

Last updated: 29 September 2026

The data controller is Noozle Labs S.r.l., Via Vincenzo Monti 4, 20123 Milano MI, Italy, VAT ID IT14795670968. Contact: [email protected]. Read this notice with our Privacy policy.

We use cookies and local storage to keep the information described below in your browser.

What we use

Cookie or storage nameProviderPurposeDuration
cc_cookieNoozleRemembers your consent choices. Necessary; does not require consent.182 days
_gaGoogle AnalyticsDistinguishes browsers to measure visits. Requires analytics consent.Default: two years, subject to configured settings and browser limits
_ga_*Google AnalyticsMaintains session information. Requires analytics consent. The suffix identifies the Analytics property.Default: two years, subject to configured settings and browser limits
noozle-pilot-draft (local storage)NoozleSaves your email address, message and product selection as you fill in the pilot form. Currently operates without a separate consent choice.Until successful submission or deletion of site data; no automatic expiry

Google Analytics uses cookies on our domain. See Google’s cookie documentation and privacy policy. Cookie expiry is separate from retention of information already collected, addressed in our Privacy policy.

Your choices

Analytics requires your consent. You can reject it and still browse the website and request a pilot.

Cookie settings are unavailable because optional tracking is not configured or the consent controls could not load.

To change or withdraw consent at any time, open Cookie settings here or in the footer, disable Analytics and select Save my choice, or select Reject all. Your choice applies to this browser.

Withdrawal does not affect the lawfulness of processing before withdrawal or automatically erase previously collected data. Existing cookies may remain until they expire or you delete them.

Browser controls

You can also block or delete cookies and site data in your browser settings. Instructions:

Deleting site data removes saved preferences and form drafts. Blocking storage can prevent those features from working.

Further privacy information

See our Privacy policy for recipients, international transfers, data-protection rights and how to exercise them, including your right to complain to a supervisory authority. It also describes form-protection processing by Cloudflare Turnstile.