Features / Connect
Real systems are not single apps. They are many services and agents talking to each other. Nodge models this directly: your apps and agents are nodes, and the events and actions between them are edges you can see and govern.
Each app announces topics and subscribes to topics from other apps. You can see, for any app, what it publishes, what it listens to, and who depends on it.
Topics can be open or private. A private topic requires the owning team's approval before another app can subscribe, so sensitive data flows are deliberate.
When one app is approved to call another's action, the platform mints a scoped API key automatically, wires it into both sides, and lets you rotate it. No manual key passing.
Connect any topic to an external endpoint like a chat or paging tool, so the right people hear about the right events.
Browse every topic across your organization. The AI agent uses this same catalogue to wire new services into the existing graph correctly.
Actions, topics, and subscriptions live in a manifest in your repository and sync on every deploy, so the wiring is versioned with the code.
Your architecture, visible and governed.
Through an event bus. Apps and agents publish topics and subscribe to topics from other apps, forming a visible graph of your services.
Yes. Topics can be private, which requires the owning team's approval before another app can subscribe.
When one app is approved to call another's action, the platform mints a scoped key automatically, wires it into both apps, and lets you rotate it. You do not pass keys by hand.
Yes. Any topic can be connected to an external endpoint such as a chat or paging tool.
In a manifest file in your repository. Actions, topics, and subscriptions sync on every deploy, so the wiring is versioned with your code.
It lets you browse every topic in your organization, and the AI agent uses it to wire new services into the existing graph correctly.
