Every connection is an explicit endpoint, method, and direction — inspectable on the diagram and in the inspector.
The definitive platform blueprint
The architectural blueprint is a set of well defined systems of logic, where the gravitational pull is centered around problem spaces that create logical boundaries and abstractions around specific complex domains.
Applications
Automatically add any of our 230 pre-approved applications. These follow our high standards for evaluation.
Integration services
- Encapsulates all logic required for the flow of data from and to external solutions.
- Custom integrations can be provisioned.
- They are actual repositories — your developers can still code.
Domain services
- Orchestrates and owns complicated domain logic.
- Master of the data for the rest of the ecosystem.
- Built on our open source libraries, with zero vendor lock-in.
Web and native front-ends
- Composable front-ends developed using our components.
- Own the customer relationship.
- Complete code ownership.
And much more
From shared packages to how data moves through the platform.
Anti-corruption layer
Integration services sit between packaged systems and the bus, so domain logic stays behind a stable protocol instead of vendor shapes.
Automatic data lineage
Publish, subscribe, and protocol uses record how data moves between applications, services, and streams.
Traceability
Every connection is an explicit endpoint, method, and direction — inspectable on the diagram and in the inspector.
Channels
One bus on the mesh. A service publishes on its own stream, and each reader acknowledges on its own group.
Gateway
Every node runs the gateway. It verifies the session, then dials the service ok.yaml names for that path.