Your agents receive what matters, without agreeing on a topic name first
Semantik is a semantic message broker. Publishers send messages. Subscribers describe the meaning they care about in SemQL, and every message that matches arrives over a live stream. The same messages are one HTTP call away when you want to search instead of wait.
Topic brokers ask you to label content before you know what the content is going to be. Agent systems generate text whose taxonomy nobody has yet. So Semantik routes on the content itself. A new subscriber picks a region of meaning and starts receiving relevant messages, with no new topic and no change to any publisher.
Delivery by meaning
An agent publishes what it found. Every subscription whose query matches that meaning receives it, in the same moment, whether or not the publisher knew the subscriber existed. One publish can match many subscriptions, and each one gets its own match event.
Namespaces
A namespace is an isolated scope for your messages and subscriptions. It pins one embedding model and one dimension count, and every publish, search and subscribe declares the same pair. Use one per tenant, and the shared global namespace when you want to reach across them.
SemQL
A query language for regions of meaning. DISTANCE is a sphere around an anchor phrase. DIRECTION is a cone pointed at one or more themes. CONTRAST pulls toward one idea and away from another. Compose with AND, OR and NOT, then scope with NAMESPACE, WINDOW and LIMIT.
Parallel coding agents, one shared context
Run four agents on one repo and they each build context from scratch, then throw it away. Give them a namespace and each one publishes what it changed and what it found. The agents that care subscribe by meaning and hear about it live. Nobody agrees on a channel first.
See how it works for parallel agentsWhat Semantik is not
- Not a replacement for Kafka. If you know your taxonomy up front and you need per-partition ordering at very high throughput, use a topic broker. Semantik gives no ordering guarantee, and delivery is at-least-once.
- Not a vector database. Search over your namespace is there, and it's the same data your subscriptions match against, but it isn't built to be your document store.
- Not a managed memory product. There's no automatic summarising and no ranking of what an agent should remember. You publish what you decide is worth publishing.
- Not an interop standard. Semantik tells an agent that something happened. It doesn't assign work or track a task through its lifecycle.
Semantik, Semantic Kernel, semantic-router
Three names that share a root and solve different problems. Semantik is Noetive's message broker: a hosted service you call over HTTP that stores messages, matches them against SemQL queries by meaning, and streams matches to subscribers.
Microsoft Semantic Kernel is an agent orchestration SDK from another vendor that runs inside your process.
semantic-router, from Aurelio Labs, is a decision layer that picks which route a request should take. It chooses a branch; Semantik delivers a message.